Retrieving the PluginFirstClassLoader...

Hi all, Currently I'm working on a plugin, which uses the PluginFirstClassLoader to avoid library clashes with Jenkins

Re: Interested in building your plugin on ci.jenkins.io?

Hi, will there be any support for Xbuild ? so that a combined java & c# plugin can be built? if so, I'd like the hp automation tools plugin to be built on that and i'll write the Jenkinsfile. thanks Fima. On Monday, August 8, 2016 at 6:48:24 PM UTC+3, R Tyler Croy wrote: > > Howdy there, your

Re: [Experiment] Reviewers Team

Small bump: reminder this list https://github.com/orgs/jenkinsci/teams/code-reviewers is open to *anyone* willing to review Jenkins code in general (core or plugins). Either you want to grow your skills, or help in general, or both, this is one good place. Note that being part of that team does

Re: Plugin to hide/mask/obfuscate regex in all build output?

You can normally ping the maintainer, but in general s/he should already have been notified... If there's one... If not, which is not always clear, well then you can take over that maintenance yourself. To get review, you can try pinging the jenkinsci/code-reviewers team. Cheers Le 9 août 2016

Re: Programmatically reuse Credentials from the SCM plugin

On Tuesday 9 August 2016, Rafael Rezende wrote: > - is there any use case where a user may actually want to use different >> credentials in the build step than in the checkout? >> > *No.* They should be always the same. > > - are you writing a pipeline capable build step

Re: Backporting for LTS 2.7.3 started

Thanks On 9 August 2016 at 15:26, Oliver Gondža wrote: > On 2016-08-09 14:37, Stephen Connolly wrote: > >> So can we get JENKINS-37189 backported? >> > > It is there, together with JENKINS-35493. > > -- > oliver > > -- > You received this message because you are subscribed to

Re: Plugin to hide/mask/obfuscate regex in all build output?

Jesse, or any Jenkins devs, Is there anyone I can ping directly about this pull request? I've never contributed to a Jenkins plugin before... any idea what I can expect in terms of upstream response to this? Thanks, Jason On Thursday, August 4, 2016 at 11:03:04 AM UTC-4, Jason Antman wrote: >

Re: Backporting for LTS 2.7.3 started

On 2016-08-09 14:37, Stephen Connolly wrote: So can we get JENKINS-37189 backported? It is there, together with JENKINS-35493. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Different config.jelly for freestyle and pipeline

On Tue, Aug 9, 2016 at 4:50 AM, Markus Axelsson wrote: > Is it possible for Jenkins to load different config.jelly depending if it's > a Freestyle project or a Pipeline project that is using the plugin? I suppose you could check information about `it`. > I need to

Re: Backporting for LTS 2.7.3 started

So can we get JENKINS-37189 backported? On 8 August 2016 at 17:30, Stephen Connolly wrote: > https://github.com/jenkinsci/jenkins/pull/2500 is something that we > really need and it should be very low risk > > On 8 August 2016 at 13:00, Oliver Gondža

Re: Programmatically reuse Credentials from the SCM plugin

> > - is there any use case where a user may actually want to use different > credentials in the build step than in the checkout? > *No.* They should be always the same. - are you writing a pipeline capable build step or one specifically > tailored for use in old-style jobs only? > *Yes.*

Re: Removing name autocompletion in new job creation

Why move the input Vs the warning text? On 9 August 2016 at 06:45, Samat Davletshin wrote: > The autocomplete parameter is not specified in jelly so I believe it is > browser behavior remembering name="name" input. > > In #2501

Different config.jelly for freestyle and pipeline

Is it possible for Jenkins to load different config.jelly depending if it's a Freestyle project or a Pipeline project that is using the plugin? I'm thinking that this would make it easier to ensure backwards compatibility since I need to make modifications to config.jelly to make the plugin

Re: Programmatically reuse Credentials from the SCM plugin

On Monday 8 August 2016, Rafael Rezende wrote: > I'm developing a plugin that depends on the Team Concert plugin > . *TC > plugin* has a Credentials field, used to connect to the Team Concert > server. > My

Re: WorkflowMultiBranchProject getLastBuild

> > On Mon, Aug 8, 2016 at 4:31 AM, Sverre Moe > wrote: > > I just need the last build from an upstream dependency. The upstream > build > > cause might be an upstream dependency, or it may be an SCM cause. Such > that > > the upstream project might not be the upstream