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 nightly release pipeline to match release pipeline #5191

Closed
dibyom opened this issue Jul 21, 2022 · 2 comments
Closed

Update nightly release pipeline to match release pipeline #5191

dibyom opened this issue Jul 21, 2022 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@dibyom
Copy link
Member

dibyom commented Jul 21, 2022

Expected Behavior

Nightly release pipeline should execute the same logic as the actual release pipeline

Actual Behavior

The nightly release pipeline looks very old (still uses pipeline resources)

Nightly: https://dashboard.dogfooding.tekton.dev/#/namespaces/default/pipelines/pipeline-release-nightly?view=yaml
Release: https://dashboard.dogfooding.tekton.dev/#/namespaces/default/pipelines/pipeline-release?view=yaml

I think we might be able to just replace the old pipeline with a new one. The work would be around identifying and making changes in our Nightly trigger to update the inputs for the new pipeline.

@dibyom dibyom added the kind/bug Categorizes issue or PR as related to a bug. label Jul 21, 2022
@imjasonh
Copy link
Member

Where does pipeline-release-nightly.yaml even come from?

I only see a pipeline-release.yaml in the repo, and publish-release-nightly.yaml was deleted in #3788 (Feb 2021)

cc @afrittoli

@dibyom
Copy link
Member Author

dibyom commented Jul 21, 2022

I was wrong - looks like we are using an updated pipeline but that is in the tekton-nightly namespace

@dibyom dibyom closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants