Re: Building docker images with declarative pipeline

[Thomas Fjellstrom]

That would explain the complete lack of examples. I'm kindof surprised 
there wasnt some kind of mapping from plugin dsl to the new declarative 
syntax, to at least allow some use of the existing apis. The script blocks 
are good enough for now however.

Thanks :)

On Tuesday, February 14, 2017 at 2:35:19 PM UTC-7, Andrew Bayer wrote:
>
> Right now, we don't have a great answer for this other than to use 
> Scripted Pipeline docker.build(...) within a script { } block - we don't 
> allow "foo.bar()" or "foo = bar()" syntax in steps blocks in Declarative 
> unless they're within a script block. Anything within a script block 
> doesn't go through validation, so you can use the full Scripted Pipeline 
> syntax there. That said, we are thinking about how to make this clearer in 
> the future so that you can build/deploy images without having to use script 
> {}.
>
> A.
>
> On Tue, Feb 14, 2017 at 2:32 PM, Thomas Fjellstrom  > wrote:
>
>> Hi,
>>
>> I'm brand new to jenkins, and have been reading a lot about the pipeline 
>> plugin. I think I have a basic grasp of it, but I haven't been able to 
>> figure out the proper syntax to build docker images in a pipeline stage. I 
>> don't want to run the steps IN a docker container, but rather build 
>> containers (multiple containers) in a pipeline Jenkinsfile. I also have 
>> some other requirements, like accessing credentials setup in the jenkins 
>> interface, and a private docker registry.
>>
>> Any help would be appreciated.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/fff6ea30-6b51-4f46-8516-8da8026c4241%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6410aaa9-3702-4b3c-b2da-a2665326ee0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Shuffling Node Labels

[Emory Penney]

Hi,

I am trying to find a solution to a sort of strange problem.  I've noticed 
Jenkins picks nodes of a given label in the same order every time.  Our 
nodes each have one executor on them so we can spread our builds and tests 
across multiple nodes but this means that one of our testers is running a 
majority of the tests.  We would like to be able to "shuffle" the node 
labels, and get a more even spread of tests across the systems in the pool. 
 It would help us more easily determine if test failures are isolated to 
one particular tester or all systems of the same configuration.

Does anyone know of a plugin to do this?  Or some other way?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c3152cbf-91d4-48e0-aa57-2ecd5b209524%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Building docker images with declarative pipeline

[Thomas Fjellstrom]

Hi,

I'm brand new to jenkins, and have been reading a lot about the pipeline 
plugin. I think I have a basic grasp of it, but I haven't been able to 
figure out the proper syntax to build docker images in a pipeline stage. I 
don't want to run the steps IN a docker container, but rather build 
containers (multiple containers) in a pipeline Jenkinsfile. I also have 
some other requirements, like accessing credentials setup in the jenkins 
interface, and a private docker registry.

Any help would be appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fff6ea30-6b51-4f46-8516-8da8026c4241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is it possible to have pipeline-stage-view-plugin display skipped stages differently than the executed stages?

[Patrick Wolf]

This is included in Blue Ocean right now. If someone wants to build this
into Stage View the API is in place for it.

On Mon, Feb 13, 2017 at 8:02 AM, Roi Aldaag  wrote:

> In the pipeline-stage-view-plugin view it seems that all stages are
> displayed the same way regardless if they were executed or skipped.
> Is there a way to have a visual indication that the stage was skipped?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/2c34d8fd-8a70-4a44-9b10-d8f4f82fdfb5%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrick Wolf
Product Director - Jenkins
CloudBees

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAGDV0P-3WJYK5iWM%2B4PMomvL_58tzji31kXjj-Tbnb%3D36wiJKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

[Andrew Bayer]

Actually, I've created the JIRA -
https://issues.jenkins-ci.org/browse/JENKINS-42027

On Tue, Feb 14, 2017 at 12:40 PM, Andrew Bayer 
wrote:

> Verified - per-folder config settings persist, but global config settings
> do not. Whacky. We'll fix it, but please do open that JIRA.
>
> A.
>
> On Tue, Feb 14, 2017 at 12:36 PM, Andrew Bayer 
> wrote:
>
>> Ah, the label and registry settings - could you please open a JIRA for
>> that?
>>
>> On Tue, Feb 14, 2017 at 11:50 AM, Dan Tran  wrote:
>>
>>>
>>> all the settings   at   Manage Jenkins --> Configure System --> Pipeline
>>> Model Definition  are empty after jenkins restart
>>>
>>> The jobs are still available
>>>
>>> Thanks
>>>
>>> -Dan
>>>
>>> On Tuesday, February 14, 2017 at 2:12:48 AM UTC-8, Daniel Beck wrote:


 > On 14.02.2017, at 09:11, Dan Tran  wrote:
 >
 > all my Jenkins are losing  Pipeline Model Definition's settings after
 restart ( ie after plugin grade)
 >

 What 'settings' are you referring to? Are the jobs gone after restart?

 --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/52d59d7a-ee18-4a3f-88b1-33df772269fe%40g
>>> ooglegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdOaUop7xfe-0AHrv5_8OVp7m0uAPTGaF0yhaicF%3DzRsZaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

[Andrew Bayer]

Verified - per-folder config settings persist, but global config settings
do not. Whacky. We'll fix it, but please do open that JIRA.

A.

On Tue, Feb 14, 2017 at 12:36 PM, Andrew Bayer 
wrote:

> Ah, the label and registry settings - could you please open a JIRA for
> that?
>
> On Tue, Feb 14, 2017 at 11:50 AM, Dan Tran  wrote:
>
>>
>> all the settings   at   Manage Jenkins --> Configure System --> Pipeline
>> Model Definition  are empty after jenkins restart
>>
>> The jobs are still available
>>
>> Thanks
>>
>> -Dan
>>
>> On Tuesday, February 14, 2017 at 2:12:48 AM UTC-8, Daniel Beck wrote:
>>>
>>>
>>> > On 14.02.2017, at 09:11, Dan Tran  wrote:
>>> >
>>> > all my Jenkins are losing  Pipeline Model Definition's settings after
>>> restart ( ie after plugin grade)
>>> >
>>>
>>> What 'settings' are you referring to? Are the jobs gone after restart?
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-users/52d59d7a-ee18-4a3f-88b1-33df772269fe%
>> 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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdOZGG3%2B06H1gHe5vmQ_CAOLyJqGu4m0WOCjgS9AGDymyKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

[Andrew Bayer]

Ah, the label and registry settings - could you please open a JIRA for that?

On Tue, Feb 14, 2017 at 11:50 AM, Dan Tran  wrote:

>
> all the settings   at   Manage Jenkins --> Configure System --> Pipeline
> Model Definition  are empty after jenkins restart
>
> The jobs are still available
>
> Thanks
>
> -Dan
>
> On Tuesday, February 14, 2017 at 2:12:48 AM UTC-8, Daniel Beck wrote:
>>
>>
>> > On 14.02.2017, at 09:11, Dan Tran  wrote:
>> >
>> > all my Jenkins are losing  Pipeline Model Definition's settings after
>> restart ( ie after plugin grade)
>> >
>>
>> What 'settings' are you referring to? Are the jobs gone after restart?
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/52d59d7a-ee18-4a3f-88b1-33df772269fe%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdObyXBzO_k3U_L2Kq0GBko-pbhye0Cc3sahwfU7-g-NKMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

[Dan Tran]

all the settings   at   Manage Jenkins --> Configure System --> Pipeline 
Model Definition  are empty after jenkins restart

The jobs are still available

Thanks

-Dan

On Tuesday, February 14, 2017 at 2:12:48 AM UTC-8, Daniel Beck wrote:
>
>
> > On 14.02.2017, at 09:11, Dan Tran  
> wrote: 
> > 
> > all my Jenkins are losing  Pipeline Model Definition's settings after 
> restart ( ie after plugin grade) 
> > 
>
> What 'settings' are you referring to? Are the jobs gone after restart? 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/52d59d7a-ee18-4a3f-88b1-33df772269fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins integration with white source plugin

[Siva varma Datla]

I have a Jenkins pipeline build where I have to configure a whitesource 
plugin for which I have the API token but in pipeline builds there is no 
post build action so how can we make this plugin work just for one job. How 
to make this plugin work for my desired Jenkins pipeline build.
Any help is much appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9d46377d-8891-4247-8020-08bdf968bd5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Are there ways to set different reference build to plugin or set dynamic thresholds?

[esharish]

We have a master job that builds the master branch and various plugins
ex.warnings plugin tracks the  counts of warnings detected in master. 

Then we have a gerrit job that build the gerrit patches.The warnings plugin
and other plugins by default compare delta against previous successful
gerrit build. But we want to make compare warnings counts against the master
build instead. Is there some known way to specify to use a different job as
reference? 

I can think of following roundabout ways. 
1. Execute post-build script in master job that will update the thresholds
in the gerrit job config.xml and reload.
2. Set dynamic thresholds with job parameters..but will not work if plugin
will not accept parameter variables as thresholds?

Does someone know other or better solutions to this?







--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Are-there-ways-to-set-different-reference-build-to-plugin-or-set-dynamic-thresholds-tp4879766.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1486587224954-4879766.post%40n4.nabble.com.
For more options, visit https://groups.google.com/d/optout.

Re: Define parameters for a group of jobs

[Richard Ginga]

correction, this needs to be run from a post-build groovy step because the
variable "manager" is predefined there

On Tue, Feb 14, 2017 at 8:56 AM, Richard Ginga 
wrote:

> here is a code snippet we run from a post-build groovy step (which you
> could use instead of the build groovy step)
>
> def globalProps = manager.hudson.getGlobalNodeProperties()
> def props = globalProps.getAll(hudson.slaves.
> EnvironmentVariablesNodeProperty.class)
>
> props[0].envVars.put( manager.envVars["YourVariableName, value])
>
>
> On Tue, Feb 14, 2017 at 8:35 AM, francesco desposito <
> francesco.desposito1...@gmail.com> wrote:
>
>> Thanks for your answers.
>> I'm going to try to use the system global variables as Richard suggested.
>>
>> Il giorno martedì 14 febbraio 2017 00:15:54 UTC+1, Richard Ginga ha
>> scritto:
>>>
>>> ok, I almost added "based on the information provided" so I may have
>>> misunderstood. #2 might still work unless you and he wanted to be able to
>>> run any of the jobs independently and provide unique parameter values at
>>> that time. if not, you would have to change each of your jobs to use a
>>> system global variable defined in the System Configuration and then one job
>>> to set them.
>>>
>>> On Mon, Feb 13, 2017 at 6:06 PM, David Karr 
>>> wrote:
>>>
 On Monday, February 13, 2017 at 8:11:27 AM UTC-8, Richard Ginga wrote:
>
> Francesco, there are actually many ways to do this.
>
> 1. use Pipeline script or System groovy build step or post build -
> "trigger parameterized  builds on other projects" to pass in parameter x
>
> 2. with system groovy script, you can create/update a global variable
> that all builds will see
>
> On Sat, Feb 11, 2017 at 5:43 AM, francesco desposito <
> francesco.d...@gmail.com> wrote:
>
>> Hello,
>> I want to group the jobs referring to a single project together.
>> Then I would like to define some parameters at group level and I want
>> that those parameters are automatically passed to the jobs belonging to
>> that group.
>> For example I want to create a group P1 with jobs a1, b1, c1. Then I
>> define a parameter x for P1. I would like that x is automatically defined
>> for the jobs a1, b1, c1.
>>
>> Is that possible?
>>
>> Thanks
>>
>
>
 I understood the OP's request, which I've often wanted myself, and I
 don't see how either of those strategies would do what he wants.  I think
 you misunderstood what he's asking.

 Let's say you have ten related jobs in a "project", all of which are
 parameterized, and all of which take a "Foo" parameter, a "Bar" parameter,
 and a "Something" parameter. He wants the ability to define in a single
 place that all of these jobs should expect the "Foo", "Bar", and
 "Something" parameters, instead of creating each one manually in each of
 the ten projects, copying the default value (if any) and description from
 the first one.

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/jenkinsci-users/c1f1b5f4-a24f-44f6-a93d-4562d5a56e53%40g
 ooglegroups.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Dick Ginga
>>> Build Engineer
>>> rgi...@disruptorbeam.com
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-users/61a19e90-75cb-4982-8145-7a428b02b634%
>> 40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com
>
>


-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaXob4cUpUJroYsiYMbbUDM3TNQ2fwahoZ71Wghbq%3Dv6zA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Define parameters for a group of jobs

[Richard Ginga]

here is a code snippet we run from a post-build groovy step (which you
could use instead of the build groovy step)

def globalProps = manager.hudson.getGlobalNodeProperties()
def props =
globalProps.getAll(hudson.slaves.EnvironmentVariablesNodeProperty.class)

props[0].envVars.put( manager.envVars["YourVariableName, value])


On Tue, Feb 14, 2017 at 8:35 AM, francesco desposito <
francesco.desposito1...@gmail.com> wrote:

> Thanks for your answers.
> I'm going to try to use the system global variables as Richard suggested.
>
> Il giorno martedì 14 febbraio 2017 00:15:54 UTC+1, Richard Ginga ha
> scritto:
>>
>> ok, I almost added "based on the information provided" so I may have
>> misunderstood. #2 might still work unless you and he wanted to be able to
>> run any of the jobs independently and provide unique parameter values at
>> that time. if not, you would have to change each of your jobs to use a
>> system global variable defined in the System Configuration and then one job
>> to set them.
>>
>> On Mon, Feb 13, 2017 at 6:06 PM, David Karr 
>> wrote:
>>
>>> On Monday, February 13, 2017 at 8:11:27 AM UTC-8, Richard Ginga wrote:

 Francesco, there are actually many ways to do this.

 1. use Pipeline script or System groovy build step or post build -
 "trigger parameterized  builds on other projects" to pass in parameter x

 2. with system groovy script, you can create/update a global variable
 that all builds will see

 On Sat, Feb 11, 2017 at 5:43 AM, francesco desposito <
 francesco.d...@gmail.com> wrote:

> Hello,
> I want to group the jobs referring to a single project together.
> Then I would like to define some parameters at group level and I want
> that those parameters are automatically passed to the jobs belonging to
> that group.
> For example I want to create a group P1 with jobs a1, b1, c1. Then I
> define a parameter x for P1. I would like that x is automatically defined
> for the jobs a1, b1, c1.
>
> Is that possible?
>
> Thanks
>


>>> I understood the OP's request, which I've often wanted myself, and I
>>> don't see how either of those strategies would do what he wants.  I think
>>> you misunderstood what he's asking.
>>>
>>> Let's say you have ten related jobs in a "project", all of which are
>>> parameterized, and all of which take a "Foo" parameter, a "Bar" parameter,
>>> and a "Something" parameter. He wants the ability to define in a single
>>> place that all of these jobs should expect the "Foo", "Bar", and
>>> "Something" parameters, instead of creating each one manually in each of
>>> the ten projects, copying the default value (if any) and description from
>>> the first one.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/c1f1b5f4-a24f-44f6-a93d-4562d5a56e53%
>>> 40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Dick Ginga
>> Build Engineer
>> rgi...@disruptorbeam.com
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/61a19e90-75cb-4982-8145-7a428b02b634%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaVbwgLMF%2B1D7u0rGOdNs86sR%2B5YJw-PJYnDSMZN7k6%3D8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Define parameters for a group of jobs

[francesco desposito]

Thanks for your answers.
I'm going to try to use the system global variables as Richard suggested.

Il giorno martedì 14 febbraio 2017 00:15:54 UTC+1, Richard Ginga ha scritto:
>
> ok, I almost added "based on the information provided" so I may have 
> misunderstood. #2 might still work unless you and he wanted to be able to 
> run any of the jobs independently and provide unique parameter values at 
> that time. if not, you would have to change each of your jobs to use a 
> system global variable defined in the System Configuration and then one job 
> to set them.
>
> On Mon, Feb 13, 2017 at 6:06 PM, David Karr  > wrote:
>
>> On Monday, February 13, 2017 at 8:11:27 AM UTC-8, Richard Ginga wrote:
>>>
>>> Francesco, there are actually many ways to do this.
>>>
>>> 1. use Pipeline script or System groovy build step or post build - 
>>> "trigger parameterized  builds on other projects" to pass in parameter x
>>>
>>> 2. with system groovy script, you can create/update a global variable 
>>> that all builds will see
>>>
>>> On Sat, Feb 11, 2017 at 5:43 AM, francesco desposito <
>>> francesco.d...@gmail.com> wrote:
>>>
 Hello,
 I want to group the jobs referring to a single project together. 
 Then I would like to define some parameters at group level and I want 
 that those parameters are automatically passed to the jobs belonging to 
 that group.
 For example I want to create a group P1 with jobs a1, b1, c1. Then I 
 define a parameter x for P1. I would like that x is automatically defined 
 for the jobs a1, b1, c1.

 Is that possible?

 Thanks 

>>>
>>>
>> I understood the OP's request, which I've often wanted myself, and I 
>> don't see how either of those strategies would do what he wants.  I think 
>> you misunderstood what he's asking.
>>
>> Let's say you have ten related jobs in a "project", all of which are 
>> parameterized, and all of which take a "Foo" parameter, a "Bar" parameter, 
>> and a "Something" parameter. He wants the ability to define in a single 
>> place that all of these jobs should expect the "Foo", "Bar", and 
>> "Something" parameters, instead of creating each one manually in each of 
>> the ten projects, copying the default value (if any) and description from 
>> the first one.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/c1f1b5f4-a24f-44f6-a93d-4562d5a56e53%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/61a19e90-75cb-4982-8145-7a428b02b634%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Conditional build parameter

['Maciej Jaros' via Jenkins Users]

Danny Wong (2017-02-14 07:33):


*Hi All,*

*Is there a way in Jenkins where if I have 2 radio buttons 
(yes/no) as a build parameter. if the user selects “yes”, then a 
dropdown will display and gets populated with data. If no, the 
dropdown disappears from the UI? Is there a way to implement this? 
Thanks!*




There is no built-in way to do that. But you can vote fore a feature 
request here:

https://issues.jenkins-ci.org/browse/JENKINS-19002

There is also a bit hacky script that allows to do what you are asking for:
https://github.com/Eccenux/jenkins-scripts/blob/master/theme/nux-js/parameter-grouping.js

Regards,
Nux.

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/97dd6589-995c-ff4c-f91b-157e368b5287%40mol.com.pl.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[Daniel Beck]

> On 14.02.2017, at 11:59, christian polzer  wrote:
> 
> Would it be possible to somehow track the version the documentation is 
> written for? :)

You can assume latest LTS or newer, with plugins up to date, as these are the 
only releases we consider to be supported. (I think rtyler has plans to improve 
this, but I doubt that'll be available soon.)

Running anything older is frequently a terrible idea anyway, see 
https://jenkins.io/security/advisories/

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5AC82BC4-928C-4ABD-9BFA-9D9B847EB0DF%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Ok, we have Jenkins LTS ver. 2.19.4 
installed with plugins updated just now.

And voila - it is working. 

Then now to another issue: Would it be possible to somehow track the 
version the documentation is written for? :)


On Tuesday, February 14, 2017 at 11:11:20 AM UTC+1, Daniel Beck wrote:
>
>
> > On 14.02.2017, at 10:22, christian polzer  > wrote: 
> > 
> > I just wondered if the pipeline example is pseudo code and if so - if it 
> has to? 
> > 
>
> You don't have the correct plugin installed: 
> https://plugins.jenkins.io/pipeline-model-definition 
>
> It should be automatically installed if you update plugins now, assuming 
> you have the default set from 2.0 onward installed. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/928af447-26af-4208-a776-fd2cc94758ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow-plugin] Setting poll to false doesn't alter the polling behavior

[Pavel Georgiev]

Hi,

Did you get any response? I see the same behavior - probably a bug? Did you 
log one?

On Monday, April 18, 2016 at 10:54:34 PM UTC+3, Kyle Allan wrote:
>
> Hello,
>
> I can't seem to understand my problem - setting poll: false in my 
> Pipeline DSL doesn't alter the behavior of the Git Poll Log like I expect. 
> I've ran the job multiple times, and I still see 2 polls within the logs 
> when I expect there to only be one.
>
> Workflow Job with an scm-polling trigger
> Pipeline from SCM configured to do a sparse checkout and ignore commits 
> from an automated user
> Pipeline DSL operates within a docker container, with changelog and poll 
> both set to false.
>
> Using strategy: Default
> [poll] Last Built Revision: Revision 57399c846b68250e81dff6f34feeb292664bdba5 
> (origin/master)
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repositories
>  > git config remote.origin.url g...@github.com/kallan357/thing.git # 
> timeout=10
> Fetching upstream changes from g...@github.com/kallan357/thing.git
>  > git --version # timeout=10
> using GIT_SSH to set credentials kallan357
>  > git fetch --tags --progress g...@github.com/kallan357/thing.git 
> +refs/heads/*:refs/remotes/origin/*
> Polling for changes in
>  > git rev-parse origin/master^{commit} # timeout=10
>  > git log --full-history --no-abbrev --format=raw -M -m --raw 
> 57399c846b68250e81dff6f34feeb292664bdba5..31621a03c0eb1d58be8e8b0d0eebed6bae6ccb23
>  # timeout=10
> Ignored commit 31621a03c0eb1d58be8e8b0d0eebed6bae6ccb23: Found excluded 
> author: jenkins-guy
> Using strategy: Default
> [poll] Last Built Revision: Revision 57399c846b68250e81dff6f34feeb292664bdba5 
> (origin/master)
> using GIT_SSH to set credentials kallan357
>  > git --version # timeout=10
>  > git ls-remote -h g...@github.com/kallan357/thing.git # timeout=10
> Found 45 remote heads on g...@github.com/kallan357/thing.git
> [poll] Latest remote head revision on refs/heads/master is: 
> 31621a03c0eb1d58be8e8b0d0eebed6bae6ccb23
> Done. Took 0.43 sec
> Changes found
>
>
> Here is my DSL that lives inside SCM alongside my project:
>
>
> node('java-docker-node') {
> timeout(15) {
> withEnv(envArray) {
> stage 'Checkout'
> git branch: 'master', credentialsId: 'abc123', changelog: false, 
> poll: false, url: 'g...@github.com/kallan357/thing.git'
>
> stage 'Build'
> sh '''
> mvn clean install
> '''
>
>
> stage 'Bump versions'
>
> sh '''./bump_version.sh'''
>
> }
>
> }
>
> }
>
>
> My bump_version script will bump my pom and commit a new version to SCM. 
> Because of the double sets of polling my job gets stuck in an infinite loop. 
>
>
> Am I missing something? I've executed my build, which I suspect should modify 
> the Jenkins polling behavior to only have a single attempt.
>
>
> Thanks,
>
> Kyle Allan
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a034197b-6095-45e3-bfa6-e84b8a00ecd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

[Daniel Beck]

> On 14.02.2017, at 09:11, Dan Tran  wrote:
> 
> all my Jenkins are losing  Pipeline Model Definition's settings after restart 
> ( ie after plugin grade)
> 

What 'settings' are you referring to? Are the jobs gone after restart?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5D309CDA-5A37-4DE8-9E3D-99777B9E902D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[Daniel Beck]

> On 14.02.2017, at 10:22, christian polzer  wrote:
> 
> I just wondered if the pipeline example is pseudo code and if so - if it has 
> to?
> 

You don't have the correct plugin installed:
https://plugins.jenkins.io/pipeline-model-definition

It should be automatically installed if you update plugins now, assuming you 
have the default set from 2.0 onward installed.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4267B60C-31F4-4F16-90EB-2EDC66B6E1A4%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Static Code Analysis & Compiler warnings build statistics

[Frederick]

Hi all,

Jenkins 2.45 & Ruby on Rails projects.

I'm trying to get the build history to show warnings so if there is a 
change for example in the number of Rubocop warnings, the devs can see the 
previous number of warnings, compared to the number of warnings fir latest 
commit.

I cannot seem to get the Static Code Analysis or Warnings plugins to work 
with Jenkins.

Can anybody share any pointers to documents that I can follow to set up 
these plugins to work and show the build statistics and their history of 
warnings and errors please?

TIA

Frederick

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/be740ac5-3136-4cd6-94dd-6c216e315d73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipline slow vs flow

[Baptiste Mathus]

It /might/ be the price of durability, since in Pipeline each steps is
serialized/checkpointed and sent from the master to somewhere to run on.
This enables it to restart in case of crash for instance, which build flow
can't do at all. And that price is probably more visible if each step
basically does nothing.

Also, you should be aware that Build Flow is deprecated de facto. His
creator abandoned it, and it gave many good feedbacks to design Pipeline.
And the last current maintainer I knew also abandoned it a few months ago.

2017-02-13 20:02 GMT+01:00 Chris Overend :

> I am not trying to say anything I just found it curious.
> We are doing testing to determine the optimal setup for Jenkins.
> We currently use flows calling flows.
> We believe we have too many builds in the build queue (3500).
>
> In the process of testing we saw this behavior and I was hoping for
> insight.
> We have seen the more builds we do the less efficient pipeline became.
> going from 1500 builds to 2000 builds the pipeline took twice as long.
>
> At 3500 builds
>
>- pipeline - 23 mins
>- flow - 8 min
>
> So how does this become negligible if the jobs are doing work?
> Does this overhead disappear?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-users/d3dfdfd4-e5df-48e4-9aec-a11552c7040f%
> 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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7YJJvBbiuGQzQ-2xdJ7p58JYEHT%3DVyBgLqwBe5CTYYfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Hi there, 

just a comment on your second question:

2) secondly, why Jenkins creates another  directory @tmp when I would like 
to execute a command from my workspace.

-> you are able to configure the executing jvm to use another tmp dir. 
Example : java -Djava.io.tmpdir=/path/to/tmpdir
(Especially handy if you are using RHEL7 or other oses which do not allow 
to execute stuff in /tmp)

On Tuesday, February 14, 2017 at 3:34:12 AM UTC+1, Sharan Basappa wrote:
>
> Tyler,
>
> I have a few questions for which I could not find answers after going 
> through the documentation.
> Unfortunately, understanding of these are necessary for anyone to create a 
> decent build jobs.
>
> 1) Jenkins seems to be executing from a directory named @tmp (and some 
> other names). The files I am referring are not available in @tmp directory 
> and hence
> the pipeline stage is exiting
> 2) secondly, why Jenkins creates another  directory @tmp when I would like 
> to execute a command from my workspace.
> All the references made by the script are available here.
> 3) I have also seen that sometimes the files from git are available but 
> .git itself is missing
>
> Can you comment?
>
> On Monday, 13 February 2017 19:31:37 UTC+5:30, R Tyler Croy wrote:
>
>> (replies inline) 
>>
>> On Mon, 13 Feb 2017, christian polzer wrote: 
>>
>> > Hello, 
>> > 
>> > I am currently trying to spread pipeline usage for a jenkins 
>> environment 
>> > within my fellow coworkers. 
>> > Of course, th jenkins pipeline is greatly embrased :) 
>> > 
>> > But what is the documentation in the jenkins book about? Fellow 
>> CoCoders 
>> > stumble over the jenkinsfile chapter as the examples are not working: 
>> > https://jenkins.io/doc/book/pipeline/ 
>> > 
>> > What documentation do you guys use? 
>>
>>
>> What examples are not working for you? I wrote almost all of them and I'm 
>> pretty sure every single one works, perhaps I made a typo. 
>>
>> Could you share the error you're seeing and the corresponding Jenkinsfile 
>> example? 
>>
>>
>> Cheers 
>> - R. Tyler Croy 
>>
>> -- 
>>  Code:  
>>   Chatter:  
>>  xmpp: rty...@jabber.org 
>>
>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
>> -- 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8de9e3e9-af40-42d6-9a45-0e335f99c374%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Hi, 
and thanks for the quick reply.
To be precice, I am getting questions about the "Jenkinsfile (Declarative 
Pipeline)" example. 

*For example : *

1.) No such DSL method 'pipeline'

*2.) "*agent any" is not working , and as far as I learned from other 
coverage, agents (= nodes? ) are addressed with this syntax:  

"node('[slave|node|agent] name here'){
}"   
**

When introducing jenkins pipelines,  I had setup loads of pipeline examples 
on our Jenkins. But as the common developer is behaving, 
they never get bored of digging into stuff, in a struggle to make things 
easier and try out different angles :-)

When they finally stumble upon the jenkins book section, this is the 
question I get from most of my colleagues:
"How is this example meant to be used, or is it referring to a version of 
pipeline which is either outdated or we dont have installed yet?"
-> It also is unclear to me, if that syntax would be working, since I never 
saw this in any other example when digging into pipeline. 

This results in parts of the team drawing conclusions how pipeline is not 
so precise at all and syntax save and blablablah, and oh well - the 
documentation...
and then they skip multibranch pipelines and setup 60 identically build 
jobs by hand (which I have to maintain and backup) :-/

Please excuse my partly bad english - and please understand that no harm is 
intended here. I am really amazed by the jenkins project and the 
documentation and all.
 
I just wondered if the pipeline example is pseudo code and if so - if it 
has to?

Thanks for the good work and kind regards,

chris












On Monday, February 13, 2017 at 3:01:37 PM UTC+1, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Mon, 13 Feb 2017, christian polzer wrote: 
>
> > Hello, 
> > 
> > I am currently trying to spread pipeline usage for a jenkins environment 
> > within my fellow coworkers. 
> > Of course, th jenkins pipeline is greatly embrased :) 
> > 
> > But what is the documentation in the jenkins book about? Fellow CoCoders 
> > stumble over the jenkinsfile chapter as the examples are not working: 
> > https://jenkins.io/doc/book/pipeline/ 
> > 
> > What documentation do you guys use? 
>
>
> What examples are not working for you? I wrote almost all of them and I'm 
> pretty sure every single one works, perhaps I made a typo. 
>
> Could you share the error you're seeing and the corresponding Jenkinsfile 
> example? 
>
>
> Cheers 
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>  xmpp: rty...@jabber.org  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
> -- 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/995a3fef-c3b0-4b90-93d5-55ffd6058f78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using pipeline shared library is failing with "I don't handle protocol 'git clone ssh'"

[Baptiste Mathus]

+Thanks Daniel, maybe…

Le 2 févr. 2017 11:18 PM, "David Karr"  a
écrit :

> On Thursday, February 2, 2017 at 9:15:57 AM UTC-8, David Karr wrote:
>>
>> In Jenkins 2.19.2, I now have three different pipeline jobs using a
>> variation of the same script components, including a bunch of methods that
>> I've pasted into each script.  I'm storing each script in git, but I think
>> it's now time to define a shared library so I can remove the duplicated
>> methods.
>>
>> So, I created a git repo with the "src", "vars", and "resources"
>> structure (initial test only has a single class in the "src" tree), and
>> referenced that repo from the shared library definition.
>>
>> I first noticed that something might be wrong when I entered "1.0" in the
>> "Default Version" field and it printed "Cannot validate default version"
>> below that.  When I clicked on "show details" it said something like this:
>> hudson.plugins.git.GitException: Command "/opt/app/git/1.9.0-0.14/bin/git
>> fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*"
>> returned status code 128:
>> stdout:
>> stderr: fatal: I don't handle protocol 'git clone ssh'
>>
>> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandI
>> n(CliGitAPIImpl.java:1745)
>>
>>
>> Even with this, I went ahead and tried adding the reference to the
>> library in one of my pipeline scripts, only to reference the single class I
>> put in the library (a simple enum definition).  In the build output, the
>> first reference to the repo containing the shared library looks like this:
>>
>> Setting origin to git clone ssh://git@.../usl_jenkins_library.git
>>  > /opt/app/git/1.9.0-0.14/bin/git config remote.origin.url git clone 
>> ssh://git@.../usl_jenkins_library.git # timeout=10
>> Fetching origin...
>> Fetching upstream changes from origin
>>  > /opt/app/git/1.9.0-0.14/bin/git --version # timeout=10
>> using GIT_ASKPASS to set credentials
>>  > /opt/app/git/1.9.0-0.14/bin/git fetch --tags --progress origin 
>> +refs/heads/*:refs/remotes/origin/*
>> hudson.plugins.git.GitException: Command "/opt/app/git/1.9.0-0.14/bin/git 
>> fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*" returned 
>> status code 128:
>> stdout:
>> stderr: fatal: I don't handle protocol 'git clone ssh'
>>
>> at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745)
>> at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489)
>>
>>
>> If it matters, I modified my pipeline script to look like this:
>> @Library("usl-pipeline-library")
>> import com.att.usl.jenkins.BUILD_STATUS
>>
>> import groovy.xml.*
>> import java.nio.file.*
>> import hudson.model.*
>> import hudson.triggers.*
>> import hudson.plugins.git.GitStatus
>>
>>
>> What might I be doing wrong here?
>>
>
> Hmm, well, this is was a head-slap error.  I didn't pay enough attention
> to what I pasted into the "repository" field.  I copied the entire "git
> clone" instruction instead of just the repository url.  Moving forward now.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/adae71ec-42d0-4b79-ae92-3b7bff880d64%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS62mv-yb8x%2By%2BBNtN63w-g%3DRnjqSY2BzbOTT-wRMEYgkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins -> Dockerfile -> Nexus Docker repository, how to do it?

[Arnoud Aarnoudse]

Yo! I am trying to get Jenkins to pull my git project, and build it into a 
docker image. After the docker image is made i want Jenkins to push it into 
my Nexus Docker repository. How can I do this? So far I have not found any 
working or complete guides.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/15907395-a5c4-4853-ba26-fc5705cd23e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Declarative Pipeline] Configure System -->Pipeline Model Definition reset after restart

[Dan Tran]

Hi,

all my Jenkins are losing  Pipeline Model Definition's settings after 
restart ( ie after plugin grade)

can someone confirm before I file a Jira?

Thanks

-Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fcecc816-b36f-4c6f-9f3f-edbb17fe593c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.