Use the slave.jar to deploy a logstash Cluster
Basically the idea is to map what KK did for Selenium with logstash. The Jenkins agent is very to neat to use and spread over a network (sounds like a Virus :p). So the idea is to deploy the logstash agent over a Jenkins grid to - Retrieve the pure Jenkins slave logs - Retrieve the underneath system components logs Any thoughts? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Difference between http://repo.jenkins-ci.org/public/ http://maven.jenkins-ci.org
Hi guys, I have a maven/repository question My company nexus is configured to access to http://maven.jenkins-ci.org. I'm trying to build a plugin an it's failing due to org.netbeans.modules:org-netbeans-insane:jar:RELEASE72 Indeed the jar isn't there: http://maven.jenkins-ci.org/content/repositories/releases/org/netbeans/modules/org-netbeans-insane/RELEASE72/ But it's there: http://repo.jenkins-ci.org/public/org/netbeans/modules/org-netbeans-insane/RELEASE72/ *Be careful to the public because it is not in releases*. too What are the differences between the 2 repositories ? Which one should add configure in my Nexus? In advance thank you -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Difference between http://repo.jenkins-ci.org/public/ http://maven.jenkins-ci.org
Indeed it's a redirection! I check the IPs and they are equals! I've updated my nexus and it worked! Thank you On Tuesday, May 21, 2013 2:43:16 PM UTC+2, Daniel PETISME wrote: Hi guys, I have a maven/repository question My company nexus is configured to access to http://maven.jenkins-ci.org. I'm trying to build a plugin an it's failing due to org.netbeans.modules:org-netbeans-insane:jar:RELEASE72 Indeed the jar isn't there: http://maven.jenkins-ci.org/content/repositories/releases/org/netbeans/modules/org-netbeans-insane/RELEASE72/ But it's there: http://repo.jenkins-ci.org/public/org/netbeans/modules/org-netbeans-insane/RELEASE72/ *Be careful to the public because it is not in releases*. too What are the differences between the 2 repositories ? Which one should add configure in my Nexus? In advance thank you -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Request for hosting new plugin - Golo
Hi all, Golo[1] is a brand new lightweight dynamic language for the JVM. I've made a plugin[2] to run Golo sources as a standard Jenkins BuildStep. I would like to be able to store it into the official jenkins-ci. Cheers Thank you. [1] http://golo-lang.org/ [2] https://github.com/danielpetisme/golo-plugin -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Request for hosting new plugin - Golo
Thank you. May I ask you to set up access to the jenkins CI in BuildHives too, please? Le mercredi 10 avril 2013 17:11:55 UTC+2, slide a écrit : Done https://github.com/jenkinsci/golo-plugin On Wed, Apr 10, 2013 at 8:10 AM, Daniel PETISME daniel@gmail.comjavascript: wrote: Hi all, Golo[1] is a brand new lightweight dynamic language for the JVM. I've made a plugin[2] to run Golo sources as a standard Jenkins BuildStep. I would like to be able to store it into the official jenkins-ci. Cheers Thank you. [1] http://golo-lang.org/ [2] https://github.com/danielpetisme/golo-plugin -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Database Plugin Documentation
Hi guys, I tried to set up the Database Plugin : - database : 1.1 - database-postgresql : 1.0 My DB is a PostgreSQL one and its hosted in a Herokuhttp://www.heroku.com/app I set up the Jenkins side et the connection test is OK. What are the next steps. I mean I thought Jenkins configuration Jobs config would be stored in this DB. My test usecase is to setup a set of Jobs and then delete the configuration files to let the DB act as Data Source but if I relaunch Jenkins my jobs simply disappear I might not using the plugin in the way I should but with it din't found anay documentation regarding this new feature. Anybody can guide my in this setup ? So, I could do a part of the doc ;) In advance, thank you. Regards Daniel -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: where can I find the code that deletes builds?
i've got 2 snippets you can use.
The first one assume that you have access at the Groovy console. It will
delete all the old builds of a job and reset the buildNumber:
def job = hudson.model.Hudson.instance.items.find{ it.name == JOB_NAME}
job.getBuilds().each{ it.delete()}
job.updateNextBuildNumber(1)
The second snippet delete the job itself (you've to check about the filesystem
cleaning). Each Item as a delete method
Have a look at:
https://github.com/jenkinsci/rrod-plugin/blob/master/src/main/java/com/michelin/cio/jenkins/plugin/rrod/model/DeleteRequest.java
The RROD plugin aims to force user to ask to the Jenkins admin to rename or
delete a job.
https://wiki.jenkins-ci.org/display/JENKINS/Request+Rename+Or+Delete+Plugin
Let me know if you succeed to do it.
Regards
Daniel
On Tuesday, February 5, 2013 11:51:14 AM UTC+1, Chris Withers wrote:
Hi All,
Trying to do some debugging for this issue:
https://issues.jenkins-ci.org/browse/JENKINS-16638
Where would I look in a clone of the jenkins repo to find the code that
deletes old builds? (since that's my only guess as to what could have
deleted these child builds...)
cheers,
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins Sticker
Hell, yeah ;) I'm talking about the LavaJUGhttp://www.lavajug.org/xwiki/bin/view/Main/WebHome (Clermont-Fd), I'll need to contact the JUG leaders. Ask either Arnaud, Gregory or Henri for feedbacks (and food advice) :D I think we can close the topic and continue the conversation by mail/Gtalk/Twitter or what ever you want. Sounds ok for you? On Sunday, February 3, 2013 9:26:49 PM UTC+1, nicolas de loof wrote: I use to distribute some when going to french JUGs, so could be an opportunity 2013/2/3 Daniel PETISME daniel@gmail.com javascript: Hello guys, I was wondering how is possible to get some Jenkins sticker outside the conferences? Devs laptops are incredible hoardings ;) I could distribute them in my local JUG also. Regards -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [RFC] any idea for give-aways
What about a USB Jenkins kit :) - an USB stick with a Jenkins logo on it - the latest Jenkins version in it (the war or natives) - Some docs - The Jenkins manual - A Jenkins Quick Win/cheatsheet Otherwise, some classics - A shirt - A (beer) bottle opener - A mug On Wednesday, January 23, 2013 9:09:08 PM UTC+1, Kohsuke Kawaguchi wrote: In the project meeting today, we had a conversation about what give-aways to make for this year. In the past several years we made 3x3 stickers, and while those are still very popular, I thought it might be fun to see if we can make something else as well. Ideally it'd be not too expensive, and it shouldn't be too bulky nor too heavy. Any discounts you can find would be greatly appreciated. Some of the ideas include a pin badge, although I haven't found any price information on it. If you have any thoughts, please let us know! -- Kohsuke Kawaguchi
Re: Job Templatator
Hi Sylvain. I saw your plugin today!!! I love the approach (I could not tried it yet). But the screenshots fit perfectly with my use case. I'll try to have a closer look on it and bring my feedback. But I'm almost sure, its what I was looking for! Daniel PETISME +33 (0) 6 69 29 45 55 daniel.peti...@gmail.com On Fri, Nov 30, 2012 at 1:30 PM, syl20bnr sylvain.ben...@gmail.com wrote: There is now an other approach which may be more intuitive for some users, this is the Job Generator plugin: https://wiki.jenkins-ci.org/display/JENKINS/Job+Generator+Plugin -syl20bnr-
Re: Job Templatator
@Blador That's what I have in mind also!! I would like to integrate this mechanism inside a Jenkins plugin. But basically, it would have the same process. Talking OOP, the config.xml will be my Class definition I just have to define a Config.xml instantiator ;) I'll try to make a POC based on your point of view and I'll keep you inform of my progresses. Thank you guys!
Re: Job Templatator
Indeed, if I generate a new job config.xml file it should be reloas, and yes it takes forever!!! That's mainly why I want to integrate such mechanism directly in a plugin. I didn't look the API yet but I know that we can create job using a REST URL, posting the config.xml. So I guess it should have a Job constructor which takes a stringify version of a config.xml. It could be a way to achieve my goal. What do you think of this solution? Daniel PETISME +33 (0) 6 69 29 45 55 daniel.peti...@gmail.com On Sun, Nov 18, 2012 at 3:34 PM, Andrew Melo andrew.m...@gmail.com wrote: On Sun, Nov 18, 2012 at 10:26 AM, blalor bla...@bravo5.org wrote: I think lots of us are trying to solve this problem. I haven't played with the job-dsl plugin, yet; it sounds like it's on the right path, but as I understand it needs to be extended to support specific plugins. I've got a pretty simple set of Python scripts that I use to build jobs. We've got about a dozen projects, each with one or more downstream deploy jobs, and another set of parallel regression and automation test jobs. So we're deep into the tens of jobs that need to be maintained. My script has a templatized XML file for each type of job and a config file for each project (which could probably be done away with if the projects were named consistently). It uses Jinja to generate the concrete job config.xml from the template and per-project config. It can both generate new jobs and update existing jobs with the new config. All I'm missing now is the ability to keep people from modifying these templatized jobs! The problem with that method (for me at least) is that reloading the configurations from disk involve rebooting jenkins, which takes forever and blocks anyone from doing work. Or, do yo have some sort of way to modify the jobs using the API? -Melo -- -- Andrew Melo
Job Templatator
Hello all, I'm searching for a template job creator. My aim is to define a template job/flow of jobs and then make them template to create a new kind of projects in the New Job dialog. I'm aware of the plugins: https://wiki.jenkins-ci.org/display/JENKINS/Template+Project+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Template+Workflows+Plugin But they don't feed my needs. I've once heard about the Nectar template plugin but I can't found it in the latest Nectar release. Any clue ? So basically my questions are: 1. Do you manage kinds of archetypes/templates/New projects entries in your Jenkins 2. If yes, how ? which practices/plugins? 3. Do you suceed to implement such behavior with flows of jobs? In advance, thank you for your comments. Regards Daniel
Build Step wrapper
Hello guys, As far as I know there is no Build-Step Wrapper/Decorator in jenkins-core,I tried (a couple month ago) to study this point but i requires some core-updates. I've got some use cases which can take advantage of this extension point. In a Job configuration we can't add some details about build steps. The idea is to include some debug/info information but at the build step level. These information could be displayed (or not) in the console output. First of all, it would improve the maintenance of a job configuration (just as comments do in a source code), then displayed in log file it offers a more functional (high-level) point of view of the job's process. I like Ant behavior which build anchors to navigate to the console output but unfortunately we can't navigate easily from build step to build step. A wrapper could build these anchors for every build steps (based on the Console annotator mechanism). This plugin is very close to the concept. https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin It's a build step, wrapping and triggering nested build steps. Is it the official approach or a smart solution? What's your thoughts on this?
Re: Plugin 'Synchronize remote jobs'
Hi, I'm very interested by your plugin. have a git repo to follow your updates? In advance, thank. Le vendredi 13 juillet 2012 15:34:41 UTC+2, mpapo - Michaël Pailloncy a écrit : Hi, Even if our goals are not the same, it seems that you need same functionnalities. I'm currently developing a plugin equivalent to your first idea (Job Comparator Plugin) with the ability to merge parts of a configuration file manually. Then, it could certainly evolve into one of yours ideas. Michaël 2012/7/11 Daniel PETISME daniel.peti...@gmail.com I'm also interested by such feature, there is my use case. 2 different organizations : Customer - Exploitation supplier. 2 Jenkins instance identical (ie: 2 masters but same infra) aim to continuously deploy on target environments (Dev, indus, Prod,etc.). The target deployment environments should be identical. Of course, the 2 organization don't have the same deployment process. *Customer:* Deploy its app on its own environment thanks to Jenkins. Once it's good, the customer tag the app and the jenkins job to the SCM tool and communicate the tag name to the supplier *Exploitation:* Pick the tagged Jenkins job, customize it and deploy the application thanks to this job. An issue appears when the customer has to re-deliver an application and the job has been updated. The Exploitation has to re-start from scratch. *List of the exiting tools already considered:* The job config history plugin allows to make diff between the different version of a job. IMHO, it must use to trace the change than to do roll backs. The job import plugin: allows to copy jobs from an instance to another but it doesn't keep trace of the original job. The 2 jobs are totally independent. The SCM sync plugin: a config history++ it allows job versionnning and rollbacks. *Ideas*: *The easiest one *Do the merge by hand each time. *MDA approach* Inspired from the Model driven architecture. If define job archetype on all the instances (models) we should be able to apply a sort of transformation to swicth from an archetype to another? *Work by increment* Reconsider the concept of copied job. Instance of copy the whole config.xml into a new_config.xml, we can imagine to reference the original copied job and keep the increment. E.g: My_JOB_MVN3.xml = My_JOB_MVN3.xml + INCEREMENT.xml Instead of copying My_JOB_MVN3.xml we can image to have a repository of jobs, and the increment just store the delta. *Object oriented approach* The aim is to use inheritance for default values and override specific behaviors. What's your thoughts?
Re: Plugin 'Synchronize remote jobs'
I'm also interested by such feature, there is my use case. 2 different organizations : Customer - Exploitation supplier. 2 Jenkins instance identical (ie: 2 masters but same infra) aim to continuously deploy on target environments (Dev, indus, Prod,etc.). The target deployment environments should be identical. Of course, the 2 organization don't have the same deployment process. *Customer:* Deploy its app on its own environment thanks to Jenkins. Once it's good, the customer tag the app and the jenkins job to the SCM tool and communicate the tag name to the supplier *Exploitation:* Pick the tagged Jenkins job, customize it and deploy the application thanks to this job. An issue appears when the customer has to re-deliver an application and the job has been updated. The Exploitation has to re-start from scratch. *List of the exiting tools already considered:* The job config history plugin allows to make diff between the different version of a job. IMHO, it must use to trace the change than to do roll backs. The job import plugin: allows to copy jobs from an instance to another but it doesn't keep trace of the original job. The 2 jobs are totally independent. The SCM sync plugin: a config history++ it allows job versionnning and rollbacks. *Ideas*: *The easiest one *Do the merge by hand each time. *MDA approach* Inspired from the Model driven architecture. If define job archetype on all the instances (models) we should be able to apply a sort of transformation to swicth from an archetype to another? *Work by increment* Reconsider the concept of copied job. Instance of copy the whole config.xml into a new_config.xml, we can imagine to reference the original copied job and keep the increment. E.g: My_JOB_MVN3.xml = My_JOB_MVN3.xml + INCEREMENT.xml Instead of copying My_JOB_MVN3.xml we can image to have a repository of jobs, and the increment just store the delta. *Object oriented approach* The aim is to use inheritance for default values and override specific behaviors. What's your thoughts?
Re: Back ports to LTS 1.447.2
Can you back port this one too: JENKINS-12928: Job name Enforcerhttps://issues.jenkins-ci.org/browse/JENKINS-12928 It's available since the version 1.455. Thanks Le mardi 22 mai 2012 08:56:35 UTC+2, vjuranek a écrit : Hi, once again sorry for LTS delay. I find following issues to be back ported to LTS 1.447.2: Blockers or critical issues: * JENKINS-8663 - Parsing of POM happens before SNAPSHOT-Parents are updated * JENKINS-12994 - Quiet period is blocking other jobs in queue * JENKINS-13129 - Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup * JENKINS-13448 - Guice injector failure can cause failure of whole Jenkins Major issues (explicitly requested on dev list or IMHO possibly critical issues): * JENKINS-1152, JENKINS-3983 - Mail server rejecting emails from hudson, SMTP authentication not working * JENKINS-9882 - Jenkins runs out of file descriptors (winstone problem) * JENKINS-12674 - Too many files open causes Jenkins to stop responding * JENKINS-13238 - Loading All Build History Fails * JENKINS-13649 - Invalid environment variable values when running hierarchical jobs on windows slaves Any other proposals for back ports? Thanks Vojta
Re: Re: Back ports to LTS 1.447.2
Le jeudi 14 juin 2012 15:41:00 UTC+2, Jorg Heymans a écrit : OK cool, i'll wait a couple more weeks then to plan our upgrade. We're currently still on 1.427 :) Jorg On Thursday, June 14, 2012 10:21:48 AM UTC+2, vjuranek wrote: Hi Jorg, LTS based on new Jenkins version is released in interval of roughly 3 months and it's rather collective decision made on Jenkins governance meetings (for detail see [1]). As 1.447.1 was release by end of March, I would expect 1.4XY.1 by beginning of July. I put it on next meeting agenda [2] to choose baseline for new LTS. But as current LTS is based on 1.447, features added in 1.448 should be definitely present in new LTS, no matter what the new baseline will be. Cheers Vojta [1] https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line [2] https://wiki.jenkins- ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda- June27thMeetinghttp://ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-June27thMeeting On Thursday 14 June 2012 00:54:48 Jorg Heymans wrote: Hi Vojta, At what point will LTS be based on a new Jenkins version ? I was hoping to use the repository per executor feature that was added in 1.448, any idea when this will get added to the LTS branch ? Thanks Jorg Heymans On Tuesday, May 22, 2012 8:56:35 AM UTC+2, vjuranek wrote: Hi, once again sorry for LTS delay. I find following issues to be back ported to LTS 1.447.2: Blockers or critical issues: * JENKINS-8663 - Parsing of POM happens before SNAPSHOT-Parents are updated * JENKINS-12994 - Quiet period is blocking other jobs in queue * JENKINS-13129 - Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup * JENKINS-13448 - Guice injector failure can cause failure of whole Jenkins Major issues (explicitly requested on dev list or IMHO possibly critical issues): * JENKINS-1152, JENKINS-3983 - Mail server rejecting emails from hudson, SMTP authentication not working * JENKINS-9882 - Jenkins runs out of file descriptors (winstone problem) * JENKINS-12674 - Too many files open causes Jenkins to stop responding * JENKINS-13238 - Loading All Build History Fails * JENKINS-13649 - Invalid environment variable values when running hierarchical jobs on windows slaves Any other proposals for back ports? Thanks Vojta Le jeudi 14 juin 2012 15:41:00 UTC+2, Jorg Heymans a écrit : OK cool, i'll wait a couple more weeks then to plan our upgrade. We're currently still on 1.427 :) Jorg On Thursday, June 14, 2012 10:21:48 AM UTC+2, vjuranek wrote: Hi Jorg, LTS based on new Jenkins version is released in interval of roughly 3 months and it's rather collective decision made on Jenkins governance meetings (for detail see [1]). As 1.447.1 was release by end of March, I would expect 1.4XY.1 by beginning of July. I put it on next meeting agenda [2] to choose baseline for new LTS. But as current LTS is based on 1.447, features added in 1.448 should be definitely present in new LTS, no matter what the new baseline will be. Cheers Vojta [1] https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line [2] https://wiki.jenkins- ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda- June27thMeetinghttp://ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-June27thMeeting On Thursday 14 June 2012 00:54:48 Jorg Heymans wrote: Hi Vojta, At what point will LTS be based on a new Jenkins version ? I was hoping to use the repository per executor feature that was added in 1.448, any idea when this will get added to the LTS branch ? Thanks Jorg Heymans On Tuesday, May 22, 2012 8:56:35 AM UTC+2, vjuranek wrote: Hi, once again sorry for LTS delay. I find following issues to be back ported to LTS 1.447.2: Blockers or critical issues: * JENKINS-8663 - Parsing of POM happens before SNAPSHOT-Parents are updated * JENKINS-12994 - Quiet period is blocking other jobs in queue * JENKINS-13129 - Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup * JENKINS-13448 - Guice injector failure can cause failure of whole Jenkins Major issues (explicitly requested on dev list or IMHO possibly critical issues): * JENKINS-1152, JENKINS-3983 - Mail server rejecting emails from hudson, SMTP authentication not working * JENKINS-9882 - Jenkins runs out of file descriptors (winstone problem) * JENKINS-12674 - Too many files open causes Jenkins to stop responding * JENKINS-13238 - Loading All Build History Fails * JENKINS-13649 - Invalid environment variable values when running
Jenkins CLI documentation
Hi guys, I'm currently trying to automate some Jenkins admin tasks. Naturally, I've tryed jenkins-cli.jar, it's a really pleasure to play with it! But (there is always a but in this ML ;-) ), it seems like the CLI tool have some issues. For instance, try to use the login command with the --username option --username is not a valid option IMHO, we could add more documention regarding this tool. I want to establish a compatible matrix to know which commands and option work. But I don't which version should I take as reference? The lastest one? The latest LTS seems legit. What do you think about it? The last question but not the least, does the SSH server will replace the cli tool? Cheers Daniel
Re: Jobs naming convention enforcer
https://lh3.googleusercontent.com/-tL5LK3Cyyy0/T0qsGQcXCWI/BiE/4ghBRFjFGXM/s1600/NotMatching.png https://lh3.googleusercontent.com/-J56nbTw8G14/T0qsAkyu1eI/Bh8/n-tc134HyJg/s1600/GlobalConfig.png Hi guys, thanks for your answers. @Jacob I do the same trick, but it's not enought. I need to be more strict @domi As a Quick and Dirty try, I've made a prototype. Have a look at the attachments. In the Gobal config page, I can specify a regexp-based naming convention. Then when I try to create a new job, if it doesn't match the pattern an error message appears. In practice, I've modified the Jenkins core and war. It bothers me to modified these core components... but I dont know how to make it in another way. What do you thing about this QD solution? I would appreciate more coments/opinions to open an Enhancement Request. Cheers Daniel
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 * *
Re: Jenkins User Conference T-Shirts
+1 for butler seating in front of Eiffel tower with wine glass
