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

feat(dogfood): use cancel-in-progress/path-change #1831

Conversation

chmouel
Copy link
Member

@chmouel chmouel commented Nov 25, 2024

Added cancel-in-progress annotation to multiple Tekton YAML files to ensure that in-progress pipeline runs are canceled when new runs are triggered. Use on-path-change and on-target-event annotations to as well for path change.

Changes

Submitter Checklist

  • 📝 Please ensure your commit message is clear and informative. For guidance on crafting effective commit messages, refer to the How to write a git commit message guide. We prefer the commit message to be included in the PR body itself rather than a link to an external website (ie: Jira ticket).

  • ♽ Before submitting a PR, run make test lint to avoid unnecessary CI processing. For an even more efficient workflow, consider installing pre-commit and running pre-commit install in the root of this repository.

  • ✨ We use linters to maintain clean and consistent code. Please ensure you've run make lint before submitting a PR. Some linters offer a --fix mode, which can be executed with the command make fix-linters (ensure markdownlint and golangci-lint tools are installed first).

  • 📖 If you're introducing a user-facing feature or changing existing behavior, please ensure it's properly documented.

  • 🧪 While 100% coverage isn't a requirement, we encourage unit tests for any code changes where possible.

  • 🎁 If feasible, please check if an end-to-end test can be added. See README for more details.

  • 🔎 If there's any flakiness in the CI tests, don't necessarily ignore it. It's better to address the issue before merging, or provide a valid reason to bypass it if fixing isn't possible (e.g., token rate limitations).

@chmouel chmouel force-pushed the use-new-cancel-in-progress-path-change branch 2 times, most recently from 4e9e58f to ea2777e Compare November 25, 2024 13:58
@chmouel
Copy link
Member Author

chmouel commented Nov 25, 2024

/retest

1 similar comment
@chmouel
Copy link
Member Author

chmouel commented Nov 25, 2024

/retest

Copy link

codecov bot commented Nov 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.38%. Comparing base (2f78eb8) to head (42cbfec).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1831      +/-   ##
==========================================
+ Coverage   65.35%   65.38%   +0.03%     
==========================================
  Files         177      177              
  Lines       13692    13704      +12     
==========================================
+ Hits         8949     8961      +12     
  Misses       4141     4141              
  Partials      602      602              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

Added `cancel-in-progress` annotation to multiple Tekton YAML files to
ensure that in-progress pipeline runs are canceled when new runs are
triggered. Use `on-path-change` and `on-target-event` annotations to as
well for path change.

Signed-off-by: Chmouel Boudjnah <[email protected]>
Rephrase the policy section remove the part about Gitea since it's not
supported and don't give the sense if it is.

Signed-off-by: Chmouel Boudjnah <[email protected]>
@chmouel chmouel force-pushed the use-new-cancel-in-progress-path-change branch from ea2777e to bd23308 Compare November 27, 2024 11:25
@chmouel chmouel merged commit fd6a243 into openshift-pipelines:main Nov 27, 2024
4 checks passed
@chmouel chmouel deleted the use-new-cancel-in-progress-path-change branch November 27, 2024 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant