RE: m2release 0.10.0 (Not yet released) - duedate
Hi Marcus, There are a couple of outstanding pull requests that I need to pull in before the release - one of which is for a defect with the release builds to keep. -1 as a default doesn't make sense (it is really 0 as you are marking zero builds to keep). If there are any features you would like that are missing the best way is to create a pull request and a JIRA issue. Regards, /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Marcus Vinicius Sent: 03 January 2013 11:08 To: jenkinsci-us...@googlegroups.com; jenkinsci-dev@googlegroups.com Subject: m2release 0.10.0 (Not yet released) - duedate Hello, I'm interessted at release 0.10.0 of m2reelase plugin. I built from source code and tried it. I have the suggestions below about the Fix Add ability to specify number of release builds to keep: - As can you see at image there is a error when you click on help image: Failed to load help image: Not found - Default number of successful release builds to keep to -1. What is the due date to perform 0.10.0 release? I'm a java developer how could i help this plugin project? [cid:image001.png@01CDE9AB.ACA227C0] -- Marcus Vinicius A. Silva P ANTES DE IMPRIMIR pense em sua responsabilidade e compromisso com o MEIO AMBIENTE. ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** inline: image001.png
RE: gerrit-trigger-plugin build errors
You will ned to install as the checkstyle config is contained within the same project as you are building. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of John Hsing Sent: 19 December 2012 10:56 To: jenkinsci-dev@googlegroups.com Subject: Re: gerrit-trigger-plugin build errors And i cloned latest codes from github(master branch) 在 2012年12月19日星期三UTC+8下午6时54分54秒，John Hsing写道： I use this comand: mvn package to build this plugin, but i got these erros: [INFO] [INFO] Building Gerrit Events 1.4.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-enforcer-plugin:1.0:display-info (default) @ gerrit-events --- [INFO] Maven Version: 3.0.4 [INFO] JDK Version: 1.6.0_37 normalized as: 1.6.0-37 [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 3.4.11-2.16-desktop [INFO] [INFO] --- maven-localizer-plugin:1.12:generate (default) @ gerrit-events --- [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ gerrit-events --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /work/jenkins-dev/plugins/gerrit-trigger-plugin/gerrit-events/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ gerrit-events --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-license-plugin:1.7:process (default) @ gerrit-events --- [INFO] Generated /work/jenkins-dev/plugins/gerrit-trigger-plugin/gerrit-events/target/gerrit-events/WEB-INF/licenses.xml [INFO] [INFO] --- maven-checkstyle-plugin:2.8:checkstyle (compile-checkstyle) @ gerrit-events --- [WARNING] The POM for com.sonyericsson.hudson.plugins.gerrit:build-config:jar:1.2.10-SNAPSHOT is missing, no dependency information available [INFO] [INFO] Reactor Summary: [INFO] [INFO] Gerrit Trigger Pom SUCCESS [4.107s] [INFO] Build Config .. SUCCESS [1.184s] [INFO] Gerrit Events . FAILURE [0.648s] [INFO] Gerrit Trigger SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7.508s [INFO] Finished at: Wed Dec 19 18:43:42 GMT+08:00 2012 [INFO] Final Memory: 22M/194M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.8:checkstyle (compile-checkstyle) on project gerrit-events: Execution compile-checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.8:checkstyle failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.8 or one of its dependencies could not be resolved: Failure to find com.sonyericsson.hudson.plugins.gerrit:build-config:jar:1.2.10-SNAPSHOT in http://repo.jenkins-ci.org/public/ was cached in the local repository, resolution will not be reattempted until the update interval of repo.jenkins-ci.orghttp://repo.jenkins-ci.org has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :gerrit-events Anyone has any ideas? ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: [ANN] looking for speakers in various parts of the world Jan 2013
I would be happy to present something on the lines of the setting up and evolution of CI system with Maven in a more traditional shop (e.g. multiple continuous branches of a product instead of the continuous deployment web2.0) and things we learnt along the way - and things that are still missing / sub optimal in London. It would give an introduction on topics like master vs slave, executors, source control setup on slaves (svn+ssh, git), maven job type, gerrit, and some cloudbees folders, templates, vmware plugins, and how we string it all together. Let me know if this is of interest. /James -Original Message- From: jenkinsci-us...@googlegroups.com [mailto:jenkinsci-us...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi Sent: 14 December 2012 00:06 To: Jenkins Dev; Jenkins Users; eve...@lists.jenkins-ci.org Subject: [ANN] looking for speakers in various parts of the world Jan 2013 Hi, I'm doing a little bit of world tour next January. As a part of it, I'm trying to do small meet-ups in places that we don't normally do them. To attract more people, I'm looking for people willing to come present in those events. It can be a talk of any size --- more than anything else I'm trying to hook up people locally (as well as meeting them myself!) A presentation doesn't have to be this is how we solved all the problems. A story of how the usage evolved is often very well-received, as well as this is what we've done so far and this is what we are struggling, I think Jenkins should fix them talks. We are looking for the following locations in particular: - London - Seoul - Toronto (this one isn't concrete) -- Kohsuke Kawaguchi http://kohsuke.org/ ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Calling a maven instance from a plugin
Hi Dimitri, Don’t use it – just look at the code which will give you an example of changing the goals. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Dimitri CHARLES Sent: 14 November 2012 11:57 To: jenkinsci-dev@googlegroups.com Subject: Re: Calling a maven instance from a plugin Hi James, Thanks for your answer. How can I use this plugin. I see that it is used to perform Maven release. Can you give me an example how can I use it? Thanks Le mercredi 14 novembre 2012 12:29:14 UTC+1, teilo a écrit : Take a look at the m2release plugin – you can dynamically (and optionally) change the default goals that get passed to maven in a plugin. /James From: jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] On Behalf Of Dimitri CHARLES Sent: 14 November 2012 09:11 To: jenkin...@googlegroups.com Subject: Calling a maven instance from a plugin Hi, I am actually writing a plugin where I want to pass some customs parameters, goals to a maven instance. For instance, some profiles, some properties contained in a POM (-Dproperty=value). I tried to look in the jenkins code and I see that the class hudson.tasks.Mavenhttp://javadoc.jenkins-ci.org/hudson/tasks/Maven.html could help me. But I also see there is the class AbstractMavenBuilderhttp://javadoc.jenkins-ci.org/hudson/maven/AbstractMavenBuilder.html. The idea that I have for the first one is I have a maven property (type of Maven) in my plugin (my plugin is a class that extends Builder), and I instantiate this property with my custom goals. In my perform method, I call maven.perform(). For the AbstractMavenBuilder, I discovered it yesterday and I was thinking to extend this class. Is this a better way to do that? Can you show an example how to call a maven instance from a plugin? Thanks for your suggestion ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postm...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Calling a maven instance from a plugin
It uses the getGoalsAndOptions rather than the intercept. Intercept is more for adding extra options, getGotalsAndOptions is used to change the default goals that run (the ones that are normally entered in the UI). See https://github.com/jenkinsci/jenkins/blob/master/maven-plugin/src/main/java/hudson/maven/MavenArgumentInterceptorAction.java /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Dimitri CHARLES Sent: 14 November 2012 14:37 To: jenkinsci-dev@googlegroups.com Subject: Re: Calling a maven instance from a plugin Hi James, Thanks for your answer. I watched and it seems that I have to implement MavenArgumentInterceptorAction. But in the class M2ReleaseArgumentInterceptorAction, why dont implement the intercept method? Le mercredi 14 novembre 2012 13:04:45 UTC+1, teilo a écrit : Hi Dimitri, Don’t use it – just look at the code which will give you an example of changing the goals. /James From: jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] On Behalf Of Dimitri CHARLES Sent: 14 November 2012 11:57 To: jenkin...@googlegroups.com Subject: Re: Calling a maven instance from a plugin Hi James, Thanks for your answer. How can I use this plugin. I see that it is used to perform Maven release. Can you give me an example how can I use it? Thanks Le mercredi 14 novembre 2012 12:29:14 UTC+1, teilo a écrit : Take a look at the m2release plugin – you can dynamically (and optionally) change the default goals that get passed to maven in a plugin. /James From: jenkin...@googlegroups.commailto:jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] On Behalf Of Dimitri CHARLES Sent: 14 November 2012 09:11 To: jenkin...@googlegroups.commailto:jenkin...@googlegroups.com Subject: Calling a maven instance from a plugin Hi, I am actually writing a plugin where I want to pass some customs parameters, goals to a maven instance. For instance, some profiles, some properties contained in a POM (-Dproperty=value). I tried to look in the jenkins code and I see that the class hudson.tasks.Mavenhttp://javadoc.jenkins-ci.org/hudson/tasks/Maven.html could help me. But I also see there is the class AbstractMavenBuilderhttp://javadoc.jenkins-ci.org/hudson/maven/AbstractMavenBuilder.html. The idea that I have for the first one is I have a maven property (type of Maven) in my plugin (my plugin is a class that extends Builder), and I instantiate this property with my custom goals. In my perform method, I call maven.perform(). For the AbstractMavenBuilder, I discovered it yesterday and I was thinking to extend this class. Is this a better way to do that? Can you show an example how to call a maven instance from a plugin? Thanks for your suggestion ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postm...@nds.commailto:postm...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postm...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines,
RE: Backports to LTS 1.480.1
I would like to nominate JENKINS-15382 [1] Not a critical or blocker, but it caused me some intermittent grief. (and I've been running this in production backported to 1.466.2 thanks to Cloudbees) /James [1] https://issues.jenkins-ci.org/browse/JENKINS-15382. -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Vojtech Juranek Sent: 21 October 2012 21:55 To: jenkinsci-dev@googlegroups.com Subject: Backports to LTS 1.480.1 Hi, as agreed on the last Jenkins meeting [1], next LTS will be based on 1.480. I identified and backported following bug fixes: JENKINS-13336 Invalid JSON is produced during remote api operations [2] JENKINS-14667 java.io.InvalidClassException [3] JENKINS-15277 Check view permissions before showing config page [4] JENKINS-15493 Excessive memory usage with large number of request threads [5] Please let me know by Tuesday if there are any other critical or blocker issues need to be backported to 1.480.1. As also agree on the meeting, RC should be available by Wednesday. Thanks Vojta [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-10-17-18.02.html [2] https://issues.jenkins-ci.org/browse/JENKINS-13336 [3] https://issues.jenkins-ci.org/browse/JENKINS-14667 [4] https://issues.jenkins-ci.org/browse/JENKINS-15277 [5] https://issues.jenkins-ci.org/browse/JENKINS-15493 ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Fwd: Jenkins survey being drafted
getServletConfig().getServletContext().getServerInfo() on the Servlet? -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Kohsuke Kawaguchi Sent: 11 September 2012 17:19 To: jenkinsci-dev@googlegroups.com Cc: Vojtech Juranek Subject: Re: Fwd: Jenkins survey being drafted On 09/11/2012 03:16 AM, Vojtech Juranek wrote: The question on which servlet container Jenkins runs would be also interesting, though not sure if interesting enough to worth separate question and makes the form longer :-) I'm getting offtopic here, but I've been wondering if there's any way to sniff this from inside Jenkins itself (by looking for some well-known class names, property file that contains the version number, etc.) ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Verify downloaded jpi-files
-Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Jesse Glick Sent: 27 July 2012 21:34 To: jenkinsci-dev@googlegroups.com Subject: Re: Verify downloaded jpi-files On 07/27/2012 08:58 AM, Fredrik Orderud wrote: a simpler check against the in-built JAR/ZIP-file CRC-32 checksum would probably be good enough in most situations Even simpler: check if the file starts with 0x50 0x4b 0x03 0x04, the ZIP magic. If not, it is some junk like an error page which should be treated like a 404 or other connection error. File a bug or open a pull request; hudson.model.UpdateCenter.UpdateCenterConfiguration.postValidate could easily do this, I think. Isn’t this a security issue - I thought the update.json was signed to make it hard to prevent installing malicious components (but this just prevents the main Jenkins site update from being forged - which is no protection at all) As it stands you don’t need to do anything complex just some dns hijacking of a mirror (or attack a mirror, or be an evil mirror) and then you can just replace whatever hpi you want (pick a popular one like git or svn) then you can serve up any arbitrary code that gets executed? I guess the update.json needs to include the signatures of components as well for this to work (with 3rd party update sites). To be honest I thought I recalled a discussion that this was already done :-( /James ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Verify downloaded jpi-files
the json that I retrieved from my commercially supported version contained zero hashes, the JSON I have just pulled from retrieved from the default update site (http://updates.jenkins-ci.org/update-center.json) did contain hashes. So not a Jenkins issue (sorry for causing any confusion on the list) Regards, /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Stephen Connolly Sent: 30 July 2012 10:06 To: jenkinsci-dev@googlegroups.com Subject: Re: Verify downloaded jpi-files The update metadata includes the signature of the metadata as well as the sha1 sums of all the downloads, so that gives plenty of security though I agree somebody could use that injection trick to create a plugin with a matching sha1 to the sha1 in the metadata... but I suspect that it would be a lot of effort... and keep in mind that if it is a popular plugin that will get updated more frequently so the effort will be wasted... and the non-popular plugins will be less likely to get uptake On 30 July 2012 09:50, Nord, James jn...@nds.commailto:jn...@nds.com wrote: -Original Message- From: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com [mailto:jenkinsci-mailto:jenkinsci- d...@googlegroups.commailto:d...@googlegroups.com] On Behalf Of Jesse Glick Sent: 27 July 2012 21:34 To: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com Subject: Re: Verify downloaded jpi-files On 07/27/2012 08:58 AM, Fredrik Orderud wrote: a simpler check against the in-built JAR/ZIP-file CRC-32 checksum would probably be good enough in most situations Even simpler: check if the file starts with 0x50 0x4b 0x03 0x04, the ZIP magic. If not, it is some junk like an error page which should be treated like a 404 or other connection error. File a bug or open a pull request; hudson.model.UpdateCenter.UpdateCenterConfiguration.postValidate could easily do this, I think. Isn't this a security issue - I thought the update.json was signed to make it hard to prevent installing malicious components (but this just prevents the main Jenkins site update from being forged - which is no protection at all) As it stands you don't need to do anything complex just some dns hijacking of a mirror (or attack a mirror, or be an evil mirror) and then you can just replace whatever hpi you want (pick a popular one like git or svn) then you can serve up any arbitrary code that gets executed? I guess the update.json needs to include the signatures of components as well for this to work (with 3rd party update sites). To be honest I thought I recalled a discussion that this was already done :-( /James ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.commailto:postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Backports to LTS 1.446.1
Hi Vojta, I would like to nominate the following, new in 1.473 (2012/07/01) Updating job config.xml shouldn't clobber in-progress builds. (issue 12318) It's not a candidate yet as it hasn't been in a release for more than 2 weeks - but I'm hoping by the time the decision is taken that this would not be the case (given a new latest release is due in a few days.). /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Vojtech Juranek Sent: 05 July 2012 08:10 To: jenkinsci-dev@googlegroups.com Subject: Backports to LTS 1.446.1 Hi, as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. I identified following two critical issues needs to be backported: * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults and console output after Jenkins reload [3] Please let me know if there are any other critical or blocker issues need to be backported to 1.466.1 Thanks Vojta [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Announcing Zubhium Plugin for Jenkins
What’s further up in the log. It is implying that the tag hasn’t been created. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Andreas Katzig Sent: 17 May 2012 22:00 To: jenkinsci-dev@googlegroups.com Subject: Re: Announcing Zubhium Plugin for Jenkins Thanks, currently having a problem with mvn release:perform. After release:prepare seems to be successful, release:perform fails at the git pull to the target/checkout directory with: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:perform (default-cli) on project zubhium: Unable to checkout from SCM [ERROR] Provider message: [ERROR] The git-pull command failed. [ERROR] Command output: [ERROR] fatal: Couldn't find remote ref refs/tags/zubhium-0.1.3 [ERROR] fatal: The remote end hung up unexpectedly Someone knows what's happening here? Thanks On Sunday, May 13, 2012 6:31:27 PM UTC+2, domi wrote: done… repo (https://github.com/jenkinsci/zubhium-plugin) and component on JIRA Domi On 13.05.2012, at 16:51, Andreas Katzig wrote: Hi again, pom.xml is now available in my repository, tested the plugin this week, it's okay to be released and hosted now. So this is my request to host it under the Jenkins GitHub repository. Plugin GitHub URL: https://github.com/derFunk/jenkins-zubhium-plugin My GitHub and Jenkins ID: derFunk Wiki Page is prepared here: http://wiki.jenkins-ci.org/display/JENKINS/Zubhium+Plugin Must be filed under Artifact Uploaders then. I already defined the plugin artifact ID as zubhium. Regards, Andreas On Saturday, May 12, 2012 3:35:18 AM UTC+2, Kohsuke Kawaguchi wrote: Nice! Want to create a page under http://wiki.jenkins-ci.org/display/JENKINS/Plugins so that other people would notice? I also don't see a POM file in your repository. On 05/09/2012 02:26 AM, Andreas Katzig wrote: Hi there, I want to announce that I've created a plugin for Zubhium (http:// www.zubhium.comhttp://www.zubhium.com/) at https://github.com/derFunk/jenkins-zubhium-plugin. Zubhium is an ad hoc distribution system for Android apps, much like TestFlight for iOS. The plugin uploads the build artifacts in a post build action. This plugin is already live in our production. I still want to check the code for errors and then request plugin hosting officially. I'm announcing, so that nobody makes the work twice. All the best, Andreas -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: glassfish repo must die
My bad - I took an action a long time ago to investigate this and I did but never really got back to anyone or progressed it to its conclusion. Getting an artifact that is not under our control whose project has no interest in pushing it isn't a problem. What's more of a stumbling block - and what I have just asked the maven list is what we do with all the patched jars we have (svnkit/winstone) /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of nicolas de loof Sent: 05 April 2012 14:22 To: Stephen Connolly Cc: jenkinsci-dev@googlegroups.com Subject: Re: glassfish repo must die synch to central will fix dependency to jenkins artifacts (so most of plugins) but we still have some plugins to depend to artifacts that aren't available on central, - guice-2.0.1, or de.regnis.q.sequence:sequence-library (for svn-stuff) for sample 2012/4/5 Stephen Connolly stephen.alan.conno...@gmail.commailto:stephen.alan.conno...@gmail.com On 4 April 2012 23:13, Kohsuke Kawaguchi kkawagu...@cloudbees.commailto:kkawagu...@cloudbees.com wrote: On 04/04/2012 01:38 PM, nicolas de loof wrote: jenkins-ci.orghttp://jenkins-ci.org http://jenkins-ci.org is under our control so we can point it to whatever we like also, plugin can't build without a repo declaration as jenkins artifacts aren't available on central I don't thing this to be a bad practice. Would you expect all developers to configure settings with adequate repo to build your project ? This *only* is a requirement for deployment on central just my 2 cents :P Yes, the goal here is to make it easier for people to check out plugins and build them, so that they can apply patches. Many of them are Maven newbies. Then let's sync to central. Every added step (like ~/.m2/settings.xml tweaking) is a hurdle. We should have repository definition in POM to avoid this. Nope... we should just sync to central As Nicolas wrote, repo.jenkins-ci.orghttp://repo.jenkins-ci.org is our domain that we control, so the same thing won't happen again. (There is a separate effort to make more of our artifacts available in central, which would eliminate this problem in a long run, but we shouldn't wait for that.) Why not just hurry that effort along ;-) 2012/4/4 Jeff MAURY jeffma...@jeffmaury.commailto:jeffma...@jeffmaury.com mailto:jeffma...@jeffmaury.commailto:jeffma...@jeffmaury.com You should rather delete this repo definition as it is not a good Maven practice and may lead to the same problem in the future. Jeff On Wed, Apr 4, 2012 at 8:58 PM, nicolas de loof nicolas.del...@gmail.commailto:nicolas.del...@gmail.com mailto:nicolas.del...@gmail.commailto:nicolas.del...@gmail.com wrote: Hi folks, as you know, glassfish maven repo (aka m.g.o-public) is definitively off, but we depend on it for many plugins dependencies, and this is hardcoded in plugin parent pom (so, to get it fixed, plugin would need to upgrade to a recent jenkins-core dependency). some of you may already encounter dependency resolution issues trying to build a plugin form scratch I volunteer to migrate the 400+ plugins to replace repository pointing to m.g.o-public and replace/add repo.jenkins-ci.org/publichttp://repo.jenkins-ci.org/public http://repo.jenkins-ci.org/public where missing, so that each plugin explicitly defines repository to our infra (I plan to write a tool for that). We discussed this on governance meeting, but I wan't to ensure everybody agree here, so please let me know if you see any drawback or have another suggestion. Nicolas -- Jeff MAURY Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: glassfish repo must die
This increases the barrier to entry. Some plugins although they are still based of the same parent are internal to companies. Although the best practices is to use a repo manager - for some companies you may not have the ability to get extra artifacts added (as its for production software only) - or may not even be using a repo manager yet. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of domi Sent: 05 April 2012 14:35 To: jenkinsci-dev@googlegroups.com Subject: Re: glassfish repo must die we should really add an enforcer rule which stops people from doing this /Domi On 05.04.2012, at 15:27, Arnaud Héritier wrote: Please remember that there are close to 200 plugins which are in SVN still. They would need to be migrated to GitHub before applying this kind of broad and automatic conversion. https://wiki.jenkins-ci.org/display/JENKINS/Moving+from+Subversion+%28svn%29+to+Github Seriously ? And they aren't dead ? Couldn't we migrate all of them in Git(Hub) ? ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Jenkins is waiting for completion of all the concurrent build to give output status
If you have the static analysis plugins (checkstyle pmd etc) then those plugins will cause the build to wait if you have compute new issues (not sure of the exact text). Bypassing compute new issues should cause latter builds not to block. https://issues.jenkins-ci.org/browse/JENKINS-11761 /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Albin Joy Sent: 13 March 2012 07:54 To: Jenkins Developers Subject: Jenkins is waiting for completion of all the concurrent build to give output status Dear All, When more than one builds are running concurrently in Jenkins, Jenkins in not showing the build status even the particular build is finished. It is waiting till the completion of all the builds which are running currenlty. Anybody can tell will it be a problem with Jenkins code or with the plugin? I am new to Jenkins community. Anybody can tell:- 1. How the build is getting triggered in the Jenkins?, Which module is doing this? 2. What are the main modules presented in Jenkins? 3. The functionalities of each module? 4. Why Jenkins are designed with different projects.? Thanks.. JoyAlbin ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: Backports for LTS 1.424.3
Unfortunately this doesn't fix it (sorry only just been able to test) Jenkins 1.424.6 INFO: Started initialization Mar 08, 2012 1:47:27 PM jenkins.model.Jenkins$6 onAttained INFO: Listed all plugins log4j:WARN No appenders could be found for logger (net.bull.javamelody). log4j:WARN Please initialize the log4j system properly. SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Mar 08, 2012 1:47:30 PM jenkins.model.Jenkins$6 onAttained INFO: Prepared all plugins :-( I'm taking a guess that the maven plugin is loaded first and the slf4j implementation is provided by the Gerrit and m2release plugins. But the classloaders haven't been added so when slf4j is loaded for maven job type it can't find an implementation and fails. So latter when the Gerrit/m2release plugin load they get the same static do nothing logger. [root@jenkins_inst plugins]# find . -name \*slf\*.jar ./m2release/WEB-INF/lib/slf4j-jdk14-1.6.0.jar ./m2release/WEB-INF/lib/slf4j-api-1.6.0.jar ./maven-plugin/WEB-INF/lib/slf4j-api-1.6.1.jar ./gerrit-trigger/WEB-INF/lib/slf4j-jdk14-1.6.1.jar ./gerrit-trigger/WEB-INF/lib/slf4j-api-1.6.1.jar So the binding would need to be present by default in the main webapp WEB-INF/lib/ - or provided by the plugin. I'm aware there is an issue in JIRA about problems with providing the binding with a certain container - but really no logs by default out of the box has to be worse than blowing up because someone can't write a container correctly doesn't it? /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Vojtech Juranek Sent: 02 February 2012 20:37 To: jenkinsci-dev@googlegroups.com Subject: Re: Backports for LTS 1.424.3 Hi James, An easier test is to open up the maven-plugin.hpi If it contains \WEB-INF\lib\slf4j-noop-*.jar then it will prevent logging thanks for easy test, if it's just about presence of slf4j-nop-*.jar (I guess you meant slf4j-not, not noop), it can be fixed by upgrade to wagon 2.2 - it's this series of commits: 532ab9448de62920fd5e2dcb73c2e0b024f39d11 ec29ce6f0c8e3a77aae54c485a28c741a266dc93 4f044c282bb2473c41a4fca32dbbd1f46d276995 7bba3abcf9456e5a933e2207c4d87bc58a9f2fc0 hopefully it doesn't break anything else... But a trawl of JIRA shows that it's probably not even been fixed (and has even got worse! looks like it was introduced in sshd, which is on in 1.424 - except for some questionable container like EAP that doesn't isolate classloaders correctly!) :-D ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
RE: maven.glassfish.org put offline
Adding the mirror was all I needed to do last night to hack away. /James From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Thomas Broyer Sent: 02 March 2012 16:52 To: jenkinsci-dev@googlegroups.com Subject: Re: maven.glassfish.org put offline D'oh! Sorry, I search for maven.glassfish.org on Google Groups but it didn't give me https://groups.google.com/d/topic/jenkinsci-dev/1aPlT07gRQ0/discussion (and I didn't recognize m.g.o-public as a synonym while quickly scanning the latest threads) So, does it mean I could have added a mirror in my settings.xml? Something like: mirror idrepo.jenkins-ci.org/id mirrorOfm.g.o-public/mirrorOf urlhttp://repo.jenkins-ci.org/public/urlhttp://repo.jenkins-ci.org/public%3c/url /mirror On Friday, March 2, 2012 5:46:38 PM UTC+1, Thomas Broyer wrote: Hi there, I was going to start hacking on Jenkins (actually on the gerrit-trigger-plugin) and Maven's “downlading the internet…” was taking much longer than it should be. I then noticed it stopped for minutes trying to resolve artifacts from maven.glassfish.orghttp://maven.glassfish.org. It turns out the server has been put offline in the last couple of days: http://java.net/projects/glassfish/lists/dev/archive/2012-02/message/118 As a workaround, I ended up hacking the downloaded POMs to remove the references to the repository: sed -i 's|http://maven.glassfish.org/content/groups/public/|http://repo1.maven.org/maven2/|http://maven.glassfish.org/content/groups/public/%7Chttp:/repo1.maven.org/maven2/%7C' $(grep -R maven.glassfish.orghttp://maven.glassfish.org ~/.m2/ --include '*.pom' -l) It all went smooth after that, proof that references to that maven repo were not actually needed ⇒ bad practice (or were they really needed at some earlier point in time?) Well, that just a FYI (with a little bit of rant); now back to hacking! (and by the way, thank you so much for making Jenkins!) ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
