-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
We have an application A that is dependent on another, application B. During the build, application A pulls in the latest version of application B's binaries. Application A always has to be rebuilt after application B. However, the branch from which application A gets built isn't always the same. (There are four branches that could need to be rebuilt: develop, release/minor, release/major, and master.)
The job is configured to build every branch (i.e. its branch specifier is "origin/**").
When I click the "Force Build" button, I'd like the ability to choose what branch to force a build on. Currently, Jenkins rebuilds on the branch of the last build.
Our current solution is to commit a fake/dummy change to the branch that needs to get rebuilt. This has created a lot of extra commits in our repository's history.