feat(RELEASE-1329): create-advisory pipeline is called via git resolver #796
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
johnbieren
force-pushed
the
release1329
branch
4 times, most recently
from
0a815c3 to
23c440d
Compare
This commit updates the managed task that calls the create-advisory internal pipeline to call the pipeline via git resolver instead of cluster resolver. It also moves the internal create-advisory 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
release1329
branch
from
23c440d to
d545e09
Compare
|
/retest |
mmalina
approved these changes
Jan 30, 2025
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.
This commit updates the managed task that calls the create-advisory internal pipeline to call the pipeline via git resolver instead of cluster resolver. It also moves the internal create-advisory pipeline to its proper directory, which is where the internal-request script expects it.
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>