-
Bug
-
Resolution: Fixed
-
Major
-
Linux Ubuntu 13.04
Apache Tomcat/7.0.35
Jenkins 1.549
git-client plugin 1.6.2
GitLab 6.1.0
Gitlab is running on the same linux server under a different sub-domain & different linux user name.
When I upgraded the git-client plugin from 1.6.1 to 1.6.2, a project now builds every time it polls the SCM (a GitLab repo) even if the version hash is identical.
Some jobs indicate that there is a problem and "could not remove the credential section from the git configuration" (see below polling log sample). But even these jobs build on every SCM poll even when the git version has has not changed. Below, I have 8 builds in a row that all reference the same revision, and all say "changes found."
======================
Started on Feb 4, 2014 5:53:33 PM
Using strategy: Default
[poll] Last Built Revision: Revision 1c8eda4fa98b092973c7dfe3b3c1d6c859971922 (origin/MASTER)
using .gitcredentials to set credentials
Could not remove the credential section from the git configuration
Done. Took 0.52 sec
Changes found
[JENKINS-21652] Building at each git-client polling interval even when no changes present
| Environment |
Original:
Jenkins 1.549 on linux server git-client plugin 1.6.2 Gitlab running on same server (different sub-domain name & different linux user name). build nodes are windows machines connected via JNLP |
New:
Linux Ubuntu 13.04 Apache Tomcat/7.0.35 Jenkins 1.549 git-client plugin 1.6.2 GitLab 6.1.0 Gitlab is running on the same linux server under a different sub-domain & different linux user name. |
Would you be willing to install a more verbose logging unreleased version of git-client-plugin to help isolate the problem? I think the polling may be hiding an exception (possibly hinted by the "could not remove the credential section", but there are several places in that polling code which might throw the exception and a more verbose logging plugin would help isolate which case you're seeing.
That more verbose git-client-plugin doesn't exist yet. I'll only create it if you're willing to use it to diagnose the problem further.
Absolutely!
Just point me to where to get it, or alternately, give me the repo URL and the maven build command and I'll build it.
If you can build the branch https://github.com/MarkEWaite/git-plugin/tree/proto-additional-logging-in-GitSCM , that adds a few additional log messages in the area of code where I think things are most likely to be failing.
Ignore previous version of this comment.
Build succeeded, which .jars / artifacts that were built are needed for this custom git-client-plugin? Forgive my ignorance, I've never installed a custom compiled plugin before.
==============================
[INFO] Installing c:\dev\jenkins\workspace\Git-Client-Plugin\target\git.hpi to C:\.m2\repository\org\jenkins-ci\plugins\git\2.0.2-SNAPSHOT\git-2.0.2-SNAPSHOT.hpi
[INFO] Installing c:\dev\jenkins\workspace\Git-Client-Plugin\pom.xml to C:\.m2\repository\org\jenkins-ci\plugins\git\2.0.2-SNAPSHOT\git-2.0.2-SNAPSHOT.pom
[INFO] Installing c:\dev\jenkins\workspace\Git-Client-Plugin\target\git.jar to C:\.m2\repository\org\jenkins-ci\plugins\git\2.0.2-SNAPSHOT\git-2.0.2-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20.998s
[INFO] Finished at: Wed Feb 05 19:56:18 MST 2014
[INFO] Final Memory: 45M/505M
[INFO] ------------------------------------------------------------------------
Finished: SUCCESS
When polling a GitHub project (which is outside of the system that hosts jenkins), polling correctly identifies that no changes have been found.
GitHub project: https://github.com/jenkinsci/jenkins.git
This does not seem to matter if a github credential is supplied or if the project is polled anonymously.