Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
Jenkins 1.421 + Git plugin 1.1.10
Note that I have to trigger manually this build as it has JENKINS-10386 but I don't think there is a real relation between them
Description
The project is here : https://github.com/exoportal/exogtn
We have 2 main branches : master = 3.1.x and 3.2.x branch
I have several jenkins jobs for each branch
Several times we noticed that in jobs configured for 3.1.x (master) , jenkins built sources from 3.2.x 
I attach a screenshot of my configuration of this job : https://ci.exoplatform.org/job/gatein-portal-3.1.x-exo-pkg
Branch specifier is set to origin/master.
If we look at the history of its builds :
https://ci.exoplatform.org/job/gatein-portal-3.1.x-exo-pkg/67/ => 3.2.x
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Using strategy: Default
Last Built Revision: Revision c5e0dadd718190ac5048291cae5ecbbd9afc73fe (origin/master)
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Fetching changes from 1 remote Git repository
Fetching upstream changes from git://github.com/exoportal/exogtn.git
Pruning obsolete local branches
Commencing build of Revision e9a51a044611c9add919d74f7271d8eab0125b44 (origin/master)
Checking out Revision e9a51a044611c9add919d74f7271d8eab0125b44 (origin/master)
Cleaning workspace
No emails were triggered.
https://ci.exoplatform.org/job/gatein-portal-3.1.x-exo-pkg/68/ => 3.1.x 
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Using strategy: Default
Last Built Revision: Revision e9a51a044611c9add919d74f7271d8eab0125b44 (origin/master)
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Fetching changes from 1 remote Git repository
Fetching upstream changes from git://github.com/exoportal/exogtn.git
Pruning obsolete local branches
Commencing build of Revision 692f33bbeafe2643a5874ed1f5ff26ed49b3f78f (origin/master)
Checking out Revision 692f33bbeafe2643a5874ed1f5ff26ed49b3f78f (origin/master)
Cleaning workspace
https://ci.exoplatform.org/job/gatein-portal-3.1.x-exo-pkg/69/ => 3.2.x
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Using strategy: Default
Last Built Revision: Revision 692f33bbeafe2643a5874ed1f5ff26ed49b3f78f (origin/master)
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Fetching changes from 1 remote Git repository
Fetching upstream changes from git://github.com/exoportal/exogtn.git
Pruning obsolete local branches
Commencing build of Revision e9a51a044611c9add919d74f7271d8eab0125b44 (origin/master)
Checking out Revision e9a51a044611c9add919d74f7271d8eab0125b44 (origin/master)
Cleaning workspace
No emails were triggered.
https://ci.exoplatform.org/job/gatein-portal-3.1.x-exo-pkg/70/ => 3.1.x
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Using strategy: Default
Last Built Revision: Revision e9a51a044611c9add919d74f7271d8eab0125b44 (origin/master)
Checkout:workspace / /home/swfhudson/data/jobs/gatein-portal-3.1.x-exo-pkg/workspace - hudson.remoting.LocalChannel@129a4ed
Fetching changes from 1 remote Git repository
Fetching upstream changes from git://github.com/exoportal/exogtn.git
Pruning obsolete local branches
Commencing build of Revision 692f33bbeafe2643a5874ed1f5ff26ed49b3f78f (origin/master)
Checking out Revision 692f33bbeafe2643a5874ed1f5ff26ed49b3f78f (origin/master)
Cleaning workspace
No emails were triggered.
Perhaps we have a wrong usage of git in this project, as I didn't yet noticed such issue for others git projects we have but It is a big issue for us to not be able to build the good branch
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
Activity
So when you went to git, clicked the second "Advanced" button the "Wipe out workspace before build" was not checked?
Did you have any other options checked that aren't set by default?
I activated the option "Clean after checkout" and "Prune branches" after having discovered the issue and it didn't help.
This is fixed in the emergency 1.1.11 release. We rolled back changes to DefaultBuildChooser that broke horribly in any case where you weren't using "**" as the branch spec. Yeesh.
I our case, the jobs were we saw this problem were not wiping out the workspace.