-
Bug
-
Resolution: Fixed
-
Major
-
None
-
In this case: Jenkins 1.536 (Jenkins version doesn't really matter :) running on Linux(CentOS6.4) respectively MacOSX(Mavericks)
Plugins: git v 2.0, git-client 1.4.6
When using the git plugin 2.0 and git-client plugin 1.4.6 the connection to a remote git repository via https fails.
Using a connection URL like https://<user>:<password>@<URL> I receive a "failed to connect" where the connection URL was reduced to https://<user>@<URL> - where of course was clear why it failed: The password wasn't submitted !?
Reverting to versions 1.5.0 (git) respectively 1.0.7 (git-client) and a Jenkins restart solved it. Keeping one of both plugins on the newer version and only downgrading the other produced another symptom: The GIT was no longer available for configuration in Jenkins. So there's a dependency between both plugins.
The "million-dollar-question" is: Is this a bug in those plugins? Or or do they simply need to be handled/configured differently. I didn't find any hint on this so far ..
Again: No offense - BUT ...
If your "use model" is to use Jenkins interactively, and believe that this is the intended way to use Jenkins then you must have got it wrong.
JENKINS IS ALL ABOUT USING IT AS A SERVICE.
Jenkins is supposed to run on some (if you want to put it this way) "background server", doing tasks like
additionally it can
etc.
And it's supposed to do all this with NO INTERACTION required!
If you don't get this concept - and do not accept that this is the main usage of Jenkins - then you are definitely on a wrong path !
Sorry ...