chore: reduce trigger job build retention from 100 to 10#1461
Open
chore: reduce trigger job build retention from 100 to 10#1461
Conversation
Test Results 506 files 506 suites 7m 21s ⏱️ Results for commit 7f5bf42. ♻️ This comment has been updated with latest results. |
Coverage Report
|
Trigger jobs are lightweight — they only kick off the composite build. Keeping 100 builds of history per branch is excessive. Align with the platform standard of 10 builds for trigger jobs.
marregui
force-pushed
the
chore/reduce-trigger-build-retention
branch
from
975c460 to
7f5bf42
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
numToKeepStrfrom100to10in trigger jobCompositeJenkinsfileandmodules/hivemq-edge-module-opcua/CompositeJenkinsfileLinear: EDG-285