Re: Support of Java 1.5/5
Hi, For the record, our master Jenkins is currently running AIX 5.3 level 10 (we are going to make it a slave soon, though, and use a only coordinating master using another OS, anyway). By the way, though I didn't find the reference information on IBM website, seems like it was eos'd in april 2012http://www.aixhealthcheck.com/blog.php?id=272 . We made the bump some months ago to use Java 6 on AIX to run Jenkins. It's been working fine since. Though admitted, we haven't the honor to be using WAS. We actually previously deployed Jenkins inside Glassfish, and are now using the embedded winstone quite happily. And for those who might be interested, Java 7 is also available on AIX. We're currently in the process of upgrading some of our softwares to it. Cheers 2012/10/9 Kohsuke Kawaguchi k...@kohsuke.org Thanks for the feedback. This is the kind of data that I was looking for. Yes, I do realize that for some users upgrading isn't a simple process. In your environment, do you have any roadmap for upgrading to WAS 7.0 and onward? If you have a large number of app servers and EOS date is Sep 30th 2013, it sounds more likely that you'll be rolling out a newer version pretty soon? If your WAS servers will be upgraded within a year, you'll be able to catch up with the latest version of Jenkins again by then, so it might not be the end of the world. (I have to say this EOS time table of WAS [1] actually made me more comfortable requiring Java6 --- IBM products are probably among the longest in terms of the support window, and even with that, there will be no Java5-based WAS supported by IBM in a year.) [1] http://en.wikipedia.org/wiki/**IBM_WebSphere_Application_** Server#Version_historyhttp://en.wikipedia.org/wiki/IBM_WebSphere_Application_Server#Version_history On 10/07/2012 07:43 PM, Chris Graham wrote: Hello Kohsuke. I'm having real troubles with my nabble account so I can not post this there, please feel free to repost. Regarding the discussions around upgrading to a minimum of Java 1.6. Whilst I understand the desire for developers to play with something shiny and new, I do find that the current 1.5 based Jenkins is more than sufficient for our needs. I lot of responses about the upgrade are normally around the just upgrade the java (assuming that I am running under tomcat of similar [if only it was so simple as that!]). I am running Jenkins inside of WebSphere on AIX. I am currently hosting Jenkins under WAS 6.1 on AIX 5.3. Whilst AIX 5.3 is nearing (or may have reached it's EOS), WAS 6.1's EOS dates have *just been extended* by a year! Additionally, although the Sun/Oracle Java 1.5 may have been EOS'd quite a while ago, the IBM Java 1.5/5 is most definately not EOS. Please see: http://www.ibm.com/**developerworks/java/jdk/**lifecycle/index.htmlhttp://www.ibm.com/developerworks/java/jdk/lifecycle/index.html . Running on AIX, we have one choice in JDK: IBM. The IBM 1.5/5 EOS is Sept 2015! The reality is that we have lots of WebSphere servers running in large data centres. So simply stating just upgrade java (assuming that it is running under Tomcat or similar) is simply not an option for us. Whilst I do realise that very (1.5% by your figures) few of us still run on 1.5, some of us will simply not be able to upgrade to a newer version of WAS/JDK as a simple task. It's not as easy as clicking your fingers. I also do wonder how many installations are in said data centres and are unable to report their presence. So I do believe that the 1.5% figure would be low, but certainly within an order of magnitude. So, please do not cut us off from future updates. Thanks for your time. -Chris Chris Graham AIX, WAS, SCM, Build and Release SME -- Kohsuke Kawaguchi http://kohsuke.org/ -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: New plugin
Hi again, It still doesn't seems to be fixed. I'm not on the member list nor do I have write permissions to the repository. My username in github is whitesource-edo Edo On Monday, October 8, 2012 11:38:12 AM UTC+2, Olivier Lamy wrote: Hi, Try again that must be fixed now. 2012/10/8 Edo Shor edo@whitesourcesoftware.com javascript:: Thanks a lot. However, I have no write access to the repository on jenkinsci. On Friday, October 5, 2012 8:51:07 AM UTC+2, Olivier Lamy wrote: Done. I have just changed the name to match our current naming convention: https://github.com/jenkinsci/whitesource-plugin 2012/10/5 Edo Shor edo@whitesourcesoftware.com: Hi again guys, We want to have our plugin hosted. please. The github user and repo is https://github.com/whitesource-edo/jenkins-whitesource-plugin 10x, Edo Shor, White Source ltd. -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: New plugin
Apologize please check again. You can try join us on irc too #jenkins on freenode. 2012/10/9 Edo Shor edo.s...@whitesourcesoftware.com: Hi again, It still doesn't seems to be fixed. I'm not on the member list nor do I have write permissions to the repository. My username in github is whitesource-edo Edo On Monday, October 8, 2012 11:38:12 AM UTC+2, Olivier Lamy wrote: Hi, Try again that must be fixed now. 2012/10/8 Edo Shor edo@whitesourcesoftware.com: Thanks a lot. However, I have no write access to the repository on jenkinsci. On Friday, October 5, 2012 8:51:07 AM UTC+2, Olivier Lamy wrote: Done. I have just changed the name to match our current naming convention: https://github.com/jenkinsci/whitesource-plugin 2012/10/5 Edo Shor edo@whitesourcesoftware.com: Hi again guys, We want to have our plugin hosted. please. The github user and repo is https://github.com/whitesource-edo/jenkins-whitesource-plugin 10x, Edo Shor, White Source ltd. -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: New plugin
Thanks a lot. It works now. On Tuesday, October 9, 2012 11:06:12 AM UTC+2, Olivier Lamy wrote: Apologize please check again. You can try join us on irc too #jenkins on freenode. 2012/10/9 Edo Shor edo@whitesourcesoftware.com javascript:: Hi again, It still doesn't seems to be fixed. I'm not on the member list nor do I have write permissions to the repository. My username in github is whitesource-edo Edo On Monday, October 8, 2012 11:38:12 AM UTC+2, Olivier Lamy wrote: Hi, Try again that must be fixed now. 2012/10/8 Edo Shor edo@whitesourcesoftware.com: Thanks a lot. However, I have no write access to the repository on jenkinsci. On Friday, October 5, 2012 8:51:07 AM UTC+2, Olivier Lamy wrote: Done. I have just changed the name to match our current naming convention: https://github.com/jenkinsci/whitesource-plugin 2012/10/5 Edo Shor edo@whitesourcesoftware.com: Hi again guys, We want to have our plugin hosted. please. The github user and repo is https://github.com/whitesource-edo/jenkins-whitesource-plugin 10x, Edo Shor, White Source ltd. -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Subversion plugin: Missing support for externals in 1.4.2/3 for subversion working copy version 1.7
Hi Jan, remember that Jenkins is an open source project and many if not most developers work on it in their spare time. So eventually this issue will probably be fixed, but unless some of the subversion plugin developers have the urgent need to have this fixed for themselves, it will probably take some time. So, if you urgently need this for yourself, you're invited to fork the sources on Github and prepare a pull request with a fix. cheers Christoph Original-Nachricht Datum: Mon, 8 Oct 2012 22:58:28 -0700 (PDT) Von: climblinne jan.linnenk...@googlemail.com An: jenkinsci-dev@googlegroups.com Betreff: Re: Subversion plugin: Missing support for externals in 1.4.2/3 for subversion working copy version 1.7 That is really sad. Nobody seems to be interested in this topic. Is there nobody who could help? We write tickets to the issue tracker, direct emails and this one to the mailing list, but nobody from the subversion developer seems to listen. Please help us! Thanks Jan
Re: Subversion plugin: Missing support for externals in 1.4.2/3 for subversion working copy version 1.7
Dear Christoph, I know what are open-source projects are about (I am also supporting other open source projects). I tried all regular ways to communicate. But there is no response since 3,5 months. As I wrote, I would like to help. But I never start doing anything without communicating the main developers, if it is ok for them and to check if I am on the right path for the implementation. Best regards Jan
new plugin
Hi All, We'd like to move the dynaslave plugin under the Jenkins org. Current source is at https://github.com/netflix-skunkworks/dynaslave-plugin We'll ultimately want to use the Jenkins CI and other infrastructure--is this where requesting voice in IRC is appropriate? Let me know and I'll hop back in (my account/nick is registered on freenode, the ultra-creative bmoyles :)) Thanks! Brian Moyles
Re: new plugin
done. please check karma is ok. 2012/10/9 Brian Moyles br...@moyles.net: Probably helps to have my github ID too :) bmoyles. If possible, Gareth Bowles (github id garethbowles) and Justin Ryan (github id quidryan) should also have access. Thanks again, Brian On Tue, Oct 9, 2012 at 11:14 AM, Brian Moyles br...@moyles.net wrote: Hi All, We'd like to move the dynaslave plugin under the Jenkins org. Current source is at https://github.com/netflix-skunkworks/dynaslave-plugin We'll ultimately want to use the Jenkins CI and other infrastructure--is this where requesting voice in IRC is appropriate? Let me know and I'll hop back in (my account/nick is registered on freenode, the ultra-creative bmoyles :)) Thanks! Brian Moyles -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: new plugin
Looks good, I'll give a shout if anything odd turns up. Thanks for the quick turnaround! Brian On Tue, Oct 9, 2012 at 12:52 PM, Olivier Lamy oliver.l...@gmail.com wrote: done. please check karma is ok. 2012/10/9 Brian Moyles br...@moyles.net: Probably helps to have my github ID too :) bmoyles. If possible, Gareth Bowles (github id garethbowles) and Justin Ryan (github id quidryan) should also have access. Thanks again, Brian On Tue, Oct 9, 2012 at 11:14 AM, Brian Moyles br...@moyles.net wrote: Hi All, We'd like to move the dynaslave plugin under the Jenkins org. Current source is at https://github.com/netflix-skunkworks/dynaslave-plugin We'll ultimately want to use the Jenkins CI and other infrastructure--is this where requesting voice in IRC is appropriate? Let me know and I'll hop back in (my account/nick is registered on freenode, the ultra-creative bmoyles :)) Thanks! Brian Moyles -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Patch parameter plugin and review board
Originally wrote this to Ryan, who developed the reviewboard Jenkins plugin, but his e-mail address no longer works, so just sending it to the dev list instead. --- Hi, Ryan, The other day I wrote a patch-parameter plugin [1] that lets people submit a patch file to Jenkins and build it. I was talking to orrc in the IRC and he thought that the review board plugin might be able to take advantages of this --- the idea is that when people create new reviews and submit a patch, Jenkins can provide a feedback by testing out that patch. A similar mechanism exists for Git, which is implemented in the gerrit trigger plugin [2], and this was very well received. I don't personally use review board, but I think it'll be a great feature. So I just wanted to pass it on. [1] https://wiki.jenkins-ci.org/display/JENKINS/Patch+Parameter+Plugin [2] https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger -- Kohsuke Kawaguchi http://kohsuke.org/
Re: Add a new installer crawler for sonar runner
Go for it, and send in a pull request to https://github.com/jenkinsci/backend-crawler On 10/09/2012 10:26 AM, Julien HENRY wrote: Hi, I would like to provide sonar-runner as an installable tool in Jenkins. It seems we need to produce a JSON file hosted in Jenkins update site. Do you think it would be possible to do something in order to publish a hudson.plugins.sonar.SonarRunnerInstaller.json based on the content of the Maven repository [1]? If nobody see an objection I will write the groovy script that produces the json by parsing [2]. Regards, Julien [1] http://repository.codehaus.org/org/codehaus/sonar-plugins/sonar-runner/ [2] http://repository.codehaus.org/org/codehaus/sonar-plugins/sonar-runner/maven-metadata.xml -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
Re: An extra element in the HTML plugin cause js exception
Hi, It seems like I found the problem - I had an 'Advanced' element (f:advanced) under a separated f:section. It worked fine with the previous UI. You need to be very careful with the tags you're using in the config.jelly file.. Uri On Tue, Oct 9, 2012 at 8:46 PM, Uri Scheiner u...@noliosoft.com wrote: Hi Guys, Any of you have any idea about this? I'm trying to find a way to control the CSS of my plugin, but finds nothing.. Any hint will be appreciated.. Uri On Wed, Oct 3, 2012 at 12:34 PM, Uri Scheiner u...@noliosoft.com wrote: Hi all, I've noticed that when adding a post-build plugin that I developed it results in *Uncaught TypeError: Cannot read property 'firstChild' of null* . I debugged the javaScript that runs when adding the plugin and I've noticed the following behavior: In general, the element that represents the plugin UI should have one child - a table element that contains the attributes that should be displayed to the user. However, I've noticed that my plugin has two childs: 1. A link element: * link rel = stylesheet href= /jenkins/adjuncts/d3d844aa/lib/form/section_.css type=text/css* 2. A table element. When I changed the JavaScript, my plugin worked fine. My question is - how do I get rid from the 'link' element? I tried to modify the config.jelly file but no luck. Any ideas? I've debugged other plugins and none of them had this 'link' element so I wonder what made it appear. Thanks, Uri
