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.

Sign up for GitHub

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

Jump to bottom

The release pipeline does not store artifacts on the GCS bucket #1325

Closed
afrittoli opened this issue Sep 17, 2019 · 0 comments · Fixed by #1327
Closed

The release pipeline does not store artifacts on the GCS bucket #1325

afrittoli opened this issue Sep 17, 2019 · 0 comments · Fixed by #1327
Assignees
@afrittoli
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
Pipelines 0.7 🐱

Comments

@afrittoli
Copy link
Member

Expected Behavior

The release yaml should be store on the target GCS bucket

Actual Behavior

Since #1122, we changed the behaviour of resources that are used as both inputs and outputs. We'll need a step in the release pipeline to add the content work /workspace/output/bucker

Steps to Reproduce the Problem

  1. Run the release pipeline
  2. No content is added to the bucket

Additional Info
@afrittoli afrittoli self-assigned this Sep 17, 2019
@afrittoli afrittoli added kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Sep 17, 2019
afrittoli added a commit to afrittoli/pipeline that referenced this issue Sep 17, 2019
@afrittoli
Fix release pipeline to handle tektoncd#1122
64393fa 
Since tektoncd#1122, we do not treat outputs that were inputs as well in any
special way, meaning that the output folder will be empty unless we
copy the input to the output.

Fix the release pipeline to handle that.

Fixes: tektoncd#1325
@afrittoli afrittoli added this to the Pipelines 0.7 🐱 milestone Sep 17, 2019
@afrittoli afrittoli mentioned this issue Sep 17, 2019
Merged
3 tasks
tekton-robot pushed a commit that referenced this issue Sep 18, 2019
@afrittoli @tekton-robot
Fix release pipeline to handle #1122
05c4164 
Since #1122, we do not treat outputs that were inputs as well in any
special way, meaning that the output folder will be empty unless we
copy the input to the output.

Fix the release pipeline to handle that.

Fixes: #1325
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afrittoli afrittoli

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Milestone
Pipelines 0.7 🐱
Development

Successfully merging a pull request may close this issue.

Fix release pipeline to handle #1122 afrittoli/pipeline
1 participant
@afrittoli