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

Update Sage Test workflow #121

Merged
merged 12 commits into from
Apr 30, 2024
Merged

Update Sage Test workflow #121

merged 12 commits into from
Apr 30, 2024

Conversation

jazzsequence
Copy link
Contributor

@jazzsequence jazzsequence commented Apr 30, 2024

Resolves an issue where Sage Test workflow fails on multidev creation because {os}-{phpver}- (e.g. mac-81-) is not a valid multidev name.

Some additional changes were made in this workflow to ensure consistency and future debugging. The trigger was updated to pull_request from push so closing, reopening, or transitions could trigger the workflow. Additionally, the pr_num (which is a misnomer now) logic was updated to use the GHA run number instead of the PR number. This way the number is more unique and there is less change of multidev name collisions when subsequent pushes are made to the same PR.

An Apply Upstream Updates step was broken out of the workflow and set as a dependency for the Sage tests because it was previously being run inside the matrix of tests. This meant that any test that found upstream updates could fail other tests that are checking for upstream updates at the same time.

@jazzsequence jazzsequence requested review from a team as code owners April 30, 2024 19:54
@jazzsequence jazzsequence changed the title if there is no pr number, set pr_num to rel Update Sage Test workflow Apr 30, 2024
@jazzsequence
Copy link
Contributor Author

MacOS tests are failing on multidev creation with Create a Multidev environment [error] The default platform hostname mac-82-99-wpcm-sage-install-tests.pantheonsite.io already exists. This is unrelated to the changes here and seems to be incidental (if the run # was 100, it would not fail, as indicated in the successful builds here. This should be safe to merge.

@jazzsequence jazzsequence merged commit 8db06be into default Apr 30, 2024
8 of 11 checks passed
@jazzsequence jazzsequence deleted the pr-num-on-release-sage-test branch April 30, 2024 21:57
jazzsequence pushed a commit that referenced this pull request Jul 31, 2024
jazzsequence added a commit that referenced this pull request Jul 31, 2024
* if there is no pr number, set pr_num to rel

* use brackets for multidev_name vars

* move workflow to pull_request instead of push

* apply the upstream updates to the multisite
this is happening inside a matrix so it will break if another run updates the upstream before the current one finishes

* don't echo empty string

* remove stray "

* apply upstream updates as a step outside the matrix

* get pr number from pull_request event

* update fallback logic

* use run number instead of pr

* use new install terminus action
jazzsequence pushed a commit that referenced this pull request Aug 1, 2024
jazzsequence added a commit that referenced this pull request Aug 1, 2024
* if there is no pr number, set pr_num to rel

* use brackets for multidev_name vars

* move workflow to pull_request instead of push

* apply the upstream updates to the multisite
this is happening inside a matrix so it will break if another run updates the upstream before the current one finishes

* don't echo empty string

* remove stray "

* apply upstream updates as a step outside the matrix

* get pr number from pull_request event

* update fallback logic

* use run number instead of pr

* use new install terminus action
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant