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

storage.googleapis.com latest release yaml still on v0.50 #7122

Closed
jimmyjones2 opened this issue Sep 17, 2023 · 12 comments
Closed

storage.googleapis.com latest release yaml still on v0.50 #7122

jimmyjones2 opened this issue Sep 17, 2023 · 12 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@jimmyjones2
Copy link
Contributor

Expected Behavior

https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml installs the latest v0.51

Actual Behavior

https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml installs v0.50

@jimmyjones2 jimmyjones2 added the kind/bug Categorizes issue or PR as related to a bug. label Sep 17, 2023
@khrm
Copy link
Contributor

khrm commented Sep 21, 2023

e2e tests are failing due to this reason. Unless we do v0.50.2 with the fix.
#7108

@khrm
Copy link
Contributor

khrm commented Sep 21, 2023

@vdemeester @lbernick @pritidesai Did we change the release policy to have the latest only as LTS? Or is it a mistake during release and by mistake we put the backporting flag?

@vdemeester
Copy link
Member

@khrm nope. I need to check why it's not the 0.51.x release on latest. I think I did set the correct flag and there was no error so… not sure what happened 🤔

@vdemeester
Copy link
Member

2023-09-21-142424

Hum interesting, something is wrong with the release pipeline it seems.

@vdemeester
Copy link
Member

cc @afrittoli

@pritidesai
Copy link
Member

I set the right setting yesterday while releasing 0.52.

releaseAsLatest=true

you are right, the latest does not point to 0.52

@pritidesai
Copy link
Member

What version of pipelines are we running in dogfooding?

@AlanGreene
Copy link
Member

v0.49.0

image

@pritidesai
Copy link
Member

Release to bucket-latest succeeded:

 ∙ pipeline-release-run-kfnck-publish-to-bucket-latest   publish-to-bucket-latest   19 hours ago   54s        Succeeded
 tkn taskrun --context=dogfooding describe pipeline-release-run-kfnck-publish-to-bucket-latest -n default
Name:              pipeline-release-run-kfnck-publish-to-bucket-latest
Namespace:         default
Service Account:   release-right-meow
Timeout:           1h0m0s
Labels:
 app.kubernetes.io/managed-by=tekton-pipelines
 app.kubernetes.io/version=0.3
 tekton.dev/memberOf=tasks
 tekton.dev/pipeline=pipeline-release
 tekton.dev/pipelineRun=pipeline-release-run-kfnck
 tekton.dev/pipelineTask=publish-to-bucket-latest
 tekton.dev/task=gcs-upload
Annotations:
 chains.tekton.dev/signed=true
 pipeline.tekton.dev/affinity-assistant=affinity-assistant-1bb04eb4f2
 pipeline.tekton.dev/release=c802069
 tekton.dev/categories=Cloud, Storage
 tekton.dev/displayName=Upload to GCS
 tekton.dev/pipelines.minVersion=0.12.1
 tekton.dev/platforms=linux/amd64
 tekton.dev/tags=cloud, gcs

🌡️  Status

STARTED        DURATION    STATUS
19 hours ago   54s         Succeeded

⚓ Params

 NAME                   VALUE
 ∙ location             gs://tekton-releases/pipeline/latest
 ∙ path                 v0.52.0
 ∙ serviceAccountPath   release.json

📂 Workspaces

 NAME            SUB PATH   WORKSPACE BINDING
 ∙ credentials   ---        Secret (secret=release-secret)
 ∙ source        bucket     PersistentVolumeClaim (claimName=pvc-0a188c7d6b-affinity-assistant-1bb04eb4f2-0)

🦶 Steps

 NAME       STATUS
 ∙ upload   Completed

@vdemeester
Copy link
Member

cc @afrittoli who has been looking at this on Friday. Latest should point to 0.52 now, but we still need to fix the release pipeline somehow.

@afrittoli
Copy link
Member

The release pipeline was fixed in #7146

@afrittoli
Copy link
Member

@jimmyjones2 Thanks again for reporting this, I will close it now, feel free to re-open should anything be missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

6 participants