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

Create Pipeline for running Tekton Pipeline CI/CD #539

Closed
bobcatfish opened this issue Feb 21, 2019 · 2 comments
Closed

Create Pipeline for running Tekton Pipeline CI/CD #539

bobcatfish opened this issue Feb 21, 2019 · 2 comments
Labels
area/yamls This issue involves writing a lot of yaml

Comments

@bobcatfish
Copy link
Collaborator

bobcatfish commented Feb 21, 2019

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):

            unit tests (#532)                    build a test cluster (#534)      
                      |                                     |
     report result to github (#535)                         |
                      |                                     |
                       \                                   /
                         \                               /
          end to end tests (#533)          yaml tests (#536)      
                          | .                     |       
        report result to github (#535)   report result to github (#535)   
                           \                      /
                             teardown test cluster  (* see additional info)

("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

@bobcatfish 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
@abayer
Copy link
Contributor

abayer commented 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?

@bobcatfish
Copy link
Collaborator Author

chmouel pushed a commit to chmouel/tektoncd-pipeline that referenced this issue Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/yamls This issue involves writing a lot of yaml
Projects
None yet
Development

No branches or pull requests

2 participants