#1705: jenkins triggers release build on changes in master ---------------------+------------------------------------------------------ Reporter: knarf | Owner: Type: defect | Status: closed Priority: minor | Milestone: Component: Other | Version: development version Resolution: fixed | Keywords: ---------------------+------------------------------------------------------ Changes (by hinder):

* status: new => closed * resolution: => fixed

Comment:

Thanks for spotting this. It turns out that I had set up the release branch of the super-repository wrongly. The initial version was using the release, but I hadn't added the release branches to the .gitmodules file, so every update was coming from master! I have now added the branch information, so the super-repo release branch is actually tracking the release. Looking at the latest Jenkins build log, it appears to have done the right thing.