Re: Docker agent build script wrapper

> > We have reached acceptable solution for the problem. It is loading groovy > script with black magic around closure. Attaching code for the community > benefit. > It boils down to construct in the loaded groovy module: def container(myImageName, Closure body){

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 30. Nov 2017, at 00:17, Kanstantsin Shautsou > wrote: > > Kohsuke, do you publicly approve that jenkins is not the bazaar anymore? Could we please keep this thread focused on the specific proposed initiative? -- You received this message because you are

Re: Removing the Everyone team in the jenkinsci GitHub org

Last time Kohsuke blocked this question with his veto because jenkinsci should be a bazaar model (and everybody should be able to work on any plugin). What happened since last time when i (and some other persons) tried to implement this and remove RW from everyone? *Kohsuke, do you publicly

Re: Asking for commiter access to amazon-ecs-plugin

Hi Mathus, It would be great if any one can change the maintainer of this plugin to Douglas as he is willing to took it so that we can utilize this plugin , many of us are waiting to get this pull request merged. Thanks Surya On Thursday, 7 September 2017 17:33:57 UTC-4,

Re: Remote Parameterized Trigger Plugin

I can be the maintainer, do I need to start a new thread? GitHub and Jenkins Id are both: n360speed > > > I think that if you have questions about taking over the plugin you > could ask Daniel Beck (https://github.com/daniel-beck). > > I'm reading :-) > > -- You received this message

Re: [PROPOSAL] Change core logging from Java Utils Logging

> Am I the only one to think it strange that we are discussing using very limited core developer resources to replace a library used pervasively throughout the Jenkins code base with a functionally identical library with no demonstrable benefit to users and rather marginal impact on developers

Re: Jenkins 2.89.1 LTS RC testing started

On Wed, Nov 29, 2017 at 9:33 AM, Daniel Beck wrote: > We missed https://issues.jenkins-ci.org/browse/JENKINS-47909 because it was > kept open. Oops, my fault for not double-checking JIRA after seeing that the PR was merged. >

Re: [PROPOSAL] Split js-libs repo in individual repos (one per module)

On Wed, Nov 29, 2017 at 6:47 AM, Victor Martinez wrote: > I'd like to purpose to standardise as individual git repos therefore their > release lifecycle and versioning can be independent and also get the > benefits of using different parent POM versions. +1, makes

Re: Jenkins 2.89.1 LTS RC testing started

> On 23. Nov 2017, at 12:44, Daniel Beck wrote: > > https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.89.1-fixed are the > backported fixes. We missed https://issues.jenkins-ci.org/browse/JENKINS-47909 because it was kept open.

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 29. Nov 2017, at 09:56, Ullrich Hafner wrote: > > Seems that I still can push changes to my repositories but I cannot access > the settings anymore (e.g., edit the description, view the collaborators). AFAICT you never were. I've looked into this about a year

Re: Remote Parameterized Trigger Plugin

> On 29. Nov 2017, at 09:45, Alejandra Ferreiro Vidal > wrote: > > I did not get a reply for my last comment in this group. It didn't look like needing a response from anyone but eventual maintainers, and nobody has spoken up so far. While Alejandra, a colleague of

Re: Removing the Everyone team in the jenkinsci GitHub org

I don't think I've ever been able to access the settings and edit the description of the repos I maintain :'( /B 2017-11-29 9:56 GMT+01:00 Ullrich Hafner : > Seems that I still can push changes to my repositories but I cannot access > the settings anymore (e.g., edit

Re: Coexistence of two equal plugins

Class full name and artifact id, changing group id has no effect. /B 2017-11-29 4:53 GMT+01:00 Slide : > Please don't double post. > > On Tue, Nov 28, 2017, 16:50 Virginia Mesa wrote: > >> Hi, I modified a Jenkins plugin in which there was a

[PROPOSAL] Split js-libs repo in individual repos (one per module)

Hi there, I've seen when using maven multimodes git repos in Jenkins plugins are mostly based on the same general versioning, such as the previous pipeline-plugin , blueocean , but I've found a minor

Re: Removing the Everyone team in the jenkinsci GitHub org

Seems that I still can push changes to my repositories but I cannot access the settings anymore (e.g., edit the description, view the collaborators). Is this doable per IRC bot? How should the new structure in collaborators look like? I’m not sure if I just missed that part in your mail…

Re: Remote Parameterized Trigger Plugin

Hi Nabel, There is no one committed to maintain this plugin. It would be great if you request to be a maintainer https://jenkins.io/project/governance/#helping-and-taking-over-dormant-plugins, and also if you merge the pull request