Skip to content
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.

Stop rerunning create jobs on non-generation bumping updates #2307

Merged
merged 1 commit into from
Nov 1, 2023

Conversation

thedadams
Copy link
Contributor

If an app is updated in such a way that the generation is not bumped (e.g. an annotation or label is add/removed/modified), then any job that is create-only would rerun if the generation of the app is 1. This change ensures that create-only jobs will not be rerun in this instance.

Checklist

  • The title of this PR would make a good line in Acorn's Release Note's Changelog
  • The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
  • All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
  • Commits follow contributing guidance
  • Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
  • Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
  • PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)

If an app is updated in such a way that the generation is not bumped
(e.g. an annotation or label is add/removed/modified), then any job that
is create-only would rerun if the generation of the app is 1. This
change ensures that create-only jobs will not be rerun in this instance.

Signed-off-by: Donnie Adams <donnie@acorn.io>
@thedadams thedadams merged commit 555acb0 into acorn-io:main Nov 1, 2023
4 checks passed
@thedadams thedadams deleted the no-create-rerun branch November 1, 2023 14:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants