-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
3
-
7
-
Problem Description:
Specs update events are considered builds, but they do not generate artifacts. This can flood the build history and cause artifact-generating builds to be deleted earlier than intended, because of the configured the number of builds to keep.
Suggested Solution:
Add a setting to toggle the Specs update events to be considered a build.
- causes
-
BAM-20213 Keep the previous latest build result during expiry if the latest build only have specs build
-
- Closed
-
- is duplicated by
-
BAM-20519 Remove Spec scan result from dashboard
- Closed
- mentioned in
-
Page Loading...
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
[BAM-20149] Add option to have Specs update events to NOT be considered as a build
Support reference count | New: 7 |
UIS | Original: 31 | New: 3 |
UIS | Original: 3 | New: 31 |
Remote Link | New: This issue links to "Page (Confluence)" [ 971875 ] |
UIS | Original: 4 | New: 3 |
UIS | Original: 3 | New: 4 |
Remote Link | New: This issue links to "Page (Confluence)" [ 867695 ] |
UIS | Original: 4 | New: 3 |
UIS | Original: 35 | New: 4 |
UIS | Original: 2 | New: 35 |