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

Use release tag for release automation #125

Closed
wants to merge 1 commit into from

Conversation

clobrano
Copy link
Contributor

Current PR bundle automation is using main branch, while it should use
the tagged commit instead.

Current PR bundle automation is using main branch, while it should use
the tagged commit instead.

Signed-off-by: Carlo Lobrano <c.lobrano@gmail.com>
Copy link
Contributor

openshift-ci bot commented Feb 15, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented Feb 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: clobrano

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

@@ -55,6 +55,7 @@ jobs:
export VERSION=${VERSION}
export PREVIOUS_VERSION=${PREVIOUS_VERSION}
export SKIP_RANGE_LOWER=${SKIP_RANGE_LOWER}
git -C operator checkout v${VERSION}
Copy link
Member

Choose a reason for hiding this comment

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

Can it maybe done in the earlier step of Checkout code?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It could but

  1. It needs another token (it can be the same used later)
  2. I wasn't able to make the actions/checkout ref parameter dynamic. It works if I write
- name: Checkout code
  uses: actions/checkout@v3
  with:
      path: operator
      ref: v0.3.0
      fetch-depth: 0

but whatever other variable I tried for the tag name, it took it litteraly (e.g. ${VERSION}, ${{ inputs.version }}, etc.)

Copy link
Member

Choose a reason for hiding this comment

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

Ok, then no need to further investigate that :D

Copy link
Member

@slintes slintes Feb 15, 2024

Choose a reason for hiding this comment

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

wait, you select the branch / tag in the action's UI, right? It doesn't checkout the selected ref then?

Copy link
Member

Choose a reason for hiding this comment

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

image

Copy link
Contributor Author

@clobrano clobrano Feb 16, 2024

Choose a reason for hiding this comment

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

I missed that selector, thanks!
At the moment I can't test, but let's keep this on hold since it might be unnecessary

image

@razo7
Copy link
Member

razo7 commented Feb 15, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Feb 15, 2024
@clobrano clobrano marked this pull request as ready for review February 15, 2024 14:41
@clobrano
Copy link
Contributor Author

clobrano commented Feb 15, 2024 via email

@slintes
Copy link
Member

slintes commented Feb 15, 2024

/hold

@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@clobrano
Copy link
Contributor Author

clobrano commented Mar 8, 2024

Closing this as unnecessary. The right branch/tag can be selected via workflow UI

@clobrano clobrano closed this Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants