Re: maintainer requests
Sure, no problem for me :) Frédéric Camblor <http://fcamblor.wordpress.com/> <http://www.twitter.com/fcamblor> BDX.io <http://bdx.io> Leader Restx <http://restx.io/> commiter Jenkins <http://jenkins-ci.org/> community member & plugin commiter On Thu, Oct 27, 2016 at 4:51 PM, Daniel Beck <m...@beckweb.net> wrote: > > > On 21.10.2016, at 23:08, Greg Langston <glangsto...@gmail.com> wrote: > > > > https://wiki.jenkins-ci.org/display/JENKINS/NodeJS+Plugin > > https://wiki.jenkins-ci.org/display/JENKINS/AWS+Cloudformation+Plugin > > https://wiki.jenkins-ci.org/display/JENKINS/Amazon+ECR > > > > There are a couple of abandoned plugins I'd like to assist in > maintaining. > > > > let me know please if you have additional questions for me. > > > > Github ID: glangston83 > > Jenkins Infra ID: glangston83 > > Hi Greg, > > Regarding NodeJS, I'm CC'ing Frédéric Camblor to get confirmation that > he's no longer maintaining it and fine with you taking over. > > Regarding AWS Cloudformation, I'm still finding out whether it actually is > abandoned. > > Regarding ECR Plugin: In the mean time, Ivan Fernandez Calvo has > volunteered to maintain this. Are still interested in co-maintaining it? > > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CADH39nqPuC6h9sKX7WsTdmyzPFMc7KxAPFxujuOWCniYg5pVnQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Request to become maintainer of SCM Sync plugin
As I mentioned in the PR #31, I'm strongly in favor of bringing new blood to this plugin as I cannot dedicate much time to it, ans, like you said, there are a tons of PR pending currently +1 then :) @Craig don't you have jenkinsci plugins commit accesses already ? If not, could a jenkins folk provide him commit access to plugins ? Cheers, Frédéric Camblor <http://fcamblor.wordpress.com/> <http://www.twitter.com/fcamblor> BDX.io <http://bdx.io> & Bordeaux JUG <http://bordeauxjug.org/> Leader Restx <http://restx.io/> commiter Jenkins <http://jenkins-ci.org/> community member & plugin commiter On Tue, Nov 10, 2015 at 9:49 PM, Craig Rodrigues <rodr...@freebsd.org> wrote: > Hi, > > Plugin: > https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin > https://github.com/jenkinsci/scm-sync-configuration-plugin > > GitHub ID: rodrigc > > I'd like to request to become a maintainer of the SCM Sync plugin. > There are some pull requests pending which fix many issues, > but the existing plugin maintainer mentioned that he does not have > time to maintain this plugin: > > https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/31 > > I'd like to work on getting these fixes in and releasing a new plugin. > -- > Craig > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CADH39npUfKJpPK-5p%3DwmHiFitXr_v3of25r-92mFUV50hrZFEQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Need review on PR for nodejs crawler in infra's backend-crawler
Hi all, I'd need some code review on PR https://github.com/jenkinsci/backend-crawler/pull/18 : it is my first autoinstaller, so I don't want to merge this on my own (moreover, I don't know if there is something to tackle on info to take this new crawler into consideration). I can't release new version of the nodejs pluginhttps://wiki.jenkins-ci.org/display/JENKINS/NodeJS+Plugin(with autoinstaller support) unless the crawler makes available nodejs available installations. Thanks in advance. Frédéric Camblor http://fcamblor.wordpress.com/ http://www.twitter.com/fcamblor Bordeaux JUG http://bordeauxjug.org/ Leader Jenkins http://jenkins-ci.org/ community member plugin commiter -- 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: Autoinstaller plugin providing directory to the PATH
Thanks to both of you, I should achieve what I want with these hints/examples :-) @Oleg Didn't knew of this two plugins which sound great ! Unfortunately, I already implemented everything in the NodeJS plugin which should make your Custom Tools Plugin example even easier by not having to write any line of code :-) ... but the initiative is cool to have a simple workaround to install something which hasn't any autoinstaller yet. Thanks again :) Frédéric Camblor http://fcamblor.wordpress.com/ http://www.twitter.com/fcamblor Bordeaux JUG http://bordeauxjug.org/ Leader Jenkins http://jenkins-ci.org/ community member plugin commiter On Thu, Aug 1, 2013 at 8:30 AM, Oleg Nenashev o.v.nenas...@gmail.comwrote: Hello, Probably, you could use Custom Tools Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Custom+Tools+Plugin. Via this plugin you can specify your own tools and installers. Version 0.3 will add support of the variables and label-specific installation options. If you need to specify path w/o any installation steps, you can use Extra Tool Installers Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Extra+Tool+Installers+Plugin Best regards, Oleg Nenashev среда, 31 июля 2013 г., 2:07:18 UTC+4 пользователь Frédéric Camblor написал: Hi everyone, I'm lacking in Jenkins API knowledge to be able to provide a specific directory to the PATH variable during a job execution only. My need : I'm enhancing the NodeJS plugin with NodeJS npm auto-installers. Once installed, node has a bin/ directory with potentially lots of executables inside it (when a new npm package is installed, it might add new executable to this bin/ folder). I'd like to provide some build step allowing to add NodeJS installation's bin/ folder to the PATH variable, during a specific build execution. It could then make it possible to call some npm executables during shell executed scripts (such as grunt, bower, jasmine and so on...) I tried appending launcher.env(PATH=/path/to/**node/bin:existing PATH value), but it didn't seemed to work (executable not found). If you have any input/doc to help me, I take it ! :-) Thanks in advance, Frédéric Camblor http://fcamblor.wordpress.com/ http://www.twitter.com/fcamblor Bordeaux JUG http://bordeauxjug.org/ Leader Jenkins http://jenkins-ci.org/ community member plugin commiter -- 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. -- 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.
Autoinstaller plugin providing directory to the PATH
Hi everyone, I'm lacking in Jenkins API knowledge to be able to provide a specific directory to the PATH variable during a job execution only. My need : I'm enhancing the NodeJS plugin with NodeJS npm auto-installers. Once installed, node has a bin/ directory with potentially lots of executables inside it (when a new npm package is installed, it might add new executable to this bin/ folder). I'd like to provide some build step allowing to add NodeJS installation's bin/ folder to the PATH variable, during a specific build execution. It could then make it possible to call some npm executables during shell executed scripts (such as grunt, bower, jasmine and so on...) I tried appending launcher.env(PATH=/path/to/node/bin:existing PATH value), but it didn't seemed to work (executable not found). If you have any input/doc to help me, I take it ! :-) Thanks in advance, Frédéric Camblor http://fcamblor.wordpress.com/ http://www.twitter.com/fcamblor Bordeaux JUG http://bordeauxjug.org/ Leader Jenkins http://jenkins-ci.org/ community member plugin commiter -- 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: Autoinstaller plugin providing directory to the PATH
I already looked at the code of the plugin. But I don't think it will help in my case because I think it is related to the *specific* way PATH variable is handled during shell scripts. Cause when I explicitely override PATH values, it isn't taken into account. This is maybe my fault (I don't override PATH in the good place), but I didn't see anything in EnvInject being able to help me (I didn't spent hours on its code either) Frédéric Camblor http://fcamblor.wordpress.com/ http://www.twitter.com/fcamblor Bordeaux JUG http://bordeauxjug.org/ Leader Jenkins http://jenkins-ci.org/ community member plugin commiter On Wed, Jul 31, 2013 at 12:37 AM, Marc MacIntyre marc...@purestorage.comwrote: envinject plugin will probably solve this for you: https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin On Tue, Jul 30, 2013 at 3:07 PM, Frédéric Camblor fcamb...@gmail.comwrote: Hi everyone, I'm lacking in Jenkins API knowledge to be able to provide a specific directory to the PATH variable during a job execution only. My need : I'm enhancing the NodeJS plugin with NodeJS npm auto-installers. Once installed, node has a bin/ directory with potentially lots of executables inside it (when a new npm package is installed, it might add new executable to this bin/ folder). I'd like to provide some build step allowing to add NodeJS installation's bin/ folder to the PATH variable, during a specific build execution. It could then make it possible to call some npm executables during shell executed scripts (such as grunt, bower, jasmine and so on...) I tried appending launcher.env(PATH=/path/to/node/bin:existing PATH value), but it didn't seemed to work (executable not found). If you have any input/doc to help me, I take it ! :-) Thanks in advance, Frédéric Camblor http://fcamblor.wordpress.com/ http://www.twitter.com/fcamblor Bordeaux JUG http://bordeauxjug.org/ Leader Jenkins http://jenkins-ci.org/ community member plugin commiter -- 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. -- Marc MacIntyre -- 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. -- 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.
