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

Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'

      Under the Git Plugin Advanced setting, I have 'Gerrit Trigger' set for choosing strategy, but occasionally, this gets reset back to Default, which doesn't default to Gerrit Trigger. This can let bad builds get through my build system because the build essentially doesn't pick up the bad changeset.

      Doesn't happen on all projects at the same time that have this setting enabled, just a few projects. Quite random and strange.

          [JENKINS-15674] Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'

          Joel Kamentz added a comment -

          I'm seeing this on Windows 7. Seems more likely to happen, upon Jenkins restart. Not necessarily all restarts (or perhaps only those which truly kill and restart the process/service) – I've seen Jenkins self-restart and not lose the setting.

          Really grasping at straws, but Jenkins does sometimes report an issue with inscrutable data, which appears to be related to CVS plugin and passwords. But, we're using git, not CVS, so this may not be related.

          Joel Kamentz added a comment - I'm seeing this on Windows 7. Seems more likely to happen, upon Jenkins restart. Not necessarily all restarts (or perhaps only those which truly kill and restart the process/service) – I've seen Jenkins self-restart and not lose the setting. Really grasping at straws, but Jenkins does sometimes report an issue with inscrutable data, which appears to be related to CVS plugin and passwords. But, we're using git, not CVS, so this may not be related.

          Roland Schulz added a comment - - edited

          We see this too. It results in a test to fail with:

          ERROR: Couldn't find any revision to build.
          Verify the repository and branch configuration for this job.

          For us it also happens sporadically and not reproducible.

          Roland Schulz added a comment - - edited We see this too. It results in a test to fail with: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. For us it also happens sporadically and not reproducible.

          I've had this happen... it happened for me when configuring an unrelated section and saving.

          Andrew Erickson added a comment - I've had this happen... it happened for me when configuring an unrelated section and saving.

          rsandell added a comment -

          A similar thing happens for me on the Warnings Plugin, the settings for what parsers to use sometimes defaults back to the first available setting, it could be unrelated.
          Do you have similar issues as well?

          What core version and git plugin versions do you use?

          rsandell added a comment - A similar thing happens for me on the Warnings Plugin, the settings for what parsers to use sometimes defaults back to the first available setting, it could be unrelated. Do you have similar issues as well? What core version and git plugin versions do you use?

          Roland Schulz added a comment -

          I've never noticed it for the Warnings Plugin. We use 1.486 with 1.1.26.

          Roland Schulz added a comment - I've never noticed it for the Warnings Plugin. We use 1.486 with 1.1.26.

          Vivek Ayer added a comment -

          What core version and git plugin versions do you use?

          We use 1.481 with 1.1.23.

          Vivek Ayer added a comment - What core version and git plugin versions do you use? We use 1.481 with 1.1.23.

          Joel Kamentz added a comment -

          1.491 with 1.1.26

          Joel Kamentz added a comment - 1.491 with 1.1.26

          Currently on 1.499 with 1.1.25, but I haven't seen it happen in awhile (maybe I just haven't been editing my GerritTrigger jobs though...).

          Andrew Erickson added a comment - Currently on 1.499 with 1.1.25, but I haven't seen it happen in awhile (maybe I just haven't been editing my GerritTrigger jobs though...).

            Unassigned Unassigned
            vsayer Vivek Ayer
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: