Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-69499

gerrit trigger plugin behaves badly when ws-cleanup is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None

      Hi, 

      We have a pretty ennoying bug in our CICD system in my company.

      I've set the Jira to Critical. You may want to review that.

       

      Here are the details:

       

      [Context]

      I have a Freestyle job with 2 string parameters:
      GERRIT_BRANCH=master

      GERRIT_REFSPEC=refs/heads/master

      SCM / git configuration: see gerrit_trigger_config.png. Important thing here is that I use Strategy for choosing what to build / Gerrit Trigger

       

      [OBSERVATIONS]

      If I keep Delete workspace before build starts disabled, the git syncs exactly the head of master.

      If I enable Delete workspace before build starts, then the git syncs some old commit but not the head (in my case from February).

      As we are heavilly using ws-cleanup and gerrit-trigger, this is a huge issue for us.

       

      One thing I noticed, if I add an empty EXCLUDE and an empty INCLUDE patterns in Delete workspace before build starts advanced configuration, then the git sync works as expected. However in that configuration, the workspace doesn't get cleaned up at the start of the build.

       

      FYI, I can repro on latest Jenkins too (version 2.346.3).

       

      Please suggest any configuration I can do to workaround this until that gets fixed. 

      Also, if you need anything else, let me know. 

      Thanks in advance !

            olivergondza Oliver Gondža
            tiribar Thierry Barthelemy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: