[Job DSL] Extend the context of another plugin?

[Dan Alvizu]

 

Hi,


I am using the Job DSL plugin on my project. I have a proprietary plugin, 
part of which is

a provider of parameters for the parameterized-trigger plugin. This allows 
me to trigger

a deployment with properties specified by my plugin:


```

*  public class *MyCustomBuildParameters
  *extends *hudson.plugins.parameterizedtrigger.AbstractBuildParameters
  {

// ...

@Extension
*public static class *DescriptorImpl *extends *
Descriptor
{

  // ...

}

  }

```


This works great in the UI - I would like to be able to specify this 
somehow as part of a job DSL:


```

  job('example') {



publishers {

  // ...

  downstreamParameterized{

trigger('') {

   *myCustomParameters()*

}

  }

}

  }

```


However it's not clear to me from reading the wiki how this would be done:


https://github.com/jenkinsci/job-dsl-plugin/wiki/Extending-the-DSL


The context of downstreamParameterized() (
javaposse.jobdsl.dsl.helpers.common.DownstreamTriggerParameterContext) is 
not marked as an ExtensibleContext, so I cannot simply add a 
ContextExtension point and a method with @DslExtensionMethod, as I could if 
this were the PublisherContext.


Is there an example out there I can reference, or can someone please point 
me in the right direction?


Thanks!

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8d834961-ff42-4e02-99b1-1108835b1fe7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins-events] Proposal: revisiting JUC in 2016

[Alyssa Tong]

Washington DC had great turnout for JUC this year. I'll put this in the
suggestion box as well :o)

@ Jonathan, would you be interested in being a JAM
 organizer
for the DC area? There were 400+ attendees at JUC DC this year so there's
definitely Jenkins interest.

thnx
alyssa

-- Forwarded message --
> From: Jonathan Jenkins 
> Date: Wed, Oct 21, 2015 at 10:34 AM
> Subject: Re: [Jenkins-events] Proposal: revisiting JUC in 2016
> To: Ioannis Moutsatsos , Jenkins Users <
> jenkinsci-us...@googlegroups.com>
> Cc: "eve...@lists.jenkins-ci.org" , "
> jenkinsci-dev@googlegroups.com" 
>
>
> Or Washington DC?  If DC, I can absolutely lend a hand.
>
>
>
>
>
> Jonathan Jenkins
>
> CEO/Chief Methodologist
>
> Certified SAFe Program Consultant (SAFe SPC), Certified Scrum Professional
> /Master (CSP/CSM)
>
> Mobile +1 240-271-0463
> jonathan.jenk...@clearlyagile.com | www.ClearlyAgile.com
> 
>
> LinkedIn 
>
>
>
> *From:* Jenkins-events [mailto:jenkins-events-boun...@lists.jenkins-ci.org]
> *On Behalf Of *Ioannis Moutsatsos
> *Sent:* Wednesday, October 21, 2015 7:03 AM
> *To:* Jenkins Users 
> *Cc:* eve...@lists.jenkins-ci.org; jenkinsci-dev@googlegroups.com
> *Subject:* Re: [Jenkins-events] Proposal: revisiting JUC in 2016
>
>
>
> Perhaps a global event on the East Coast (NY, Boston?) would be more
> accessible to both US and European audiences.
>
> Travel to and from these hubs is usually less expensive especially flying
> from/to Europe.
>
> Best regards
>
> Ioannis
>
>
> On Monday, October 19, 2015 at 10:51:43 PM UTC-4, Kohsuke Kawaguchi wrote:
>
> Putting my CloudBees hat on, I'd like to discuss the following proposed
> changes to the events in 2016, where we are moving away from JUC into a new
> model.
>
>
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Revisiting+JUC+in+2016
>
>
>
> I put this up for the project meeting agenda in 1.5 week, but I hope to
> get discussions going well before that.
>
>
>
> --
>
> Kohsuke Kawaguchi
>
>
> ___
> Jenkins-events mailing list
> jenkins-eve...@lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-events
>
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNaz3uOWBpSSVcDLR726wi5hzV66zwGmWm403kLtMWfLCeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

envinject: should it be able to set the workspace?

[martinda]

A while ago, I was able to use the envinject plugin to set the workspace 
path, but it does do that anymore. I wish I could control the workspace 
location for two reasons:
1) I need to share workspaces between jobs because of the large volume of 
data being produced (archiving is not practical)
2) Gradle is unable to continue a build when the absolute path to the build 
output changes 

.

Q) Is the envinject supposed to be able to control the workspace location?

Thanks,
Martin

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8e5769dd-958e-450e-a5d4-15c9157006f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 2.0 proposal

[Jesse Glick]

On Wed, Oct 21, 2015 at 1:28 PM, Kohsuke Kawaguchi  wrote:
> That there will be more of these problems down the road.

Perhaps. More important is the ongoing burden of not knowing whether
what you wrote in `src/main/java/**/*.java`, or what you loaded from
`*-sources.jar`, is actually what is running.

> I feel like we are throwing the baby out with the bathwater.

This baby is Otesánek. :-)

> it's not that problems are hard to understand or hard to fix.

For you perhaps.

> if you are going to remove BCT altogether, what do we do with existing
> uses of them? Queue.Item#id is a relatively recent change. Are we just going
> to break plugins that use them?

There was no fully developed proposal yet. My idea was to have an
automated system for detecting plugin source repos still using the
deprecated API, then fixing those, and concurrently blocking the old
plugin releases from being used. So a user would never see linkage
errors, but they might be required to upgrade a plugin when upgrading
core (or a lower-level plugin).

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3MSQ4pX14%3DdepUc%3D28WOV6Ny2RNyaCgN4Gkd65z1esVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Is ArtifactManager nonstandard?

['Laurence Bordowitz' via Jenkins Developers]

TL;DR should I use ArtifactManager in my plugin? If not, what direction should 
I take with this?
I'm looking to write a tool which archives artifacts without using the Jenkins 
filer. I'm aware of the S3 plugin, and I'm looking to make something like that 
for an internal storage solution kinda like S3.

I did some digging into the jenkins codebase, and I found that one could make 
their own "ArtifactManager" and "ArtifactManagerFactory," and this would 
suffice to archive artifacts. This is what the compress-artifacts-plugin does, 
and I will probably use that plugin as a template if I am going to use the 
ArtifactManager pattern. The question is whether to use it or not. The S3 
plugin doesn't use it, the copy artifacts plugin doesn't use it, the windows 
azure doesn't use it. In fact, I don't know of any plugin which uses the 
ArtifactManager other than Compress Artifacts and some proprietary CloudBees 
plugin.
-- Larry Bordowitz

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1277283664.1256713.1445455293346.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Looking for some help with a baffling plugin bug (ansicolor)

[Owen Mehegan]

Turns out this was a failure of the plugin to migrate its global 
configuration after some code was refactored. Open to any guidance about 
best practices for doing that cleanly during an upgrade.

On Monday, October 19, 2015 at 1:59:04 PM UTC-7, Owen Mehegan wrote:
>
> Myself and the maintainers of the jenkins-ansicolor plugin have been 
> struggling with a weird bug. So far I am the only one who can reproduce it, 
> and I can only repro it on my production Jenkins server. A 
> seemingly-identical test server does not exhibit the bug. We seem to have 
> exhausted most of the obvious possible causes. I have isolated the breakage 
> to a specific commit, but that hasn't helped us come up with a fix. I'm 
> hoping that getting some additional experienced eyes on the problem might 
> generate some other suggestions for how we could debug this (I'm also 
> personally limited in that I don't really know Java at all). My comment at 
> https://github.com/dblock/jenkins-ansicolor-plugin/issues/57#issuecomment-148869752
>  
> summarizes the current state of the bug.
>
> Thanks in advance to anyone who takes a look :) 
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/27c20efe-674f-47d3-9096-1fef1a749eff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 2.0 proposal

[Kohsuke Kawaguchi]

I feel like there's a gap in perception here. I'm sensing that you are
feeling that this is a systematic problem where fixing one problem at hand
wouldn't solve problems down the road. That there will be more of these
problems down the road.

In contrast, what I see is one bug (failing to update StackMapFrame) and
two failed attempts to fix it, and we are this close to fixing it properly.
And class file format change that drives issues like this only happens at
major Java releases, and Java9 has no such changes currently in it.
Hopefully this helps you see why I feel like we are throwing the baby out
with the bathwater.

And it's not that problems are hard to understand or hard to fix. What
makes this issue painful is that it blows up in unexpected places.

Anyway, I'm losing this argument.

Now, if you are going to remove BCT altogether, what do we do with existing
uses of them? Queue.Item#id is a relatively recent change. Are we just
going to break plugins that use them?


2015-10-20 14:40 GMT-07:00 Jesse Glick :

> On Tue, Oct 20, 2015 at 2:38 PM, Kohsuke Kawaguchi  wrote:
> > …this is relatively easily achievable by moving the transformed code
> into a
> > separate method so that bytecode index remain the same.
>
> I am not going to sleep more soundly tonight. :-)
>
> I think the broader issue is that use of runtime bytecode manipulation
> has proven to be subject to catastrophic bugs which are tricky to
> understand, much less fix. And pity the developer who attaches a Java
> debugger with a `*-sources.jar` and tries to step through rewritten
> code. We should be considering simpler, lower-tech options. If a field
> has been replaced with a getter, or whatever, let us make sure we fix
> the deprecated source code references and release those fixes and make
> sure users are not running the wrong version.
>


-- 
Kohsuke Kawaguchi

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xvMGgXCdVPttYu-_kD7YLmJqzkrn87gWY2K457pF87mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: 2.0 proposal

[Kanstantsin Shautsou]

That's what all people asking about last years, but there is number of old 
developers (not jenkins admins/users) that likes developing tricky code as 
it their main work.
KISS
On Wednesday, October 21, 2015 at 12:19:00 PM UTC+3, Artur Szostak wrote:
>
> Guys, are you writing compilers / compiler tools or a continuous 
> integration / deployment tool?
> Fix the API's, refactor the source code, update the plugin code and 
> recompile. Hop to it. ;-)
> Don't use these kinds of hacks. It leads to the dark side.
>
> Sorry if I sound harsh. But the things you are trying to do on a 
> supposedly production ready system are insane. You are all making me more 
> and more scared of upgrading or doing anything with my Jenkins system by 
> the minute. :-(
>
> Artur
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f7d45f90-acfa-4422-b584-367dc66c56c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: revisiting JUC in 2016

[Alyssa Tong]

I think meeting on the East Coast is a great idea. The challenge w/ NY is
that it's super expensive to do anything :o) and Boston had a good turn out
but the Bay Area seems to always have the greatest turn out, the attendance
in the Bay Area has doubled to tripled in # compared to other cities..

On Wed, Oct 21, 2015 at 4:02 AM, Ioannis Moutsatsos 
wrote:

> Perhaps a global event on the East Coast (NY, Boston?) would be more
> accessible to both US and European audiences.
> Travel to and from these hubs is usually less expensive especially flying
> from/to Europe.
>
> Best regards
> Ioannis
>
> On Monday, October 19, 2015 at 10:51:43 PM UTC-4, Kohsuke Kawaguchi wrote:
>>
>> Putting my CloudBees hat on, I'd like to discuss the following proposed
>> changes to the events in 2016, where we are moving away from JUC into a new
>> model.
>>
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Revisiting+JUC+in+2016
>>
>> I put this up for the project meeting agenda in 1.5 week, but I hope to
>> get discussions going well before that.
>>
>> --
>> Kohsuke Kawaguchi
>>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/7019b9c7-f27a-4d65-b346-c6ca90dfddfc%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNazmDdcWfZNEve1qEaMj9T%2B7jMm-nENGL9_VZ0NivVsPGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: 2.0 proposal

[Manuel Jesús Recena Soto]

I totally agree!

2015-10-21 11:18 GMT+02:00 Artur Szostak :
> Guys, are you writing compilers / compiler tools or a continuous integration
> / deployment tool?
> Fix the API's, refactor the source code, update the plugin code and
> recompile. Hop to it. ;-)
> Don't use these kinds of hacks. It leads to the dark side.
>
> Sorry if I sound harsh. But the things you are trying to do on a supposedly
> production ready system are insane. You are all making me more and more
> scared of upgrading or doing anything with my Jenkins system by the minute.
> :-(
>
> Artur
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3C350C9D1C9DEE47BAEA43102B433C9EBE5E1151%40HQMBX2.ads.eso.org.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CABa-UofeYEYYQZqH9k8CkTqkQWWDE0x469By1yDn%3DO6YVmj06A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: revisiting JUC in 2016

[Ioannis Moutsatsos]

Perhaps a global event on the East Coast (NY, Boston?) would be more 
accessible to both US and European audiences.
Travel to and from these hubs is usually less expensive especially flying 
from/to Europe.

Best regards
Ioannis

On Monday, October 19, 2015 at 10:51:43 PM UTC-4, Kohsuke Kawaguchi wrote:
>
> Putting my CloudBees hat on, I'd like to discuss the following proposed 
> changes to the events in 2016, where we are moving away from JUC into a new 
> model.
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Revisiting+JUC+in+2016
>
> I put this up for the project meeting agenda in 1.5 week, but I hope to 
> get discussions going well before that.
>
> -- 
> Kohsuke Kawaguchi
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7019b9c7-f27a-4d65-b346-c6ca90dfddfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: 2.0 proposal

[Artur Szostak]

Guys, are you writing compilers / compiler tools or a continuous integration / 
deployment tool?
Fix the API's, refactor the source code, update the plugin code and recompile. 
Hop to it. ;-)
Don't use these kinds of hacks. It leads to the dark side.

Sorry if I sound harsh. But the things you are trying to do on a supposedly 
production ready system are insane. You are all making me more and more scared 
of upgrading or doing anything with my Jenkins system by the minute. :-(

Artur

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3C350C9D1C9DEE47BAEA43102B433C9EBE5E1151%40HQMBX2.ads.eso.org.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin Build-name-updater

[Lev Mishin]

Thanks!

On Wed, Oct 21, 2015, 11:14 AM Oleg Nenashev  wrote:

> Hi Lev,
>
> I'll ping Kohsuke regarding the ownership handover.
>
> Best regards,
> Oleg
>
> среда, 21 октября 2015 г., 9:53:14 UTC+3 пользователь Lev Mishin написал:
>
>> sorry for the delay, I've just applied your comments
>>
>> On Saturday, October 17, 2015 at 7:05:07 PM UTC+3, Oleg Nenashev wrote:
>>>
>>> The response came in a separate thread. Added the plugin's maintainer to
>>> Cc.
>>> I'd bet that KK will allow it.
>>>
>>> I've also added some comments to your pull request
>>> . IMO
>>> needs an update before merging
>>>
>>> Hi,
 Great if you want to adopt a plugin.
 Please read and follow the small procedure here:
 https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Helpingandtakingoverdormantplugins

 Basically, the TL;DR is: you want to ping the current/last
 maintainer(s) to check they are OK to give ownership.
 If they give their agreement or don't answer within some days, then
 you'll be given permissions to become the official maintainer.

 Cheers

>>>
>>> среда, 14 октября 2015 г., 16:17:17 UTC+3 пользователь Lev Mishin
>>> написал:

 The last repo update was commited two years ago so the repo looks
 abandoned, could you give me write rights for it please?

 On Friday, October 9, 2015 at 7:24:55 PM UTC+3, Lev Mishin wrote:
>
>
>- Github link:
>
> https://github.com/Le0Michine/Jenkins-Build-name-updater-plugin/tree/master
>
>- Repo name: "Build-name-updater-plugin"
>- User name the same as in the URL
>- jenkins-ci.org username: Le0;
>- Description: my plugin updates a build name during the build
>process, it was necessary because custom build name could tell some 
> useful
>information. Sometimes we just unable to set custom build name before 
> build
>or in pre-build steps because we just don't know that so using my 
> plugin
>you can set the build name in a separate build step, you can use a 
> file in
>the build workspace or environment variable or both of them as the 
> build
>name source.
>
> --
>
> Kind regards,
> Lev Mishin
>
 --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/i9bjjyF75bw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/a8210308-b935-472b-8e6c-f538b8244a1b%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Kind regards,
Lev Mishin

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAGAc5LUUrw4tmHTbmy_07uckJt%2BVV_%2B6pM1sMPgP%3DDyNERe5AQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin Build-name-updater

[Oleg Nenashev]

Hi Lev,

I'll ping Kohsuke regarding the ownership handover.

Best regards,
Oleg

среда, 21 октября 2015 г., 9:53:14 UTC+3 пользователь Lev Mishin написал:
>
> sorry for the delay, I've just applied your comments
>
> On Saturday, October 17, 2015 at 7:05:07 PM UTC+3, Oleg Nenashev wrote:
>>
>> The response came in a separate thread. Added the plugin's maintainer to 
>> Cc.
>> I'd bet that KK will allow it. 
>>
>> I've also added some comments to your pull request 
>> . IMO 
>> needs an update before merging
>>
>> Hi,
>>> Great if you want to adopt a plugin.
>>> Please read and follow the small procedure here: 
>>> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Helpingandtakingoverdormantplugins
>>>
>>> Basically, the TL;DR is: you want to ping the current/last maintainer(s) 
>>> to check they are OK to give ownership.
>>> If they give their agreement or don't answer within some days, then 
>>> you'll be given permissions to become the official maintainer.
>>>
>>> Cheers
>>>
>>
>> среда, 14 октября 2015 г., 16:17:17 UTC+3 пользователь Lev Mishin написал:
>>>
>>> The last repo update was commited two years ago so the repo looks 
>>> abandoned, could you give me write rights for it please?
>>>
>>> On Friday, October 9, 2015 at 7:24:55 PM UTC+3, Lev Mishin wrote:


- Github link: 

 https://github.com/Le0Michine/Jenkins-Build-name-updater-plugin/tree/master
 
- Repo name: "Build-name-updater-plugin"
- User name the same as in the URL
- jenkins-ci.org username: Le0;
- Description: my plugin updates a build name during the build 
process, it was necessary because custom build name could tell some 
 useful 
information. Sometimes we just unable to set custom build name before 
 build 
or in pre-build steps because we just don't know that so using my 
 plugin 
you can set the build name in a separate build step, you can use a file 
 in 
the build workspace or environment variable or both of them as the 
 build 
name source.

 -- 

 Kind regards,
 Lev Mishin

>>>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a8210308-b935-472b-8e6c-f538b8244a1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: fixing tied label get/set vs configuration page

[Oleg Nenashev]

Hi.

The best recommendation would be to create a pull-request to Jenkins.
Then PR builder will build your code and run tests. If the build passes you 
will be also able to download Jenkins WAR file from there and reuse results.

For local tests you can also build with -DskipTests . It will prevent 
Windows failures on tests. Builds are supposed to pass on Windows as well, 
but we don't test this flow regularly.

BR, Oleg

вторник, 20 октября 2015 г., 8:01:27 UTC+3 пользователь mdonohue написал:
>
> I've been looking at some issues for the configurationslicing plugin, and 
> one that came up is https://issues.jenkins-ci.org/browse/JENKINS-29547 
> which says the configuration slice for 'tied label' ignores the value 
> 'master'.
>
> It looks like this is an issue with core jenkins, as I commented in the 
> issue.  The get/set functions enforce a representation invariant that 
> 'master' is saved as a null label, but the job configuration page doesn't 
> follow that invariant, and it bypasses the get/set functions.  Thus when 
> setting 'master' via the configuration slicing plugin, the job 
> configuration appears not to have a tied label at all.
>
> I have what I think is a reasonable fix for jenkins core, but I am unable 
> to get jenkins to build on Windows without errors.  
>
> My proposed fix is here, but I've thus far been unable to test it due to 
> Windows build issues: 
> https://github.com/mdonohue/jenkins/commit/2cb89d3e269318644fabd1acb4861690e662aef9
>  
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f77ec415-fb81-4527-8d51-5bd52a533bd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.