Wow. We are hitting the very same problem with the last Git plugin at the
piblish step.
Could you bring up more info? For example, what's auth. profile and what
are the git version used?
On Tuesday, December 17, 2013 7:51:45 PM UTC+4, slide wrote:
I recently upgraded my Git plugin and have
Looks like this is due to a bug:
https://issues.jenkins-ci.org/browse/JENKINS-21110
On Tuesday, December 17, 2013 7:51:45 PM UTC+4, slide wrote:
I recently upgraded my Git plugin and have started getting the following
error:
Pushing tag DB2013-12-17_05-35-37 to repo origin
ERROR: Failed
FYI, I ended up just moving the tagging and pushing of the tag into a shell
command to get around this for now.
On Wed, Dec 25, 2013 at 2:05 PM, Ivan Kalinin pupss...@gmail.com wrote:
Looks like this is due to a bug:
https://issues.jenkins-ci.org/browse/JENKINS-21110
On Tuesday, December
Did you guys get a solution for this issue.
Thanks,
Bala
On Sunday, September 23, 2012 9:52:02 PM UTC+8, Ramesh Ankam wrote:
Hello Group,
I installed Jenkins 1.4.x on Linux/Tomcat6. We have our code base in
GitHub, we are unable to get clone the workspace for public and private
GitHub
Since the message was sent 15 months ago, I assume they found a solution.
Is there a reason you asked a question checking the status of question
opened 15 months ago?
In case others see the problem, I would first check if a correct path is
configured for the git command. The command should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SOLVED!
While browsing changelogs of various plugins, I stumbled over the
following entries in the changelog of the Maven plugin (v2.1 as of Dec
17 2013):
- - Fixed: Maven plugin sends email to 'null' adress issue #20209
- - Fixed: Hacks used by
