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

feat(RELEASE-1328): embargo-check pipeline is called via git resolver #783

Draft
wants to merge 2 commits into
base: development
Choose a base branch
from

Conversation

johnbieren
Copy link
Collaborator

Describe your changes

Relevant Jira

Checklist before requesting a review

  • I have marked as draft or added do not merge label if there's a dependency PR
    • If you want reviews on your draft PR, you can add reviewers or add the release-service-maintainers handle if you are unsure who to tag
  • My commit message includes Signed-off-by: My name <email>
  • I have bumped the task/pipeline version string and updated changelog in the relevant README
  • I read CONTRIBUTING.MD and commit formatting

Copy link

openshift-ci bot commented Jan 23, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@johnbieren
Copy link
Collaborator Author

Relates to #782

@johnbieren johnbieren changed the title Release1328 feat(RELEASE-1328): embargo-check pipeline is called via git resolver Jan 23, 2025
This commit updates the embargo-check internal pipeline to call its one
task via git resolver. The pipeline itself still uses a cluster
resolver, which will be changed in a separate commit.

Signed-off-by: Johnny Bieren <[email protected]>
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant