forked from Automattic/jetpack
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Arbitrary PR that will fail the plugin install test #13
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anomiex
force-pushed
the
test/build-tests-fail
branch
from
January 9, 2023 20:55
202684e
to
0626ae0
Compare
anomiex
force-pushed
the
test/build-tests-fail
branch
from
January 9, 2023 21:02
0626ae0
to
49eb394
Compare
anomiex
force-pushed
the
test/build-tests-fail
branch
from
January 9, 2023 21:09
49eb394
to
3706a1e
Compare
GitHub has an unfortunate behavior in that workflow artifacts are not available via the API until the entire workflow has completed. This means that the "Test plugin upgrades" job in the build workflow unnecessarily delays the availability of the build artifact for Jetpack Live Branches and future wpcom automated testing for 6 or so minutes. To get around this, we create a new "Post-Build" workflow that is triggered by `workflow_run` after the Build workflow completes. But since this new workflow isn't automatically attached to the PR, we have to make API calls to get it to show up there. This is a second attempt at Automattic#25892, which had to be reverted as using the Actions app put the checks into the "suite" of a random workflow.
anomiex
force-pushed
the
test/build-tests-fail
branch
from
January 9, 2023 21:16
3706a1e
to
625a284
Compare
3 tasks
anomiex
force-pushed
the
trunk
branch
3 times, most recently
from
February 27, 2023 21:07
545e973
to
29e7eb2
Compare
anomiex
force-pushed
the
trunk
branch
12 times, most recently
from
May 20, 2023 17:58
52f7fd0
to
0de0975
Compare
anomiex
force-pushed
the
trunk
branch
2 times, most recently
from
August 30, 2023 14:00
f3284db
to
60a416e
Compare
anomiex
force-pushed
the
trunk
branch
3 times, most recently
from
November 29, 2023 17:17
68bffb0
to
d39bb13
Compare
anomiex
force-pushed
the
trunk
branch
10 times, most recently
from
January 30, 2024 16:54
5d93525
to
5d7882b
Compare
anomiex
force-pushed
the
trunk
branch
2 times, most recently
from
April 4, 2024 18:07
cebab81
to
9584b75
Compare
anomiex
force-pushed
the
trunk
branch
2 times, most recently
from
April 10, 2024 13:25
b03e6b5
to
a0c3167
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #
Proposed changes:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: