[JIRA] [swarm] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
Rene Kok created JENKINS-24149 LogConfigurationException due to conflicting commons-logging versions Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm Created: 07/Aug/14 9:43 AM Description: We run a Maven type job using Jenkins version 1.565.1. When building on master, the job builds fine. When using a swarm client, the job fails with the following error shown in the console log: ... at org.kohsuke.stapler.Stapler.clinit(Stapler.java:1062) ... 51 more Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) ... 56 more Caused by: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) ... 57 more channel stopped Environment: LTS 1.565.1 Project: Jenkins Priority: Critical Reporter: Rene Kok 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/d/optout.
[JIRA] [swarm] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
Rene Kok commented on JENKINS-24149 LogConfigurationException due to conflicting commons-logging versions We found a workaround by patching swarm-client-1.16-jar-with-dependencies.jar: We removed the commons-logging dependency and replaced it with the classes from commons-logging-1.1.3 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/d/optout.
[JIRA] [swarm] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
Rene Kok
edited a comment on JENKINS-24149
LogConfigurationException due to conflicting commons-logging versions
We found a workaround by patching swarm-client-1.16-jar-with-dependencies.jar:
We removed the commons-logging dependency and replaced it with the classes from commons-logging-1.1.3
mkdir /tmp/swarm-client /tmp/commons-logging
cd /tmp/swarm-client
curl --silent -o swarm-client-1.16-jar-with-dependencies.jar http://${OUR_REPOSITORY}/jcenter/org/jenkins-ci/plugins/swarm-client/1.16/swarm-client-1.16-jar-with-dependencies.jar
unzip swarm-client-1.16-jar-with-dependencies.jar
cd /tmp/commons-logging
curl --silent -o commons-logging-1.1.3.jar http://${OUR_REPOSITORY}/jcenter/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar
unzip commons-logging-1.1.3.jar
mv /tmp/swarm-client/org/apache/commons/logging/ org/apache/commons/logging.NOTUSED
mv /tmp/commons-logging/org/apache/commons/logging/ /tmp/swarm-client/org/apache/commons
cd /tmp/swarm-client
rm swarm-client-1.16-jar-with-dependencies.jar
zip -r swarm-client-1.16-portbase-jar-with-dependencies.jar hudson jenkins META-INF org
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/d/optout.
[JIRA] [swarm] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
Rene Kok
edited a comment on JENKINS-24149
LogConfigurationException due to conflicting commons-logging versions
We found a workaround by patching swarm-client-1.16-jar-with-dependencies.jar:
We removed the commons-logging dependency and replaced it with the classes from commons-logging-1.1.3
mkdir /tmp/swarm-client /tmp/commons-logging
cd /tmp/swarm-client
curl --silent -o swarm-client-1.16-jar-with-dependencies.jar http://${OUR_REPOSITORY}/jcenter/org/jenkins-ci/plugins/swarm-client/1.16/swarm-client-1.16-jar-with-dependencies.jar
unzip swarm-client-1.16-jar-with-dependencies.jar
cd /tmp/commons-logging
curl --silent -o commons-logging-1.1.3.jar http://${OUR_REPOSITORY}/jcenter/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar
unzip commons-logging-1.1.3.jar
mv /tmp/swarm-client/org/apache/commons/logging/ /tmp/swarm-client/org/apache/commons/logging.NOTUSED
mv /tmp/commons-logging/org/apache/commons/logging/ /tmp/swarm-client/org/apache/commons
cd /tmp/swarm-client
rm swarm-client-1.16-jar-with-dependencies.jar
zip -r swarm-client-1.16-portbase-jar-with-dependencies.jar hudson jenkins META-INF org
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/d/optout.
[JIRA] [swarm] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
Rene Kok
edited a comment on JENKINS-24149
LogConfigurationException due to conflicting commons-logging versions
We found a workaround by patching swarm-client-1.16-jar-with-dependencies.jar:
We removed the commons-logging dependency and replaced it with the classes from commons-logging-1.1.3
mkdir /tmp/swarm-client /tmp/commons-logging
cd /tmp/swarm-client
curl --silent -o swarm-client-1.16-jar-with-dependencies.jar http://${OUR_REPOSITORY}/jcenter/org/jenkins-ci/plugins/swarm-client/1.16/swarm-client-1.16-jar-with-dependencies.jar
unzip swarm-client-1.16-jar-with-dependencies.jar
cd /tmp/commons-logging
curl --silent -o commons-logging-1.1.3.jar http://${OUR_REPOSITORY}/jcenter/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar
unzip commons-logging-1.1.3.jar
mv /tmp/swarm-client/org/apache/commons/logging/ /tmp/swarm-client/org/apache/commons/logging.NOTUSED
mv /tmp/commons-logging/org/apache/commons/logging/ /tmp/swarm-client/org/apache/commons
cd /tmp/swarm-client
rm swarm-client-1.16-jar-with-dependencies.jar
zip -r swarm-client-1.16-MODIFIED-jar-with-dependencies.jar hudson jenkins META-INF org
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/d/optout.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Rene Kok commented on JENKINS-20492 Re-Execute promotion button is gone Fix promoted-builds-2.18-20140807.061532-2.hpi worked for me. thanks. 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/d/optout.
[JIRA] [swarm] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
Rene Kok commented on JENKINS-24149 LogConfigurationException due to conflicting commons-logging versions This is still an issue with Jenkins LTS version 1.565.3 and Swarm plugin 1.19 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/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Rene Kok commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails We are using BitBucket cloud. Our scan bitbucket over 100+repositories randomly fails because the API rate limit is reached (https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html). With the current implementation of the plugin we can do nothing but wait one hour (rate limit is measured per hour) and then try again to recover the lost build jobs. I.m.o. the request rate can be reduced a lot (preventing hitting the API rate limit) if the scan logic is changed to only add jobs or branches that do not exist yet. A separate scan could do nightly cleanups of removed branches/repositories. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Rene Kok edited a comment on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails We are using BitBucket cloud. Our scan bitbucket over 100+repositories randomly fails because the API rate limit is reached (https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html). With the current implementation of the plugin we can do nothing but wait one hour (rate limit is measured per hour) and then try again to recover the lost build jobs.I.m.o. the request rate can be reduced a lot (preventing hitting the API rate limit) if the scan logic is changed to only add jobs or branches that do not exist yet. A separate scan could do nightly cleanups of removed branches/repositories. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
