Create Pipeline for nightly releases #860
Assignees
Labels
area/test-infra
Issues or PRs related to the testing infrastructure
area/testing
Issues or PRs related to testing
area/yamls
This issue involves writing a lot of yaml
Milestone
Comments
|
/assign |
|
@vdemeester does this mean you'll be doing #531 as well? :D :D :D |
|
@bobcatfish are you saying this is currently blocked by #530 and #531? |
|
@Gl4di4torRr it's not entirely blocked but it's kinda related 👼 Now that Kubecon and Red Hat Summit are behind, I'll have more time to make this happen 🕺 |
|
@vdemeester great! i am looking for a good "first time contributor" issue to tackle. if this would be a good one, i can try implementing this. |
|
@vdemeester nvm looks like y'all have a |
vdemeester
added
area/test-infra
|
Gonna base this on @vdemeester 's proposal for automated releases |
This was referenced Sep 3, 2019
Closed
bobcatfish
added a commit
to bobcatfish/pipeline
that referenced
this issue
Sep 4, 2019
This Pipeline will be triggered via prow over in the tektoncd/plumbing repo every night. It will create releases of all images normally released when doing official releases, plus also the image used for building with ko, and tag them with the date and commit they were built at, and will create the release.yaml as well. This Pipeline is missing a few things that are in the manual release Pipeline - due to tektoncd#1124 unit tests have a race condition, due to tektoncd#1205 the linting is flakey and it would be frustrating to lose a whole nightly release, and finally due to using v0.3.1 it's not possible to use workingDir, which is required by the golang build Task. The Pipelines and Tasks have been updated to work with Tekton Pipelines v0.3.1 because that's what we're using in our official cluster (since currently Prow requires it). Made release instructions more oriented toward someone actually making a release vs. a random person trying to run the same pipeline against their own infrastructure. Removed example Runs b/c it's much simpler to invoke via `tkn`, or Prow (these were falling out of date with how we were actually using the Pipelines/Tasks as well). Fixes tektoncd#860
bobcatfish
added a commit
to bobcatfish/pipeline
that referenced
this issue
Sep 4, 2019
This Pipeline will be triggered via prow over in the tektoncd/plumbing repo every night. It will create releases of all images normally released when doing official releases, plus also the image used for building with ko, and tag them with the date and commit they were built at, and will create the release.yaml as well. This Pipeline is missing a few things that are in the manual release Pipeline - due to tektoncd#1124 unit tests have a race condition, due to tektoncd#1205 the linting is flakey and it would be frustrating to lose a whole nightly release, and finally due to using v0.3.1 it's not possible to use workingDir, which is required by the golang build Task. The Pipelines and Tasks have been updated to work with Tekton Pipelines v0.3.1 because that's what we're using in our official cluster (since currently Prow requires it). Made release instructions more oriented toward someone actually making a release vs. a random person trying to run the same pipeline against their own infrastructure. Removed example Runs b/c it's much simpler to invoke via `tkn`, or Prow (these were falling out of date with how we were actually using the Pipelines/Tasks as well). Removed the `gcs-uploader-image` PipelineResource which is no longer being used. Fixes tektoncd#860
bobcatfish
added a commit
to bobcatfish/plumbing
that referenced
this issue
Sep 4, 2019
This is the configuration to run the Pipeline + Tasks being added in tektoncd/pipeline#1274 every night at midnight PDT. I've successfully run this by setting the cron to every 5 minutes. This configuration is already applied to the repo. Status can be seen at https://prow.tekton.dev/?type=periodic. Part of tektoncd/pipeline#860
2 tasks
tekton-robot
pushed a commit
to tektoncd/plumbing
that referenced
this issue
Sep 5, 2019
This is the configuration to run the Pipeline + Tasks being added in tektoncd/pipeline#1274 every night at midnight PDT. I've successfully run this by setting the cron to every 5 minutes. This configuration is already applied to the repo. Status can be seen at https://prow.tekton.dev/?type=periodic. Part of tektoncd/pipeline#860
|
Nightly releases are now releasing to the gs bucket |
tekton-robot
pushed a commit
that referenced
this issue
Sep 16, 2019
This Pipeline will be triggered via prow over in the tektoncd/plumbing repo every night. It will create releases of all images normally released when doing official releases, plus also the image used for building with ko, and tag them with the date and commit they were built at, and will create the release.yaml as well. This Pipeline is missing a few things that are in the manual release Pipeline - due to #1124 unit tests have a race condition, due to #1205 the linting is flakey and it would be frustrating to lose a whole nightly release, and finally due to using v0.3.1 it's not possible to use workingDir, which is required by the golang build Task. The Pipelines and Tasks have been updated to work with Tekton Pipelines v0.3.1 because that's what we're using in our official cluster (since currently Prow requires it). Made release instructions more oriented toward someone actually making a release vs. a random person trying to run the same pipeline against their own infrastructure. Removed example Runs b/c it's much simpler to invoke via `tkn`, or Prow (these were falling out of date with how we were actually using the Pipelines/Tasks as well). Removed the `gcs-uploader-image` PipelineResource which is no longer being used. Fixes #860
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Folks who are integrating with Tekton would like to be able to integrate with regular builds (e.g. nightly) so that they can test out new functionality and catch integration pain points and bugs between releases.
Actual Behavior
Currently we release manually approximately every 4 weeks. In #531 we will add a Pipeline which can do this via Prow.
Additional Info
Pipelinefor releases #531 adds release Pipeline triggering via ProwSolving this issue should include:
The text was updated successfully, but these errors were encountered: