feat: upload release manifests to oracle cloud #9121

anithapriyanatarajan · 2025-11-03T04:01:59Z

Changes

This PR incorporates the listed changes to ensure Tekton's nightly release artifacts are stored and published using Oracle Cloud for future releases.

Switched release artifact storage from GCS (gs://...) to Oracle Cloud (tekton-nightly), updating default bucket names and related descriptions in both .github/workflows/nightly-builds.yaml and tekton/release-pipeline.yaml.
Updated workflow to use oracle cloud credentials (OCI_API_KEY, OCI_FINGERPRINT, etc.) from workflow secrets instead of GCS service account keys, and changed secret creation logic accordingly.
Changed Git authentication secret to use basic-auth type for compatibility with the Git resolver.
Added a new repoName parameter to both the workflow and pipeline for improved artifact organization, and passed

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
Has Tests included if any functionality added or changed
pre-commit Passed
Follows the commit message standard
Meets the Tekton contributor standards (including functionality, content, code)
Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

/kind feat

tekton-robot · 2025-11-03T04:02:01Z

@anithapriyanatarajan: The label(s) kind/feat cannot be applied, because the repository doesn't have them.

Details

In response to this:

Changes

This PR incorporates the listed changes to ensure Tekton's nightly release artifacts are stored and published using Oracle Cloud for future releases.

Switched release artifact storage from GCS (gs://...) to Oracle Cloud (tekton-releases-nightly), updating default bucket names and related descriptions in both .github/workflows/nightly-builds.yaml and tekton/release-pipeline.yaml.

Updated workflow to use oracle cloud credentials (OCI_API_KEY, OCI_FINGERPRINT, etc.) from workflow secrets instead of GCS service account keys, and changed secret creation logic accordingly.

Changed Git authentication secret to use basic-auth type for compatibility with the Git resolver.

Added a new repoName parameter to both the workflow and pipeline for improved artifact organization, and passed

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps

Has Tests included if any functionality added or changed

pre-commit Passed

Follows the commit message standard

Meets the Tekton contributor standards (including functionality, content, code)

Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep

Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.

Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE
/kind feat

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

anithapriyanatarajan · 2025-11-03T04:02:59Z

/kind misc

tekton-robot · 2025-11-03T04:03:01Z

@anithapriyanatarajan: The label(s) kind/chore cannot be applied, because the repository doesn't have them.

Details

In response to this:

/kind chore

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

anithapriyanatarajan · 2025-11-03T04:03:29Z

/kind misc

anithapriyanatarajan · 2025-11-03T04:14:36Z

@afrittoli @vdemeester - The following assumptions were made for this PR.

Oracle cloud bucket name for nightlies: tekton-nightly
Folder structure would remain the same as earlier tekton-nightly/<pipeline>/previous/<v2025mmdd-xxxxxxx/ & tekton-nightly/<pipeline>/latest/
Auth credentails to access the buckets shall be configured as workflow secrets - OCI_API_KEY, OCI_FINGERPRINT, OCI_TENANCY_OCID, OCI_USER_OCID, OCI_REGION in the pipelines repository workflow secrets for actions.
The resulting manifest download url based on latest releases is echoed as BASE_URL="https://infra.tekton.dev/tekton-nightly/${REPO_NAME}/previous/${VERSION_TAG}".

anithapriyanatarajan · 2025-11-03T06:06:03Z

/retest

AlanGreene · 2025-11-03T10:50:21Z

.github/workflows/nightly-builds.yaml

+        description: 'Oracle Cloud bucket name for builds'
        required: false
-        default: 'gs://tekton-releases-nightly/pipeline'
+        default: 'tekton-releases-nightly'


This should be tekton-nightly for the new OCI bucket

Thankyou. Resubmitted with updated bucket name. But the GHCR imageRegistryPath -https://github.com/anithapriyanatarajan/pipeline/blob/865d2ff9b6646475a5efd759fdac888d9072ce90/tekton/release-pipeline.yaml#L21 is still the same. Hope this is fine.

AlanGreene · 2025-11-03T11:35:50Z

tekton/release-pipeline.yaml

+              # Format: https://infra.tekton.dev/tekton-nightly/<repoName>/previous/<versionTag>
+              BASE_URL="https://infra.tekton.dev/tekton-nightly/${REPO_NAME}/previous/${VERSION_TAG}"


These should use releaseBucket to construct the correct URL since this pipeline is also used for official releases.

This was overlooked. Thankyou for pointing out

AlanGreene · 2025-11-03T11:38:44Z

.github/workflows/nightly-builds.yaml

-        description: 'Nightly bucket for builds'
+        description: 'Oracle Cloud bucket name for builds'
        required: false
-        default: 'gs://tekton-releases-nightly/pipeline'


Is there a particular reason for removing the repo name from the bucket config and making it a separate param?

This pipeline should always publish to <bucket>/pipeline so making it configurable seems unusual, unless we're planning to use this as a template for a generic pipeline that can be reused across multiple repos. In which case, I think there are likely many other changes that would be required so each repo can customise the pipeline to their needs, and would require careful design before implementing.

In Oracle cloud, I was not able to pass the bucket name as /pipeline. Hence introduced a new param called reponame and pass as object prefix. https://github.com/anithapriyanatarajan/pipeline/blob/865d2ff9b6646475a5efd759fdac888d9072ce90/.github/workflows/nightly-builds.yaml#L24

afrittoli · 2025-11-03T13:16:00Z

@afrittoli @vdemeester - The following assumptions were made for this PR.

Oracle cloud bucket name for nightlies: tekton-nightly

Yes, the bucket name is tekton-nightly

Folder structure would remain the same as earlier tekton-nightly/<pipeline>/previous/<v2025mmdd-xxxxxxx/ & tekton-nightly/<pipeline>/latest/

Yes, it's the same. This is one example item:

    {
      "archival-state": null,
      "etag": "f23b3042-c0d1-4998-a58d-afffd9e1159c",
      "md5": "ktmoZ5lniEJH7PRApoPbRg==",
      "name": "add-pr-body-ci/previous/v20250110-55b6235b28/release.notags.yaml",
      "size": 2968,
      "storage-tier": "Standard",
      "time-created": "2025-09-29T10:31:26.913000+00:00",
      "time-modified": "2025-09-29T10:31:26.913000+00:00"
    },

Auth credentails to access the buckets shall be configured as workflow secrets - OCI_API_KEY, OCI_FINGERPRINT, OCI_TENANCY_OCID, OCI_USER_OCID, OCI_REGION in the pipelines repository workflow secrets for actions.

+1

The resulting manifest download url based on latest releases is echoed as BASE_URL="https://infra.tekton.dev/tekton-nightly/${REPO_NAME}/previous/${VERSION_TAG}".

+1

anithapriyanatarajan · 2025-11-04T06:04:57Z

/retest

savitaashture · 2025-11-04T07:32:33Z

/retest

waveywaves · 2025-11-04T07:59:06Z

/retest

afrittoli · 2025-11-04T09:07:38Z

/retest

afrittoli · 2025-11-04T14:34:16Z

/retest

afrittoli

/approve

AlanGreene

Thanks @anithapriyanatarajan

tekton-robot · 2025-11-04T17:28:56Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli, AlanGreene

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [afrittoli]

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

vdemeester · 2025-11-04T20:37:20Z

/lgtm

github-project-automation bot added this to Tekton Community Roadmap Nov 3, 2025

tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Nov 3, 2025

github-project-automation bot moved this to Todo in Tekton Community Roadmap Nov 3, 2025

tekton-robot requested review from dibyom and pritidesai November 3, 2025 04:02

tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 3, 2025

tekton-robot added the kind/misc Categorizes issue or PR as a miscellaneuous one. label Nov 3, 2025

anithapriyanatarajan force-pushed the change-upload-target branch 2 times, most recently from 8ecc2a7 to c89de24 Compare November 3, 2025 06:31

AlanGreene suggested changes Nov 3, 2025

View reviewed changes

anithapriyanatarajan force-pushed the change-upload-target branch from 0975d60 to 865d2ff Compare November 3, 2025 11:01

anithapriyanatarajan requested a review from AlanGreene November 3, 2025 11:14

AlanGreene reviewed Nov 3, 2025

View reviewed changes

feat: upload release manifests to oracle cloud

933ab09

anithapriyanatarajan force-pushed the change-upload-target branch from dd67593 to 933ab09 Compare November 3, 2025 14:14

afrittoli reviewed Nov 4, 2025

View reviewed changes

tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 4, 2025

AlanGreene approved these changes Nov 4, 2025

View reviewed changes

tekton-robot assigned vdemeester Nov 4, 2025

tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 4, 2025

tekton-robot merged commit 866a4a5 into tektoncd:main Nov 4, 2025
120 of 132 checks passed

github-project-automation bot moved this from Todo to Done in Tekton Community Roadmap Nov 4, 2025

waveywaves mentioned this pull request Dec 17, 2025

ci: cherry pick CI fixes to 1.3.0 and 1.6.0 #9243

Closed

12 tasks

		# Format: https://infra.tekton.dev/tekton-nightly/<repoName>/previous/<versionTag>
		BASE_URL="https://infra.tekton.dev/tekton-nightly/${REPO_NAME}/previous/${VERSION_TAG}"

feat: upload release manifests to oracle cloud #9121

feat: upload release manifests to oracle cloud #9121

Uh oh!

Conversation

anithapriyanatarajan commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Submitter Checklist

Release Notes

Uh oh!

tekton-robot commented Nov 3, 2025

Changes

Submitter Checklist

Release Notes

Uh oh!

anithapriyanatarajan commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tekton-robot commented Nov 3, 2025

Uh oh!

anithapriyanatarajan commented Nov 3, 2025

Uh oh!

anithapriyanatarajan commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anithapriyanatarajan commented Nov 3, 2025

Uh oh!

AlanGreene Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

anithapriyanatarajan Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

AlanGreene Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

anithapriyanatarajan Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

AlanGreene Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

anithapriyanatarajan Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

afrittoli commented Nov 3, 2025

Uh oh!

anithapriyanatarajan commented Nov 4, 2025

Uh oh!

savitaashture commented Nov 4, 2025

Uh oh!

waveywaves commented Nov 4, 2025

Uh oh!

afrittoli commented Nov 4, 2025

Uh oh!

afrittoli commented Nov 4, 2025

Uh oh!

afrittoli left a comment

Choose a reason for hiding this comment

Uh oh!

AlanGreene left a comment

Choose a reason for hiding this comment

Uh oh!

tekton-robot commented Nov 4, 2025

Uh oh!

vdemeester commented Nov 4, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

anithapriyanatarajan commented Nov 3, 2025 •

edited

Loading

anithapriyanatarajan commented Nov 3, 2025 •

edited

Loading

anithapriyanatarajan commented Nov 3, 2025 •

edited

Loading