Re: log4j version in jenkins.war is too old
Bump? Anyone? On Wednesday, November 7, 2012 9:26:22 PM UTC+4, Ivan Kalinin wrote: Hi, people! I bumped into a problem with some third-party libraries (namely, dasein-cloud-nimbula) that I am trying to use within a plugin. The library depends on log4j version no less than 1.2.15, but jenkins.war contains 1.2.9 that has classpath precedence over one supplied in plugin (or I guess so). That conflict causes *java.lang.NoSuchMethodError: org.apache.log4j.Logger.isTraceEnabled()Z* errors due to the method absent in 1.2.9. mvn depency:tree points that log4j dependency comes from a * org.acegisecurity.acegi-security* dependency in core/pom.xml, put pom for the acegi-security contains no version specification in log4j dependency. see herehttp://repo1.maven.org/maven2/org/acegisecurity/acegi-security/1.0.5/acegi-security-1.0.5.pom My questions are: 1. can log4j in Jenkins be promoted to the latest version? If so, I could create a pull request as soon as someone points me the way to do it. 2. how can I override that dependency problem in my plugin's pom.xml? Maybe, thats not a problem at all. Testbed that gives me the error is *mvn hpi:run* in my plugin dev project. TY for any help or hints.
Re: Single email notification from a muti-configuration project
You can ask for email-ext plugin feature on Jenkins JIRA, or implement this. On Friday, November 9, 2012 9:29:44 AM UTC+2, Chai wrote: We currently use email-ext plugin for enabling email notifications on builds. We see that the users are receiving mutiple notifications if the project is configured as a muti-configuration project. Is there a way to send a single email instead. Jenkins version1.404 Email-ext version 2.14 Thanks Chaitanya
Re: log4j version in jenkins.war is too old
Hi Ivan, you should be able to add an exclusion of log4j to your declaration of *org.acegisecurity.acegi-security * as per http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html cheers Tim On 9 November 2012 08:44, Ivan Kalinin pupss...@gmail.com wrote: Bump? Anyone? On Wednesday, November 7, 2012 9:26:22 PM UTC+4, Ivan Kalinin wrote: Hi, people! I bumped into a problem with some third-party libraries (namely, dasein-cloud-nimbula) that I am trying to use within a plugin. The library depends on log4j version no less than 1.2.15, but jenkins.war contains 1.2.9 that has classpath precedence over one supplied in plugin (or I guess so). That conflict causes *java.lang.NoSuchMethodError: org.apache.log4j.Logger.isTraceEnabled()Z* errors due to the method absent in 1.2.9. mvn depency:tree points that log4j dependency comes from a * org.acegisecurity.acegi-security* dependency in core/pom.xml, put pom for the acegi-security contains no version specification in log4j dependency. see herehttp://repo1.maven.org/maven2/org/acegisecurity/acegi-security/1.0.5/acegi-security-1.0.5.pom My questions are: 1. can log4j in Jenkins be promoted to the latest version? If so, I could create a pull request as soon as someone points me the way to do it. 2. how can I override that dependency problem in my plugin's pom.xml? Maybe, thats not a problem at all. Testbed that gives me the error is *mvn hpi:run* in my plugin dev project. TY for any help or hints. -- Tim Pizey http://pizey.net/~timp
Re: Moving Plugins to github
2012/11/9 Christopher Orr ch...@orr.me.uk Hi there, On 08/11/12 18:53, Thomas Fürer wrote: Would someone by so kind and help me with moving my plugins from svn to github? thinbackup (https://svn.jenkins-ci.org/**trunk/hudson/plugins/** thinBackup/ https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/ ) owner at github: tofuatgit, alienllama Normally SVN plugins are already in GitHub, but I couldn't find this one, so I guess somebody more familiar with the migration process needs to help out. I'll run a svn - git conversion for this one. silktestsuite (https://svn.jenkins-ci.org/**trunk/hudson/plugins/**silktestsuite/https://svn.jenkins-ci.org/trunk/hudson/plugins/silktestsuite/ ) owner at github: tofuatgit This repo is already in GitHub; I think you should have access here: https://github.com/jenkinsci/**silktestsuite-pluginhttps://github.com/jenkinsci/silktestsuite-plugin Regards, Chris
Re: Moving Plugins to github
done : https://github.com/jenkinsci/thin-backup-plugin also created CI job on https://jenkins.ci.cloudbees.com/job/plugins/job/thin-backup-plugin/ 2012/11/9 nicolas de loof nicolas.del...@gmail.com 2012/11/9 Christopher Orr ch...@orr.me.uk Hi there, On 08/11/12 18:53, Thomas Fürer wrote: Would someone by so kind and help me with moving my plugins from svn to github? thinbackup (https://svn.jenkins-ci.org/**trunk/hudson/plugins/** thinBackup/https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/ ) owner at github: tofuatgit, alienllama Normally SVN plugins are already in GitHub, but I couldn't find this one, so I guess somebody more familiar with the migration process needs to help out. I'll run a svn - git conversion for this one. silktestsuite (https://svn.jenkins-ci.org/**trunk/hudson/plugins/**silktestsuite/https://svn.jenkins-ci.org/trunk/hudson/plugins/silktestsuite/ ) owner at github: tofuatgit This repo is already in GitHub; I think you should have access here: https://github.com/jenkinsci/**silktestsuite-pluginhttps://github.com/jenkinsci/silktestsuite-plugin Regards, Chris
Re: Moving Plugins to github
I committed a README on svn to document the move also, created a wiki page https://wiki.jenkins-ci.org/display/JENKINS/Thin+Backup+Plugin, please document this plugin 2012/11/9 nicolas de loof nicolas.del...@gmail.com done : https://github.com/jenkinsci/thin-backup-plugin also created CI job on https://jenkins.ci.cloudbees.com/job/plugins/job/thin-backup-plugin/ 2012/11/9 nicolas de loof nicolas.del...@gmail.com 2012/11/9 Christopher Orr ch...@orr.me.uk Hi there, On 08/11/12 18:53, Thomas Fürer wrote: Would someone by so kind and help me with moving my plugins from svn to github? thinbackup (https://svn.jenkins-ci.org/**trunk/hudson/plugins/** thinBackup/https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/ ) owner at github: tofuatgit, alienllama Normally SVN plugins are already in GitHub, but I couldn't find this one, so I guess somebody more familiar with the migration process needs to help out. I'll run a svn - git conversion for this one. silktestsuite (https://svn.jenkins-ci.org/**trunk/hudson/plugins/**silktestsuite/https://svn.jenkins-ci.org/trunk/hudson/plugins/silktestsuite/ ) owner at github: tofuatgit This repo is already in GitHub; I think you should have access here: https://github.com/jenkinsci/**silktestsuite-pluginhttps://github.com/jenkinsci/silktestsuite-plugin Regards, Chris
Re: Moving Plugins to github
Hey Nicolas, You've never seen the thinBackup plugin before? ;) https://wiki.jenkins-ci.org/display/JENKINS/Thinbackup Chris On 09/11/12 13:11, nicolas de loof wrote: I committed a README on svn to document the move also, created a wiki page https://wiki.jenkins-ci.org/display/JENKINS/Thin+Backup+Plugin, please document this plugin 2012/11/9 nicolas de loof nicolas.del...@gmail.com mailto:nicolas.del...@gmail.com done : https://github.com/jenkinsci/thin-backup-plugin also created CI job on https://jenkins.ci.cloudbees.com/job/plugins/job/thin-backup-plugin/ 2012/11/9 nicolas de loof nicolas.del...@gmail.com mailto:nicolas.del...@gmail.com 2012/11/9 Christopher Orr ch...@orr.me.uk mailto:ch...@orr.me.uk Hi there, On 08/11/12 18:53, Thomas Fürer wrote: Would someone by so kind and help me with moving my plugins from svn to github? thinbackup (https://svn.jenkins-ci.org/__trunk/hudson/plugins/__thinBackup/ https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/) owner at github: tofuatgit, alienllama Normally SVN plugins are already in GitHub, but I couldn't find this one, so I guess somebody more familiar with the migration process needs to help out. I'll run a svn - git conversion for this one. silktestsuite (https://svn.jenkins-ci.org/__trunk/hudson/plugins/__silktestsuite/ https://svn.jenkins-ci.org/trunk/hudson/plugins/silktestsuite/) owner at github: tofuatgit This repo is already in GitHub; I think you should have access here: https://github.com/jenkinsci/__silktestsuite-plugin https://github.com/jenkinsci/silktestsuite-plugin Regards, Chris
Re: Moving Plugins to github
OH, sorry for that :-/ I don't know how to remove this page from wiki. Can edit, move, not delete... 2012/11/9 Christopher Orr ch...@orr.me.uk Hey Nicolas, You've never seen the thinBackup plugin before? ;) https://wiki.jenkins-ci.org/**display/JENKINS/Thinbackuphttps://wiki.jenkins-ci.org/display/JENKINS/Thinbackup Chris On 09/11/12 13:11, nicolas de loof wrote: I committed a README on svn to document the move also, created a wiki page https://wiki.jenkins-ci.org/**display/JENKINS/Thin+Backup+**Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Thin+Backup+Plugin, please document this plugin 2012/11/9 nicolas de loof nicolas.del...@gmail.com mailto:nicolas.deloof@gmail.**com nicolas.del...@gmail.com done : https://github.com/jenkinsci/**thin-backup-pluginhttps://github.com/jenkinsci/thin-backup-plugin also created CI job on https://jenkins.ci.cloudbees.**com/job/plugins/job/thin-** backup-plugin/https://jenkins.ci.cloudbees.com/job/plugins/job/thin-backup-plugin/ 2012/11/9 nicolas de loof nicolas.del...@gmail.com mailto:nicolas.deloof@gmail.**com nicolas.del...@gmail.com 2012/11/9 Christopher Orr ch...@orr.me.uk mailto: ch...@orr.me.uk Hi there, On 08/11/12 18:53, Thomas Fürer wrote: Would someone by so kind and help me with moving my plugins from svn to github? thinbackup (https://svn.jenkins-ci.org/__**trunk/hudson/plugins/__** thinBackup/https://svn.jenkins-ci.org/__trunk/hudson/plugins/__thinBackup/ https://svn.jenkins-ci.org/**trunk/hudson/plugins/** thinBackup/ https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/ ) owner at github: tofuatgit, alienllama Normally SVN plugins are already in GitHub, but I couldn't find this one, so I guess somebody more familiar with the migration process needs to help out. I'll run a svn - git conversion for this one. silktestsuite (https://svn.jenkins-ci.org/__**trunk/hudson/plugins/__** silktestsuite/https://svn.jenkins-ci.org/__trunk/hudson/plugins/__silktestsuite/ https://svn.jenkins-ci.org/**trunk/hudson/plugins/** silktestsuite/https://svn.jenkins-ci.org/trunk/hudson/plugins/silktestsuite/ ) owner at github: tofuatgit This repo is already in GitHub; I think you should have access here: https://github.com/jenkinsci/_**_silktestsuite-pluginhttps://github.com/jenkinsci/__silktestsuite-plugin https://github.com/jenkinsci/**silktestsuite-pluginhttps://github.com/jenkinsci/silktestsuite-plugin Regards, Chris
Re: Moving Plugins to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 this can normally only be done by an confluence but thanks a lot for your help guys! thomas Am 09.11.2012 15:07, schrieb nicolas de loof: OH, sorry for that :-/ I don't know how to remove this page from wiki. Can edit, move, not delete... 2012/11/9 Christopher Orr ch...@orr.me.uk mailto:ch...@orr.me.uk Hey Nicolas, You've never seen the thinBackup plugin before? ;) https://wiki.jenkins-ci.org/__display/JENKINS/Thinbackup https://wiki.jenkins-ci.org/display/JENKINS/Thinbackup Chris On 09/11/12 13:11, nicolas de loof wrote: I committed a README on svn to document the move also, created a wiki page https://wiki.jenkins-ci.org/__display/JENKINS/Thin+Backup+__Plugin https://wiki.jenkins-ci.org/display/JENKINS/Thin+Backup+Plugin, please document this plugin 2012/11/9 nicolas de loof nicolas.del...@gmail.com mailto:nicolas.del...@gmail.com mailto:nicolas.deloof@gmail.__com mailto:nicolas.del...@gmail.com done : https://github.com/jenkinsci/__thin-backup-plugin https://github.com/jenkinsci/thin-backup-plugin also created CI job on https://jenkins.ci.cloudbees.__com/job/plugins/job/thin-__backup-plugin/ https://jenkins.ci.cloudbees.com/job/plugins/job/thin-backup-plugin/ 2012/11/9 nicolas de loof nicolas.del...@gmail.com mailto:nicolas.del...@gmail.com mailto:nicolas.deloof@gmail.__com mailto:nicolas.del...@gmail.com 2012/11/9 Christopher Orr ch...@orr.me.uk mailto:ch...@orr.me.uk mailto:ch...@orr.me.uk mailto:ch...@orr.me.uk Hi there, On 08/11/12 18:53, Thomas Fürer wrote: Would someone by so kind and help me with moving my plugins from svn to github? thinbackup (https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/ https://svn.jenkins-ci.org/__trunk/hudson/plugins/__thinBackup/ https://svn.jenkins-ci.org/__trunk/hudson/plugins/__thinBackup/ https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/) owner at github: tofuatgit, alienllama Normally SVN plugins are already in GitHub, but I couldn't find this one, so I guess somebody more familiar with the migration process needs to help out. I'll run a svn - git conversion for this one. silktestsuite (https://svn.jenkins-ci.org/trunk/hudson/plugins/silktestsuite/ https://svn.jenkins-ci.org/__trunk/hudson/plugins/__silktestsuite/ https://svn.jenkins-ci.org/__trunk/hudson/plugins/__silktestsuite/ https://svn.jenkins-ci.org/trunk/hudson/plugins/silktestsuite/) owner at github: tofuatgit This repo is already in GitHub; I think you should have access here: https://github.com/jenkinsci/silktestsuite-plugin https://github.com/jenkinsci/__silktestsuite-plugin https://github.com/jenkinsci/__silktestsuite-plugin https://github.com/jenkinsci/silktestsuite-plugin Regards, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQnQ7nAAoJEMIrIJt+IWiiTzwH/39kQn7/dtAppBhIXx5CsuSF ja5KzoFvQSTuKfcG4avs8IKzit0rsP2RlOk4fk88vqi8A3mDdReJpsQT0PQGP3Vw M61TKRPnRLfb8vzRHLUuGqZsOHFuFp7kpPnaNWKvKMA3gXqevQietL6CJSgejwhJ HDEworbati3eQPvUL0x+9IySer7No6WNXrRe7SODS0yLPfBCznFhcSIZ9ZodeMby FmAxgCt0lQiAzsgOryJU8yyxYNigs2pEuRO5guXprHLD6EzL9Dz14Dmfd5oU1DEg eeAW5hchhQxkn5bWmsJrPd1J/+fdT4CPcXVWHT4Wdzupf69CRPIUUv7SCC0ZqXE= =TLxw -END PGP SIGNATURE-
Re: revert to esx snapshot in build step
got it done finally just waiting to publish onto github On Thursday, October 18, 2012 9:45:15 AM UTC-5, xterm wrote: i am a first time poster and first time plugin creator. i am trying to create a plugin to revert an esx vm to a snapshot during the build step. I have everything working up to the point where i commit the launch but when i try and perform the 'setChannel' i get this: runtimeexception: java.io.EOFException: unexpected stream termination because of this line: vsSlave.setChannel(new BufferedInputStream(System.in), new BufferedOutputStream(System.out), listener.getLogger(), null); i guess i am not doing something right but i am not sure how to make it right. the documentation says to run setChannel after launch to let hudson/jenkins know of the etablished connection and to tie inputstream to slave.jar but im not sure how to do this. i believe that if i do this correctly, the channel will be synced and i wont get the following error if this line is not included. if i dont include the setchannel in the code, i get another run time exception: channelalreadyclosed exception. --xterm