-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
CentOS 6.3
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.
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.