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

Any updates here? Specifically asking for: https://github.com/jenkinsci/amazon-ecs-plugin/pull/48 -- 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

Re: Coexistence of two equal plugins

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 drop-down and I > wanted a textbox. Once modified, my idea was to upload this version of > plugin and at the same time keep the previous one

Coexistence of two equal plugins

Hi, I modified a Jenkins plugin in which there was a drop-down and I wanted a textbox. Once modified, my idea was to upload this version of plugin and at the same time keep the previous one unchanged, so as not to disrupt the execution of other jobs that use it. I have changed the

f:select with multiple attribute

Hi All, I have a in my Builder config.jelly which is populated by the BuilderDescriptor Everything works fine, the user can select multiple options that are correctly stored and used in the build. However, when the user goes back to the job configure page, the options are not selected. I can

Re: Team/repo associations cleanup: You may have lost some permissions today

Oliver, I don't understand what you're asking for. > On 28. Nov 2017, at 20:26, Oliver Gondža wrote: > > Some of these are maintained by us, please grant access to olivergondza for: > > - exclude-matrix-parent You already have write via Everyone, unchanged from yesterday.

Re: Team/repo associations cleanup: You may have lost some permissions today

On 2017-11-28 14:59, Daniel Beck wrote: So, if you lost access to any of these repos today, this is the reason. Please respond to this thread, or ping me on IRC, to get your access restored, if you are a (co)maintainer of any of these: Some of these are maintained by us, please grant access

Re: Remote Parameterized Trigger Plugin

Did anyone ever get access to commit? I was hoping to request to be a maintainer as well. I found that the plugin was doing a fire and forget, so I fixed that with one of my pull requests. I also see pull request https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/32 is

Re: Removing the Everyone team in the jenkinsci GitHub org

On Tue, Nov 28, 2017 at 11:30 AM, Daniel Beck wrote: > I've chewed through 4+ hours worth of API rate limits just with the basic > approach I've used yesterday to list existing permissions. Enumerating all > merged PRs for all repos, then looking at who merged them, plus

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 16:46, Jesse Glick wrote: > > I was just unclear on why you think we cannot > detect maintainer-like actions (merging PRs, cutting releases) with > decent confidence. Note that the GH API doesn't work just based on Git data (in fact, those are

Re: Removing the Everyone team in the jenkinsci GitHub org

+1, go-go-gadget githubfixings On Tue, 28 Nov 2017, Daniel Beck wrote: > Hi everyone, > > For a long time, we didn't really manage GitHub permissions for plugins: We > just added new repos and contributors to the 'Everyone' team, giving everyone > access to everything, and that was it.

Re: Team/repo associations cleanup: You may have lost some permissions today

I seem to have lost the ability to control settings on the git-plugin repository. Could you add me to a group that has admin permissions for https://github.com/jenkinsci/git-plugin ? Mark Waite On Tue, Nov 28, 2017 at 6:59 AM Daniel Beck wrote: > Hi everyone, > > In

Re: Removing the Everyone team in the jenkinsci GitHub org

Generally +1 for sure. Minor comment: On Mon, Nov 27, 2017 at 7:25 PM, Daniel Beck wrote: > Have at least 5 'contributions' (~commits in the contributors graph) > > […] GitHub makes it impossible to efficiently determine who has performed > various maintainer-specific actions,

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

On Mon, Nov 27, 2017 at 7:56 PM, Stephen Connolly wrote: > any other user provided handler could [also queue unformatted log records] Theoretically. I cannot think of any such case. Handlers are known to be registered by Jenkins core; the `support-core` plugin;

Team/repo associations cleanup: You may have lost some permissions today

Hi everyone, In preparation for the larger Everyone permissions cleanup[1] I wrote a script determining collaborators/contributors for every plugin. Reviewing its output, I found ~40 repos that had broken team/repo associations, i.e. per-repo teams that grant access to repositories other than

Re: Testing Jenkins Plugins

hi, Is there a way to check or update the configuration of jenkins instance that is created for each test? -- 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

Re: Removing the Everyone team in the jenkinsci GitHub org

+1. A sensible move for sure. With hundreds of repos and hundreds of committers, /some/ segregation can definitely help avoid screwing up, even from non malicious users. Thanks Daniel for that cleanup 2017-11-28 11:50 GMT+01:00 Daniel Beck : > > > On 28. Nov 2017, at 11:26,

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 11:26, Robert Sandell wrote: > > A mid sized pr normally sits around 5 commits, so does one merged pr count as > five contributions? > I think so (perhaps unless squashed?). Note that this does not grant additional commit access to people who

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 04:58, Kohsuke Kawaguchi wrote: > > If this change inadvertently remove somebody's commit access, presumably we > expect people to follow this and mail this list? Or just email this list in panic/rage without following a guide ;-) That's why I plan to

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 03:39, Mark Waite wrote: > > I won't remove "Everyone" from the git-client-plugin or the git-plugin until > after you've made the change, since removing that group would remove write > permission for key people (Stephen, Jesse, Sam, Liam,

Re: Removing the Everyone team in the jenkinsci GitHub org

> 3. Have at least 5 'contributions' (~commits in the contributors graph) A mid sized pr normally sits around 5 commits, so does one merged pr count as five contributions? /B 2017-11-28 4:58 GMT+01:00 Kohsuke Kawaguchi : > Thanks for driving this. > > If this change

Re: Docker agent build script wrapper

Hi, next release of docker-plugin is going to introduce "dockerNode" keyword in pipeline, so you can create an agent from a docker image: dockerNode(dockerHost: 'unix:///var/run/docker.sock', image: 'jenkins/slave', remoteFs: '/home/jenkins') { sh 'echo "hello there"' } this is still under