-
Bug
-
Resolution: Fixed
-
Minor
-
None
The `Automatic branch project triggering » Branch names to build automatically` property was a hack.
The correct way to implement that feature would be using a BranchBuildStrategy as that will correctly suppress. We should remove the property... the correct path to removal will look something like this:
- Create an extension plugin for Branch API that implements at least BranchBuildStrategy based on matching the branch name
- Add a migration to Branch API that removes the NoTriggerBranchProperty property and replaces it with the BranchBuildStrategy (by magic, as we cannot have circular dependencies)
- Add some magic that auto-installs the branch build strategy plugin only if the migration is needed (so that regular users are not confused by more configuration options until they install the plugins enabling same)
What we'll probably have to do is more complex:
- Create an extension point to migrate the NoTriggerBranchProperty (no implementations in branch-api
- Create an administrative monitor that alerts to install the branch build strategy plugin if a migration is required
- Disable adding the NoTriggerBranchProperty via the UI, but allow maintaining an existing configuration
- At some future date, remove the NoTriggerBranchProperty entirely
- is blocked by
-
JENKINS-48792 A branch build strategy that only builds named branches
- Closed
- relates to
-
JENKINS-54864 github multibranch builds fail to build with latest branch api update
- Resolved
- links to