feat(RELEASE-1328): embargo-check pipeline is called via git resolver #783
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
|
Skipping CI for Draft Pull Request. |
|
Relates to #782 |
johnbieren
changed the title
johnbieren
force-pushed
the
release1328
branch
2 times, most recently
from
8ed82f8 to
4dc86a0
Compare
|
/retest |
1 similar comment
|
/retest |
johnbieren
force-pushed
the
release1328
branch
4 times, most recently
from
964cdba to
00b7981
Compare
mmalina
reviewed
Jan 27, 2025
This commit updates the managed task that calls the embargo-check internal pipeline to call the pipeline via git resolver instead of cluster resolver. It also moves the internal embargo-check pipeline to its proper directory, which is where the internal-request script expects it. Signed-off-by: Johnny Bieren <[email protected]>
johnbieren
force-pushed
the
release1328
branch
from
cdfb548 to
811fe03
Compare
|
/retest |
mmalina
approved these changes
Jan 27, 2025
|
/retest |
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.
Describe your changes
Relevant Jira
Checklist before requesting a review
do not mergelabel if there's a dependency PRrelease-service-maintainershandle if you are unsure who to tagSigned-off-by: My name <email>