Re: Accessing another plugin's configuration
I think this approach is quite fragile (well it works but may break very soon...). I would suggest that you talk with the author of the plug-in to see if he could add an extension point for those properties. Ulli On 02/22/2012 11:12 AM, Emanuele Zattin wrote: Let's suppose you have a Project object you want the instance of a particular Publisher that job is configured for... then you can: MyPublisher = Iterables.filter(p.getPublishers().values(), Predicates.instanceOf(MyPublisher.class)); I hope this helps. BR, Emanuele Zattin --- -I don't have to know an answer. I don't feel frightened by not knowing things; by being lost in a mysterious universe without any purpose — which is the way it really is, as far as I can tell, possibly. It doesn't frighten me.- Richard Feynman On Wed, Feb 22, 2012 at 11:06 AM, dschulten dietrich.schul...@googlemail.com wrote: Hi, I am looking into https://issues.jenkins-ci.org/browse/JENKINS-6964 (Selenium plugin can't start RCs on slaves.) where Kohsuke proposed to tunnel the Selenium communication. In order to establish the tunnel, I would like to read the configuration of the slave and get SSH credentials from there. The ssh-slave plugin persists the slave credentials for its own use, but is it possible to access this information from other plugins? If so, how? Best regards, Dietrich
Re: JUC Paris T-shirt
+1 to #3. 2012/2/22 Adrien Lecharpentier adrien.lecharpent...@gmail.com Great work! my +1 to #3 -- Adrien Lecharpentier Le 22 février 2012 09:06, Alyssa Tong at...@cloudbees.com a écrit : Super. Thanks KK. #3 #5 are also my favorites..my top pick is #5. On Tue, Feb 21, 2012 at 11:38 PM, Kohsuke Kawaguchi k...@kohsuke.orgwrote: These all look awesome! My +1 to #3 and #5. 2012/2/22 Alyssa Tong at...@cloudbees.com: Hello, Based on feedback received, here's some images we came up with. Could I kindly get the community's vote on which image you like best? Again, if there's suggestions to tweak any of these images pls do share. https://skitch.com/alytong/8dwka/jenkinsinparis-crv-1.pdf-1-page thank you in advance, alyssa -- Kohsuke Kawaguchi
Re: mad jenkins on hpi:run
Greetings, Try wiping out work/ directory and then restart hpi:run. -Jesse On Feb 22, 2012 4:38 AM, Emanuele Zattin emanue...@gmail.com wrote: Hello there! While developing a plugin I got the weird behavior shown in the picture. Please note the null instead of job and the dead executors. In the stdout/err, before even opening the browser to visit the webpage, I can see that subversion, maven and the other plugins have been stopped, but no exception is shown and no stacktrace. As soon as I open the webpage the console goes crazy with exceptions. The whole log is attached as well. At the moment I cannot try on another machine, but starting jenkins with java -jar jenkins.war works fine, even with my plugin. I have the feeling there might be some conflict going on with a jenkins.pkg installation i did some months ago. I think I removed everything installed by the pkg file, but maybe something is still there. Any hint? BR, Emanuele Zattin --- -I don't have to know an answer. I don't feel frightened by not knowing things; by being lost in a mysterious universe without any purpose — which is the way it really is, as far as I can tell, possibly. It doesn't frighten me.- Richard Feynman
Re: Accessing another plugin's configuration
Hi guys, If Iunderstand the problem, it's all about sharing information betwwen plugins, right? And what about centralize these information? In fact, Romain Seguy already talk about a (not open-sourced yet) plugin we have and may fit your needs. https://groups.google.com/d/msg/jenkinsci-dev/baNWBRuThWE/QARWQE-b8KEJ To centralize information (For instance, SSH connections details) we define *RESOURCES. *This resource (a SSH Site for instance) will be your credentials storage. Some of our plugins, built upon this one, display the list of the available resources (preventing user mistakes). If you (or other) are interested by this plugin, we can release it. Cheers Daniel * *
HTML comments in Groovy views... is it possible?
I would like to put something like this in the head of page of a plugin: !--[if lte IE 8]script language=javascript type=text/javascript src=makeStupidIeHappy.js/script![endif]-- Is it possible at the current stage? BR, Emanuele Zattin --- -I don't have to know an answer. I don't feel frightened by not knowing things; by being lost in a mysterious universe without any purpose — which is the way it really is, as far as I can tell, possibly. It doesn't frighten me.- Richard Feynman
Re: Accessing another plugin's configuration
Actually CloudBees have a credentials store plugin that we will be releasing OSS in the near future. That plugin should solve quite a few credentials management problems. On 22 February 2012 16:38, Daniel PETISME daniel.peti...@gmail.com wrote: Hi guys, If Iunderstand the problem, it's all about sharing information betwwen plugins, right? And what about centralize these information? In fact, Romain Seguy already talk about a (not open-sourced yet) plugin we have and may fit your needs. https://groups.google.com/d/msg/jenkinsci-dev/baNWBRuThWE/QARWQE-b8KEJ To centralize information (For instance, SSH connections details) we define RESOURCES. This resource (a SSH Site for instance) will be your credentials storage. Some of our plugins, built upon this one, display the list of the available resources (preventing user mistakes). If you (or other) are interested by this plugin, we can release it. Cheers Daniel
Re: Accessing another plugin's configuration
Just to let people know what kind of things it can do: 1. Introduces Global (all jobs in the system) System (only root actions) scoped credentials 2. Introduces per-user credentials (only available to the user that owns them) 3. (With enhancements to our folders plugin) Introduces per folder credentials Some things we need to do before OSSing it involve finding a nice way to integrate it into the git subversion auth, so that this credential store can be used in addition to the current (what I would see as legacy) auth store(s) Plugins depending on the cloudbees-credentials plugin can define their own credentials types and those credentials types will be available via the same API. The API allows resolving credentials for a specific item and for a specific authentication. On 22 February 2012 17:02, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Actually CloudBees have a credentials store plugin that we will be releasing OSS in the near future. That plugin should solve quite a few credentials management problems. On 22 February 2012 16:38, Daniel PETISME daniel.peti...@gmail.com wrote: Hi guys, If Iunderstand the problem, it's all about sharing information betwwen plugins, right? And what about centralize these information? In fact, Romain Seguy already talk about a (not open-sourced yet) plugin we have and may fit your needs. https://groups.google.com/d/msg/jenkinsci-dev/baNWBRuThWE/QARWQE-b8KEJ To centralize information (For instance, SSH connections details) we define RESOURCES. This resource (a SSH Site for instance) will be your credentials storage. Some of our plugins, built upon this one, display the list of the available resources (preventing user mistakes). If you (or other) are interested by this plugin, we can release it. Cheers Daniel
Re: ParameterizedTriggerPlugin - some feedback please on JENKINS-12488 and LinesFromFileParameterFactory
OK, so I'm starting to get the hint that this isn't interesting to people. :) Other than modifying hudson.plugins.parameterizedtrigger.BuildInfoExporterAction, is there some other way to force the plugin to export details about the builds it triggered for later build steps? I'm hoping that I don't have to maintain a fork of the ParameterizedTriggerPlugin. Thanks! Brian On Tue, Feb 14, 2012 at 4:59 PM, Brian Parker onebrianpar...@gmail.com wrote: Can one someone please give me some feedback on if they think having the ParameterizedTriggerPlugin add the triggered builds to the environment for later build steps is a good idea? I've created https://issues.jenkins-ci.org/browse/JENKINS-12488 . I've created a pull request for that issue and also a new ParameterFactory - https://github.com/jenkinsci/parameterized-trigger-plugin/pull/16 If you don't want the LinesFromFileParameterFactory, I think I can always package that as a separate plugin that depends on the ParameterizedTriggerPlugin. However, I don't know how else we'll accomplish our goals without something similar to JENKINS-12488. For that reason, I'm kind of eager for some feedback. Please let me know what you think. Thank you! Brian
Re: RFC: Breadcrumb on steroid
wow - its not me starting this again :) here it is... https://github.com/imod/jenkins/commit/451d1dc6b5c868d5f0a46bf150f5ed9cefd36f36 /Domi On 22.02.2012, at 10:54, Andrew Gray wrote: Hi All, While we are speaking about Ui fixes, one thing I never understood is why we have not changed Jenkins to match the new red and black color scheme. There is a pull request somewhere with the work all done it just needs to be merged. I really think it would add to the brand not only in its own right but also to distinguish Jenkins from Hudson. While Branding IS marketing and marketing is something that we developers may hold is less regard than enhanced functionality, marketing has its place. From someone who wants to see the widest possible adoption of Jenkins, it is business-type people that I often need to convince not only on the idea of CI but also that Jenkins is the correct choice therefore a completely aligned brand has value. We all want Jenkins to look as professional a package as possible, therefore on this basis I ask that the pull request be merged as part of this Ui improvement drive. Happy to discuss, over to you. Regards, Andrew On Wednesday, February 22, 2012, Jesse Farinacci wrote: Greetings, On Mon, Feb 20, 2012 at 11:43 PM, Andrew Gray andrew.paul.g...@gmail.com wrote: Say I wanted to queue a build for all jobs in a view at once. I don't disagree that it could be more conveniently or prominently displayed, but https://wiki.jenkins-ci.org/display/JENKINS/Bulk+Builder+Plugin does have a way to bulk submit all jobs in a View. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: Accessing another plugin's configuration
In my case I need at least access to ssh slave credentials to open an ssh tunnel for selenium remote controls, or maybe even to the established connections stored within ssh-slaves pluginImpl, if they can be used to create tunnels. But it seems currently I would need an extension point in ssh-slaves in order to access its active connections safely. @Stephen: would you accept such an extension point in ssh-slaves? Or would you rather have me read the credentials from the plugin you mentioned above? Cheers, D' Am 22.02.2012 18:26 schrieb Stephen Connolly stephen.alan.conno...@gmail.com: Just to let people know what kind of things it can do: 1. Introduces Global (all jobs in the system) System (only root actions) scoped credentials 2. Introduces per-user credentials (only available to the user that owns them) 3. (With enhancements to our folders plugin) Introduces per folder credentials Some things we need to do before OSSing it involve finding a nice way to integrate it into the git subversion auth, so that this credential store can be used in addition to the current (what I would see as legacy) auth store(s) Plugins depending on the cloudbees-credentials plugin can define their own credentials types and those credentials types will be available via the same API. The API allows resolving credentials for a specific item and for a specific authentication. On 22 February 2012 17:02, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Actually CloudBees have a credentials store plugin that we will be releasing OSS in the near future. That plugin should solve quite a few credentials management problems. On 22 February 2012 16:38, Daniel PETISME daniel.peti...@gmail.com wrote: Hi guys, If Iunderstand the problem, it's all about sharing information betwwen plugins, right? And what about centralize these information? In fact, Romain Seguy already talk about a (not open-sourced yet) plugin we have and may fit your needs. https://groups.google.com/d/msg/jenkinsci-dev/baNWBRuThWE/QARWQE-b8KEJ To centralize information (For instance, SSH connections details) we define RESOURCES. This resource (a SSH Site for instance) will be your credentials storage. Some of our plugins, built upon this one, display the list of the available resources (preventing user mistakes). If you (or other) are interested by this plugin, we can release it. Cheers Daniel
Re: Admin stuff: Change of leader on some JIRA components
Greetings, On Wed, Feb 22, 2012 at 8:11 AM, Romain Seguy romain.se...@gmail.com wrote: May a JIRA admin change the owner of the following components from rseguy to danielpetisme please: backup clearcase-ucm-baseline copy-to-slave mask-passwords qc rad-builder role-strategy was-builder Complete. https://issues.jenkins-ci.org/browse/JENKINS#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
