Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make use of GitHub CI #107

Merged
merged 39 commits into from
Jan 16, 2023
Merged

Make use of GitHub CI #107

merged 39 commits into from
Jan 16, 2023

Conversation

rptb1
Copy link
Member

@rptb1 rptb1 commented Jan 11, 2023

Implementing use of GitHub CI in parallel with Travis CI to help with #109 .

Maintaining both helps with #98 (comment)

I suggest reviewing and merging #104 to master before this, because it's included.

@rptb1 rptb1 added the build Problems with builds and build automation label Jan 11, 2023
@rptb1 rptb1 changed the title Experimenting with GitHub CI Make use of GitHub CI Jan 13, 2023
@rptb1 rptb1 linked an issue Jan 13, 2023 that may be closed by this pull request
@rptb1 rptb1 marked this pull request as ready for review January 14, 2023 10:30
@rptb1 rptb1 added the git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo label Jan 14, 2023
@rptb1 rptb1 marked this pull request as draft January 15, 2023 14:48
@rptb1
Copy link
Member Author

rptb1 commented Jan 15, 2023

Reverted to draft while I update and cross-reference design.mps.tests.ci.

@rptb1 rptb1 added the optional Will cause failures / of benefit. Worth assigning resources. label Jan 15, 2023
@rptb1 rptb1 added this to the Perforce Polarity milestone Jan 16, 2023
@rptb1 rptb1 marked this pull request as ready for review January 16, 2023 14:11
Copy link
Contributor

@thejayps thejayps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are doing a "review lite" as suggested by @rptb1.

Review paused to merge pull request #92

.github/workflows/build-and-test.yml Show resolved Hide resolved
.travis.yml Show resolved Hide resolved
code/poolams.c Outdated Show resolved Hide resolved
…ate irrelevant differences from branch/2023-01-06/gcc-11.3.0-warnings from code review.
Copy link
Contributor

@thejayps thejayps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good after merge of #92 (also see #114)

@rptb1
Copy link
Member Author

rptb1 commented Jan 16, 2023

Executing pull request merge procedure.

Checklist results

  1. A nice meta-thing is that the Check results above not only show that the branch builds, but that it solves the problem as well!

  2. An automated test case for this is impractical because it would require demonstrating that Travis was slower on branches in Git.

  3. This branch introduces one file under the MIT licence, which is totally compatible with the MPS BSD licence but illustrates how the MPS must cope with licensed material.

  4. Not quite. The Travis build is queued up for at least an hour because of the very problem that this branch solves. So we're going to go ahead (since there are no actual MPS code changes). We're overriding the procedure in this case.

@rptb1 rptb1 merged commit 3c62e29 into master Jan 16, 2023
rptb1 added a commit that referenced this pull request Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Problems with builds and build automation git-migration Project migration from Ravenbrook internal Perforce infrastructure to public git repo optional Will cause failures / of benefit. Worth assigning resources.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MPS CI relies on slow and expensive Travis CI
2 participants