Re: How to contribute to jenkins sci

Hi, thanks for the interest! We aggregate the project-wide contributing guidelines here: https://jenkins.io/participate/ If you want to contribute a fix, it would be the best starting point Regarding the referenced issue, I have assigned it to a proper JIRA component. Hopefully it helps, Oleg

[JEP-200] - Status update, retrospective, and changes in maintenance on May 01

Hi all, I would like to provide a status update regarding JEP-200 stories. It has been more than 3 months since the original release in Jenkins 2.102 and one month since the release in LTS (announcement

[Newbie] Declarative Pipeline agent/docker directive causing script.sh not found error

New Item > Pipeline > Pipeline script pipeline { agent { docker 'maven:3-alpine' } stages { stage('Example Build') { steps { sh 'mvn -B clean verify' } } } } Error: Started by user Calvin Running in Durability level:

How to contribute to jenkins sci

Hi, My self, Prince Raj Kumar working for Adobe. I am working on a project, which are totally based on jenkins. I am using jenkins declarative pipeline. I found some of the issues in it, also logged under jenkins-issues, but not found any update. Issues link:

Re: Correct jelly control file location

On Tue, Apr 24, 2018 at 1:53 PM, Greg Allen wrote: > I have created my own jelly control that I have placed in my maven project > at src/main/resources/lib/form/mycontrol.jelly. The `/lib/form` namespace is reserved by Jenkins core and you may not use it for your own controls.

Re: Request access to join the Jenkins CERT team

Belated +1 On Tuesday, April 24, 2018 at 1:13:55 PM UTC+2, Daniel Beck wrote: > > > > On 2. Apr 2018, at 10:44, Ivan Fernandez Calvo > wrote: > > > > I would like to request access to join the Jenkins CERT team. > > > > I approve this request. Welcome aboard. > > --

Correct jelly control file location

I have created my own jelly control that I have placed in my maven project at src/main/resources/lib/form/mycontrol.jelly. I then reference this tag in my jelly file like this: xmlns:d="jelly:define" xmlns:l="/lib/layout" xmlns:t="/lib/hudson" xmlns:f="/lib/form">        

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi Alex, If this version has been tested & run for 2 years in your company, I think it's okay to just apply this huge PR and refine the code quality & the comments later. But this is just my opinion, I'm not the maintainer. 2018-04-24 20:22 GMT+08:00 'Alexander Link' via Jenkins Developers <

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi Tony, We incorporated much of the feedback by Oleg (thanks again for the review!), but yes, I think there are still some unprocessed comments (those without +1 marker). We need to decide how urgent they are - currently we are not working on them due to capacity reasons. Nevertheless you

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

I did spend some time looking at that PR, but it appears as though there is still work to be done on it, or at least, changes requested. Is that not the case? I got a little lost trying to figure out what was still to be done. Tony On Tue, Apr 24, 2018 at 12:18 PM, 'Alexander Link' via Jenkins

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi, as Oleg mentioned we did many changes to this plugin in the last 2 years – in our fork unfortunately, since contribution did not work due to missing maintainers. You find *all* changes in our openSource branch:

Re: Request access to join the Jenkins CERT team

> On 2. Apr 2018, at 10:44, Ivan Fernandez Calvo > wrote: > > I would like to request access to join the Jenkins CERT team. > I approve this request. Welcome aboard. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

(offlist) I want to be clear: I was not singling you out or criticizing. This looks like a challenging thread, and you're doing a great job staying positive and open to ideas. If there's anything I can do to help just say so. Thanks for all your hard work, Liam Newman On Sun, Apr 22, 2018 at

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

I would like to point out that there is a major work being done on Pipeline compatibility in https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/32 . It would be great to invite Alejandra Ferreiro Vidal and Alexander Link to this discussion. Will do that. BR, Oleg On

Re: Request to become maintainer of the statistics-gatherer-plugin

Hi Luca, Please also take a look at the Daniel's comment. It really makes sense to ping the maintainer via another email before doing the release, just in case. Seems I missed Daniel's comment and expedited the permission transfer a bit. My apologies for that. My proposal would be to... -

Re: Request to become maintainer of the statistics-gatherer-plugin

Oh gosh, this is the messy GitHub PRs :-( I had actually two requests in the pipeline but when you create two PRs in a chain ... GitHub messes them up. Let me fix it manually and re-push. Luca. > On 24 Apr 2018, at 09:15, Oleg Nenashev wrote: > > Hi Luca, > > Thanks

Re: Request to become maintainer of the statistics-gatherer-plugin

Hi Luca, Thanks for the ping! Access to the repo granted. Regarding the release permissions, something is wrong in https://github.com/jenkins-infra/repository-permissions-updater/pull/670 . It refers another plugin you have created recently, but not Statistics gatherer. BR, Oleg On Tuesday,

Re: Request to become maintainer of the statistics-gatherer-plugin

Any updates? The timeout ended yesterday and we got no further feedback from the current maintainer. Thank you. Luca. > On 19 Apr 2018, at 22:48, Oleg Nenashev wrote: > > +1. If there is no response, let's transfer ownership once the response > timeout expires > >