-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Create Pipeline
for running Tekton Pipeline CI/CD
#539
Labels
area/yamls
This issue involves writing a lot of yaml
Comments
bobcatfish
added
area/yamls
This issue involves writing a lot of yaml
okr
This is for some internal Google project tracking
and removed
okr
This is for some internal Google project tracking
labels
Feb 21, 2019
An idea for the "teardown" task - have it be a shell script run in parallel to the two branches already defined, that periodically queries GitHub to see if the commit status has been set for the two branches, and when they are set, blows away the cluster? |
|
chmouel
pushed a commit
to chmouel/tektoncd-pipeline
that referenced
this issue
Oct 7, 2020
Regenerate openshift patches
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
We should be testing Pipelines with Pipelines.
We should have a Pipeline which does the following, in this order (this is graph with 2 roots):
("end to end tests" and "yaml tests" both execute in parallel, both depend on "build a test cluster" AND the unit test reporting results)
Runs should be triggered by new PR creation.
Actual Behavior
The CI/CD used by Tekton Pipelines (triggered via prow jobs) invokes scripts only.
Additional Info
The text was updated successfully, but these errors were encountered: