Skip to content

CNF-21346: Add latest tag to on-push builds#609

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-kni:mainfrom
fontivan:sskeard/cnf-21346-add-latest-tag
Mar 9, 2026
Merged

CNF-21346: Add latest tag to on-push builds#609
openshift-merge-bot[bot] merged 1 commit intoopenshift-kni:mainfrom
fontivan:sskeard/cnf-21346-add-latest-tag

Conversation

@fontivan
Copy link
Copy Markdown
Contributor

@fontivan fontivan commented Mar 6, 2026

  • The latest tag is helpful to avoid having to go look up whatever the most recent push is
  • Only apply it to the on-push build as we don't want every PR updating latest
  • The build pipeline already has the additional tags parameter configured, so we just need to add the values

@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

@fontivan: This pull request references CNF-21346 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

  • The latest tag is helpful to avoid having to go look up whatever the most recent push is
  • Only apply it to the on-push build as we don't want every PR updating latest

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from rauhersu and shajmakh March 6, 2026 13:59
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fontivan

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

@fontivan: This pull request references CNF-21346 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

  • The latest tag is helpful to avoid having to go look up whatever the most recent push is
  • Only apply it to the on-push build as we don't want every PR updating latest
  • The build pipeline already has the additional tags parameter configured, so we just need to add the values

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 openshift-eng/jira-lifecycle-plugin repository.

@fontivan
Copy link
Copy Markdown
Contributor Author

fontivan commented Mar 6, 2026

@abraham2512
Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 9, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 7782718 into openshift-kni:main Mar 9, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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.

3 participants