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

CI improvements #264

Merged
merged 1 commit into from
Aug 9, 2024
Merged

CI improvements #264

merged 1 commit into from
Aug 9, 2024

Conversation

alilleybrinker
Copy link
Collaborator

This commit features several CI improvements:

  • Clearer naming of CI files, pipelines, and jobs.
  • Adds "website-test.yml" to test website changes on PRs.
  • Removes duplicative tests on main after equivalent tests on PRs, given that PRs can only merge with passing tests.

@alilleybrinker alilleybrinker added the type: chore Clean up or management task. label Aug 8, 2024
@alilleybrinker alilleybrinker added this to the 3.6.0 milestone Aug 8, 2024
@alilleybrinker alilleybrinker self-assigned this Aug 8, 2024
@alilleybrinker alilleybrinker changed the title chore: CI improvements. CI improvements Aug 8, 2024
This commit features several CI improvements:

- Clearer naming of CI files, pipelines, and jobs.
- Adds "website-test.yml" to test website changes on PRs.
- Removes duplicative tests on `main` after equivalent tests
  on PRs, given that PRs can only merge with passing tests.

Signed-off-by: Andrew Lilley Brinker <[email protected]>
@alilleybrinker alilleybrinker force-pushed the alilleybrinker/site-ci branch from 2573775 to 3977498 Compare August 9, 2024 17:32
@alilleybrinker alilleybrinker requested review from a team and patrickjcasey and removed request for a team August 9, 2024 17:33
@mchernicoff mchernicoff merged commit bf2a68a into main Aug 9, 2024
6 checks passed
alilleybrinker added a commit that referenced this pull request Aug 9, 2024
The website deploy CI job was quietly broken by #264, and this commit
fixes it by ensuring the job dependency name matches the earlier renamed
build job.

It also gives the "Website Deploy" and "Website Test" workflows distinct
names so they're clearly different in the GitHub UI.

Signed-off-by: Andrew Lilley Brinker <[email protected]>
mchernicoff pushed a commit that referenced this pull request Aug 9, 2024
The website deploy CI job was quietly broken by #264, and this commit
fixes it by ensuring the job dependency name matches the earlier renamed
build job.

It also gives the "Website Deploy" and "Website Test" workflows distinct
names so they're clearly different in the GitHub UI.

Signed-off-by: Andrew Lilley Brinker <[email protected]>
@cstepanian
Copy link
Contributor

I think there is a caching issue caused by no longer running the tests on pushes to main.
It may seem duplicative to also build on main, but the end result will be that every Pull Request build will start without a cache. (subsequent pushes to the PR will be able to use the cache created for that PR)

GitHub Actions isolates caches created for Pull Requests, so they cannot be used when building other Pull Requests (except when the new PR is based on another PR that had a cache) or the main branch.
Builds on main are the only way for Actions to create caches that can be used by Pull Requests on their first build.

@alilleybrinker
Copy link
Collaborator Author

Oh, how annoying. Okay, want to open a PR to run on main again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: chore Clean up or management task.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants