[JIRA] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Gabriel Lopez updated an issue Jenkins / JENKINS-34117 java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Change By: Gabriel Lopez Teamconcert fails to checking check out code when the builds are requested from RTC.This is due to changes in Jenkins 1.655, specifically in JENKINS-33467 and [this commit|https://github.com/jenkinsci/jenkins/commit/4adee7597aad7a338db8d3eb320575ae618a8c81].There , it is mentioned that some plugins break due to the new changes , and need to be changed. Teamconcert has suffers the same issue,it assumes that CauseAction.getCauses is not inmutable , in [this line|https://github.com/jenkinsci/teamconcert-plugin/blob/master/com.ibm.team.build.hjplugin/src/main/java/com/ibm/team/build/internal/hjplugin/RTCScm.java#L1158].[See fix|https://github.com/Diabol/delivery-pipeline-plugin/commit/541cca5f10d2c3419a10514f61aa9d238a01d6e4] from another plugin.Please fix it ASAP, as we can't update jenkins. Full stacktrace:RTC : checkout...RTC : Build initiated by request from RTCFATAL: RTC : checkout failure: nulljava.lang.UnsupportedOperationExceptionat java.util.Collections$UnmodifiableCollection.add(Collections.java:1075)at com.ibm.team.build.internal.hjplugin.RTCScm.checkout(RTCScm.java:1158)at hudson.scm.SCM.checkout(SCM.java:485)at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)at hudson.model.Run.execute(Run.java:1738)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:410)ERROR: RTC : checkout failure: null Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34121) IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3
Title: Message Title
Gabriel Lopez updated an issue
Jenkins / JENKINS-34121
IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3
Change By:
Gabriel Lopez
It is not possible to run slaves anymore using IBM Java.This is due to the new [encrypted communication|https://issues.jenkins-ci.org/browse/JENKINS-26580] introduced in Jenkins 1.653, where the handshake is done [using "AES/CTR/PKCS5Padding"|https://github.com/jenkinsci/remoting/blob/master/src/main/java/org/jenkinsci/remoting/engine/HandshakeCiphers.java#L109]. I couldn't find what ciphers IBM Java does or doesn't support (maybe nothing else than the [default ones|https://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.security.api.doc/jce/javax/crypto/Cipher.html]), but I created a quick test to check . See (see below ) .Would it be possible to switch to a cipher supported by IBM Java? * Test: * import java.security.NoSuchAlgorithmException;import javax.crypto.Cipher;import javax.crypto.NoSuchPaddingException; public class PaddingIssue { private static final String CIPHER = "AES/CTR/PKCS5Padding"; public static void main(String[] args) throws NoSuchAlgorithmException, NoSuchPaddingException {Cipher encryptCipher = Cipher.getInstance(CIPHER);System.out.println("Fine!"); }} * Executions: * IBM JAVA 1.6/usr/lib/j2re1.6-ibm/jre/bin/java PaddingIssue Exception in thread "main" java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES/CTR/PKCS5Padding at javax.crypto.Cipher.getInstance(Unknown Source) at PaddingIssue.main(PaddingIssue.java:10)Caused by: javax.crypto.NoSuchPaddingException: CTR mode must be used with ISO10126Padding or NoPadding at com.ibm.crypto.provider.AESCipher.engineSetPadding(Unknown Source) at javax.crypto.Cipher$a.a(Unknown Source) ... 2 moreIBM JAVA 1.7/usr/lib/j2re1.7-ibm/jre/bin/java PaddingIssue Exception in thread "main" java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES/CTR/PKCS5Padding at javax.crypto.Cipher.getInstance(Unknown Source) at PaddingIssue.main(PaddingIssue.java:10)Caused by: javax.crypto.NoSuchPaddingException: CTR mode must be used with ISO10126Padding or NoPadding at com.ibm.crypto.provider.AESCipher.engineSetPadding(Unknown Source) at javax.crypto.Cipher$a.a(Unknown Source) ... 2 moreIBM JAVA 1.8/usr/lib/jvm/java-ibm-x86_64-80/jre/bin/java PaddingIssue Exception in thread "main" java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES/CTR/PKCS5Padding at javax.crypto.Cipher.getInstance(Unknown Source) at PaddingIssue.main(PaddingIssue.java:10)Caused by: javax.crypto.NoSuchPaddingException: CTR mode must be used with ISO10126Padding or NoPadding at com.ibm.crypto.provider.AbstractBufferingCipher.engineSetPadding(Unknown Source) at javax.crypto.Cipher$a.a(Unknown Source) ... 2 moreOpenJDK 7/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java PaddingIssue Fine! * Full stacktrace: * Mar 22, 2016 3:54:13 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP3-connectMar 22, 2016 3:54:14 PM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: Failed to create handshake ciphersjava.lang.AssertionError: Failed to create handshake ciphersat org.jenkinsci.remoting.engine.HandshakeCiphers.create(HandshakeCiphers.java:116)
[JIRA] [core] (JENKINS-34121) IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3
Title: Message Title
Gabriel Lopez created an issue
Jenkins / JENKINS-34121
IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Apr/08 11:07 AM
Priority:
Major
Reporter:
Gabriel Lopez
It is not possible to run slaves anymore using IBM Java.
This is due to the new encrypted communication introduced in Jenkins 1.653, where the handshake is done using "AES/CTR/PKCS5Padding".
I couldn't find what ciphers IBM Java does or doesn't support (maybe nothing else than the default ones), but I created a quick test to check. See below.
Would it be possible to switch to a cipher supported by IBM Java?
Test: import java.security.NoSuchAlgorithmException; import javax.crypto.Cipher; import javax.crypto.NoSuchPaddingException;
public class PaddingIssue { private static final String CIPHER = "AES/CTR/PKCS5Padding";
public static void main(String[] args) throws NoSuchAlgorithmException, NoSuchPaddingException { Cipher encryptCipher = Cipher.getInstance(CIPHER); System.out.println("Fine!"); }
}
Executions: IBM JAVA 1.6 /usr/lib/j2re1.6-ibm/jre/bin/java PaddingIssue Exception in thread "main" java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES/CTR/PKCS5Padding at javax.crypto.Cipher.getInstance(Unknown Source) at PaddingI
[JIRA] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Gabriel Lopez updated an issue Jenkins / JENKINS-34117 java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Change By: Gabriel Lopez Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Gabriel Lopez created an issue Jenkins / JENKINS-34117 java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Issue Type: Bug Assignee: Unassigned Components: teamconcert-plugin Created: 2016/Apr/08 9:38 AM Priority: Critical Reporter: Gabriel Lopez Teamconcert fails to checking out code when the builds are requested from RTC. This is due to changes in Jenkins 1.655, specifically in JENKINS-33467 and this commit. There is mentioned that some plugins break due to the new changes and need to be changed. Teamconcert has the same issue,it assumes that CauseAction.getCauses is not inmutable, in this line. See fix from another plugin. Please fix it ASAP, as we can't update jenkins. Full stacktrace: RTC : checkout... RTC : Build initiated by request from RTC FATAL: RTC : checkout failure: null java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection.add(Collections.java:1075) at com.ibm.team.build.internal.hjplugin.RTCScm.checkout(RTCScm.java:1158) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.Abstr
[JIRA] [teamconcert-plugin] (JENKINS-30245) Missing Credentials in Global Team Concert/RTC configuration
Title: Message Title Gabriel Lopez commented on JENKINS-30245 Re: Missing Credentials in Global Team Concert/RTC configuration After the 1.1.9.8 update, this issue seems to be resolved (at least for me): Seems to be this fix: Jenkins Plugin v1.1.9.7 doesn't save the credentials of the global RTC configuration (Manage Jenkins) https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375688 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-30245) Missing Credentials in Global Team Concert/RTC configuration
Title: Message Title Gabriel Lopez commented on JENKINS-30245 Re: Missing Credentials in Global Team Concert/RTC configuration Hi. I had the same issue; RTC global credentials didn't get saved: You selected one credentials, save or apply, everything went fine, but then you refresh the page and the credentials aren't selected anymore. On the XML configuration on the server, the ID saved was Github's.com plain credentials, an OAuth token configured through https://wiki.jenkins-ci.org/display/JENKINS/Plain+Credentials+Plugin. After several tests, I disabled plain credentials plugin (and Github plugin, since it depends on it), restarted the server and then they it worked fine again. So, I think there is a compatibility issue with Plain Credentials plugin and Rational Team Concert global config. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
