Re: [configuration-as-code] Descriptors configuration

Thanks ! 2017-11-27 23:53 GMT+01:00 Jesse Glick : > On Fri, Nov 24, 2017 at 8:17 AM, nicolas de loof > wrote: > > I'm looking if stapler can > > easily answer "does this descriptor have a global view" without making > > assumption on the view

Re: Removing the Everyone team in the jenkinsci GitHub org

Thanks for driving this. If this change inadvertently remove somebody's commit access, presumably we expect people to follow this and mail this list? On Mon, Nov 27, 2017 at 4:25 PM Daniel Beck

Re: Removing the Everyone team in the jenkinsci GitHub org

That sounds reasonable to me. 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, etc.). I don't seem to be able to add people to either the

Re: Removing the Everyone team in the jenkinsci GitHub org

Great - thanks for your help Daniel! Richard. On Tue, 28 Nov 2017 at 14:13 Daniel Beck wrote: > > > On 28. Nov 2017, at 01:39, Richard Bywater wrote: > > > > Should a plugin maintainer have full admin access to the repo? Reason I > ask is that I recently

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 01:39, Richard Bywater wrote: > > Should a plugin maintainer have full admin access to the repo? Reason I ask > is that I recently took over as maintainer for the HTML publisher plugin but > don't have any access outside of committing etc. As the

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

On Mon 27 Nov 2017 at 22:51, Jesse Glick wrote: > On Wed, Nov 22, 2017 at 2:07 PM, Stephen Connolly > wrote: > > there is the logging of incorrect values > > I guess this is a concern according to the handler. > `Logger.log(LogRecord)`

Re: Removing the Everyone team in the jenkinsci GitHub org

That sounds like a reasonable approach to me. Semi related question re "I know that quite a few plugin maintainers have long removed the Everyone team from their plugin repositories to prevent such problems, but the default is still to add the team to a new plugin repo." Should a plugin

Removing the Everyone team in the jenkinsci GitHub org

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. Contrary to its name, it doesn't actually include _everyone_, at least not anymore:

Re: [configuration-as-code] Descriptors configuration

On Fri, Nov 24, 2017 at 8:17 AM, nicolas de loof wrote: > I'm looking if stapler can > easily answer "does this descriptor have a global view" without making > assumption on the view template language Try `Descriptor.getGlobalConfigPage`. -- You received this message

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

On Wed, Nov 22, 2017 at 2:07 PM, Stephen Connolly wrote: > there is the logging of incorrect values I guess this is a concern according to the handler. `Logger.log(LogRecord)` calls `Handler.publish` synchronously. And typical handlers would then format the

Docker agent build script wrapper

Hi, We are building scientific model running and testing environment product. We use Jenkins as a core building, integration and model running tool. Now our users are scientist and have little technological background so we look to fold our current Jenkinsfile into something more compact and