Skip to content
This repository was archived by the owner on Dec 1, 2022. It is now read-only.

Download nightly build manifest when version is CI#1201

Merged
openshift-ci[bot] merged 2 commits into
mainfrom
fix-ci
Aug 4, 2022
Merged

Download nightly build manifest when version is CI#1201
openshift-ci[bot] merged 2 commits into
mainfrom
fix-ci

Conversation

@nak3
Copy link
Copy Markdown

@nak3 nak3 commented Aug 3, 2022

#1191 changed to download the manifest from https://github.com/knative/$component/releases/download/knative-$release_suffix/$file but the nightly build does not exist in the URL.

This patch fixes it.

@nak3
Copy link
Copy Markdown
Author

nak3 commented Aug 3, 2022

current error:

00:35:12  ++ basename ./test/test_images/multicontainer/sidecarcontainer
00:35:12  + local image_base=sidecarcontainer
00:35:12  + mkdir -p openshift/ci-operator/knative-test-images/sidecarcontainer
00:35:12  + bin=sidecarcontainer
00:35:12  + envsubst
00:35:12  ./openshift/release/generate-release.sh ci
00:35:12  Writing resolved yaml to openshift/release/knative-serving-ci.yaml
00:35:12  --2022-08-02 20:35:12--  https://github.com/knative/serving/releases/download/knative-c0/serving-crds.yaml
00:35:12  Resolving github.com (github.com)... 140.82.113.3
00:35:12  Connecting to github.com (github.com)|140.82.113.3|:443... connected.
00:35:12  HTTP request sent, awaiting response... 404 Not Found
00:35:12  2022-08-02 20:35:12 ERROR 404: Not Found.

@openshift-ci openshift-ci Bot requested review from alanfx and skonto August 3, 2022 05:03
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2022
@skonto
Copy link
Copy Markdown

skonto commented Aug 3, 2022

@nak3
Ok missed that we call generate-release with ci when we cut the branch, good catch. However we dont need to download the nightly files just skip them because they are not going to be used by the S-O or anywhere. S-O will not fetch them at all and actually we are going to override the files under artifacts dir since we have multiple calls here https://github.com/openshift/knative-serving/blob/main/openshift/release/create-release-branch.sh#L18-L19 that will call download_release_artifacts multiple times.
The artifacts dir should only contain the release files the S-O is going to get when running openshift-knative-operator/hack/update-manifests.sh.
So if release == "ci' let's skip calling download_release_artifacts here.

Maybe the right place to add download_release_artifacts call is not in the generate-release file but in create-release-branch.sh directly and call it once there. As a side note it is also confusing that we call make generate-release four times in create-release-branch.sh.

@nak3
Copy link
Copy Markdown
Author

nak3 commented Aug 3, 2022

Thank you @skonto I will close this PR so would you mind opening the PR as you wanted to change?
I can add the line in https://github.com/openshift/knative-serving/blob/main/openshift/release/generate-release.sh#L12 to skip calling it but maybe you want to change more?

@skonto
Copy link
Copy Markdown

skonto commented Aug 3, 2022

I can add the line in https://github.com/openshift/knative-serving/blob/main/openshift/release/generate-release.sh#L12 to skip calling it

Yes please do. Let's add that line and we can clean up when we unify manifest generation as a next step we have some internal technical debt there.

@skonto
Copy link
Copy Markdown

skonto commented Aug 4, 2022

/lgtm

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Aug 4, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nak3, skonto

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:

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

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2022
@openshift-ci openshift-ci Bot merged commit db6615d into main Aug 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants