Details
-
Suggestion
-
Resolution: Duplicate
-
None
Description
Currently, our workflow includes two types of builds:
- Pipelines builds that are set up to check the code quality.
- Pipelines builds that are set up to test our software.
We always run both and, even though the "test builds" run successfully our "code quality builds" can fail and, due to the feature "Check the last commit for at least x successful build and no failed builds" we are not able to merge our changes.
We would like to request this functionality to be slipt in two:
- Check the last commit for at least x successful build
- Check the last commit for no failed builds
For now, we are using as a workaround the API call to update the build status to Successful but we would really appreciate have this option split.
Attachments
Issue Links
- duplicates
-
BCLOUD-15258 Split "no failed builds" requirement into its own branch permission
- Gathering Interest