Recently we has a checkin trigger a build for another branch. So we have branch.Old and branch.New. The jenkin jobs for branch.New is a clones of the old branch with change in the perforce client view mapping. The builds have been working for almost a month no problems. Today a dev checked into the new branch and jenkins triggered an old build sending out failure email. The client path map to the build branch in the build log, so it does not makes sense why the old branch triggered.
We are currently using the perforce and Jenkins version after release 1.70 <but not the latest>. Has anyone seen this before? Does anyone know what might have caused this problem? Thanks, Mark -- View this message in context: http://jenkins.361315.n4.nabble.com/Checkin-triggers-the-wrong-build-to-execute-tp4637817.html Sent from the Jenkins issues mailing list archive at Nabble.com.
