[JIRA] [publish-over-ssh-plugin] (JENKINS-29360) Bump jsch to fix Algorithm negotiation failed

2015-07-11 Thread egore...@egore911.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph B created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29360 
 
 
 
  Bump jsch to fix Algorithm negotiation failed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 bap 
 
 
 

Components:
 

 publish-over-ssh-plugin 
 
 
 

Created:
 

 11/Jul/15 6:45 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Christoph B 
 
 
 
 
 
 
 
 
 
 
Recent OpenSSH servers running on ubuntu use the following key exchange algorithms 

 

KexAlgorithms curve25519-sha...@libssh.org,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
 

 
When using the current version (1.13) which uses jsch 0.1.45 the plugin will fail with the message Algorithm negotiation failed. Bumping the dependency to 0.1.53 solves the problem as i.e. diffie-hellman-group-exchange-sha256 was enabled by default in 0.1.51. 
I rebuilt the 1.13 version with jsch 0.1.53 and it works fine on our Jenkins cluster. Please bump this dependency. 
 
 
 
 
 
 
 
 
 
 
 
 

   

[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client

2013-03-14 Thread egore...@egore911.de (JIRA)














































Christoph B
 commented on  JENKINS-17195


InvalidTagNameException with version 1.0.4 of git client















This is pretty severe to me. Our complete build system stopped running because all of our 250 projects are prefixed by a text and followed by a space. Please repair this.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client

2013-03-14 Thread egore...@egore911.de (JIRA)














































Christoph B
 commented on  JENKINS-17195


InvalidTagNameException with version 1.0.4 of git client















I'm not going to disable the internal tagging temporarily by changing the configuration of 250 projects 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-15571) hudson-jacoco-plugin crashes if jacoco didn't run

2013-03-04 Thread egore...@egore911.de (JIRA)














































Christoph B
 commented on  JENKINS-15571


hudson-jacoco-plugin crashes if jacoco didnt run















Yes, the configuration is fine.

Let me gibe you a better example of how it happens: When a build process failed (e.g. due to a compile error in some java class or an error when downloading a maven dependency) and the maven-jacoco-plugin will not be executed you end up with a pretty empty target folder, which is also missing jacoco/classes.

It's basically a followup error.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-15571) hudson-jacoco-plugin crashes if jacoco didn't run

2012-10-18 Thread egore...@egore911.de (JIRA)














































Christoph B
 created  JENKINS-15571


hudson-jacoco-plugin crashes if jacoco didnt run















Issue Type:


Bug



Assignee:


Ognjen Bubalo



Components:


jacoco



Created:


18/Oct/12 3:00 PM



Description:


Right now the hudson-jacoco-plugin will crash if it is invoked atfter the build is done and the build didn't run jacoco. It should rather gracefully do nothing.

The following exception occours:


java.io.FileNotFoundException: /jacoco/classes (No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.init(FileInputStream.java:137)
	at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:181)
	at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:110)
	at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:116)




Project:


Jenkins



Priority:


Major



Reporter:


Christoph B

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira