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

Add Workspaces in Release pipeline instead of PipelineResources #1061

Merged

Conversation

vinamra28
Copy link
Member

@vinamra28 vinamra28 commented Jul 10, 2020

Changes

Currently release pipeline is using PipelineResources so instead of that we are replacing them with workspaces and also adding the git-clone task.

Closes #1019

Signed-off-by: vinamra28 vinjain@redhat.com

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Run the code checkers with make check
  • Regenerate the manpages, docs and go formatting with make generated
  • Commit messages follow commit message best practices

See the contribution guide
for more details.

@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Jul 10, 2020
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 10, 2020
@vinamra28
Copy link
Member Author

/test pull-tekton-cli-integration-tests

@tekton-robot tekton-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. and removed release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Jul 10, 2020
@vinamra28
Copy link
Member Author

/release-note-none

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 10, 2020
@vinamra28 vinamra28 changed the title Add Workspaces in Release pipeline instead os PipelineResources Add Workspaces in Release pipeline instead of PipelineResources Jul 10, 2020
Currently release pipeline is using PipelineResources so instead of that we are replacing them with workspaces and also adding the git-clone task.

Signed-off-by: vinamra28 <vinjain@redhat.com>
@vinamra28 vinamra28 force-pushed the vinamra28/release-pipeline-cleanup branch from ef87c31 to ff6d9ad Compare July 14, 2020 10:30
@vinamra28
Copy link
Member Author

@vdemeester could you please review 😅

@piyush-garg
Copy link
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 20, 2020
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good to me. I think we should go ahead and get this in — and exercices it during next release 😝
/cc @danielhelfand @chmouel @piyush-garg

tekton/release-pipeline-run.yml Outdated Show resolved Hide resolved
Signed-off-by: vinamra28 <vinjain@redhat.com>
@tekton-robot tekton-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 21, 2020
@vdemeester
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 21, 2020
@piyush-garg
Copy link
Contributor

/lgtm

Copy link
Contributor

@pradeepitm12 pradeepitm12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pradeepitm12

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2020
@pradeepitm12
Copy link
Contributor

/test pull-tekton-cli-integration-tests

@tekton-robot tekton-robot merged commit a66a0d2 into tektoncd:master Jul 22, 2020
@vinamra28 vinamra28 deleted the vinamra28/release-pipeline-cleanup branch July 22, 2020 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use workspaces instead of PipelineResource on release pipeline
5 participants