Counting the number of agents in a running pipeline

[Damien Coraboeuf]

Hi,

We have heavy duty pipelines running on multiple agents (40-50) in parallel 
and this number of agents is dynamic.

At the end of the pipeline, in a post/always section for example, I'd like 
to get the list of agents (or their number at least) having been used by 
this pipeline so that I can send it to some monitoring application.

I've started to play around with FlowNodeUtil, FlowNode, etc., but this 
looks awfully complex and I was wondering if a simpler solution was 
existing.

Thanks for any help,
Damien

-- 
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/c5325fea-e081-4fc6-ac8b-d417ad431ff1n%40googlegroups.com.

Re: Jenkins updates web site returns 404 errors when downloading plugins

[Damien Coraboeuf]

Problem identified and followed up at 
https://issues.jenkins-ci.org/browse/INFRA-2154

On Monday, 17 June 2019 11:33:10 UTC+2, Damien Coraboeuf wrote:
>
> Note that the issue can be reproduced very easily:
>
> curl -vL --output test.hpi https://
> updates.jenkins.io/download/plugins/workflow-durable-task-step-plugin/2.31/workflow-durable-task-step-plugin.hpi
>
> Sometimes it works, sometimes it does not.
>
> On Monday, 17 June 2019 10:07:06 UTC+2, Damien Coraboeuf wrote:
>>
>> Hi,
>>
>> This morning, we keep having 404 errors when downloading plugins from 
>> https://updates.jenkins.io, for example: 
>> https://updates.jenkins.io/download/plugins/pipeline-milestone-step/1.3.1/pipeline-milestone-step.hpi
>>  
>> (just an example, all kinds of plugins are impacted).
>>
>> We have this issue from our workstations or from our AWS EC2 instances 
>> (eu-west-1).
>>
>> Is that a known issue?
>>
>> Thanks,
>> Damien
>>
>

-- 
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/dbd4a10d-e152-489a-a478-76f7572e2b69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins updates web site returns 404 errors when downloading plugins

[Damien Coraboeuf]

Note that the issue can be reproduced very easily:

curl -vL --output test.hpi https:
//updates.jenkins.io/download/plugins/workflow-durable-task-step-plugin/2.31/workflow-durable-task-step-plugin.hpi

Sometimes it works, sometimes it does not.

On Monday, 17 June 2019 10:07:06 UTC+2, Damien Coraboeuf wrote:
>
> Hi,
>
> This morning, we keep having 404 errors when downloading plugins from 
> https://updates.jenkins.io, for example: 
> https://updates.jenkins.io/download/plugins/pipeline-milestone-step/1.3.1/pipeline-milestone-step.hpi
>  
> (just an example, all kinds of plugins are impacted).
>
> We have this issue from our workstations or from our AWS EC2 instances 
> (eu-west-1).
>
> Is that a known issue?
>
> Thanks,
> Damien
>

-- 
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/629b3aea-4aca-4fb1-ab2b-db1f89c37c99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins updates web site returns 404 errors when downloading plugins

[Damien Coraboeuf]

Hi,

This morning, we keep having 404 errors when downloading plugins from 
https://updates.jenkins.io, for example: 
https://updates.jenkins.io/download/plugins/pipeline-milestone-step/1.3.1/pipeline-milestone-step.hpi
 
(just an example, all kinds of plugins are impacted).

We have this issue from our workstations or from our AWS EC2 instances 
(eu-west-1).

Is that a known issue?

Thanks,
Damien

-- 
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/d55b690a-a014-4bb0-8b46-2e3f47f383c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Regression in `dir` step when wrapping other steps?

[Damien Coraboeuf]

It seems to have been solved by updating (again) all the plugins, esp. 
Groovy + Basic Steps. It seems we were in an intermediary situation.

On Wednesday, 5 June 2019 16:02:01 UTC+2, Devin Nusbaum wrote:
>
> Also, can you post the exact error message you are getting?
>
> On Jun 5, 2019, at 09:59, Devin Nusbaum  > wrote:
>
> I’m not aware of any intentional changes like this. What versions of 
> Pipeline Groovy and Pipeline Nodes and Processes are you currently running?
>
> On Jun 5, 2019, at 06:51, Damien Coraboeuf  > wrote:
>
> Hi,
>
> We're using Jenkins LTS 2.164.3 and Pipeline Basic Steps 2.16, and the 
> behaviour of the `dir` step has started to change, impacting most of our 
> pipelines.
>
> I could reproduce this on a small pipeline:
>
> node {
> stage("Test") {
> sh '''
> mkdir -p parent/child
> echo test > parent/child/file
> '''
> 
> dir('parent') {
>  withCredentials([
> usernamePassword(credentialsId: 
> 'docker-repository', usernameVariable: 'DOCKER_REPOSITORY_USR', 
> passwordVariable: 'DOCKER_REPOSITORY_PSW'),
> ]) {
> sh 'ls -l child'
> }
> }
> }
> }
>
> The last sh step would fail - the dir context is lost.
>
> If I put `dir` closer to its context, it works:
>
> node {
> stage("Test") {
> sh '''
> mkdir -p parent/child
> echo test > parent/child/file
> '''
> 
> withCredentials([
> usernamePassword(credentialsId: 
> 'docker-repository', usernameVariable: 'DOCKER_REPOSITORY_USR', 
> passwordVariable: 'DOCKER_REPOSITORY_PSW'),
> ]) {
> dir('parent') {
> sh 'ls -l child'
> }
> }
> }
> }
>
> Since this impacts many many pipelines, it is a big regression for us?
>
> Does anybody know if this is known regression? I could not find any post 
> nor ticket about this.
>
> Thanks,
> Damien
>
> -- 
> 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 jenkins...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/d57326a1-a342-4836-9d11-b3abf7e5ca4d%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/d57326a1-a342-4836-9d11-b3abf7e5ca4d%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/b12d3f68-5fed-41ec-afc7-758c516d1303%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Regression in `dir` step when wrapping other steps?

[Damien Coraboeuf]

Hi,

We're using Jenkins LTS 2.164.3 and Pipeline Basic Steps 2.16, and the 
behaviour of the `dir` step has started to change, impacting most of our 
pipelines.

I could reproduce this on a small pipeline:

node {
stage("Test") {
sh '''
mkdir -p parent/child
echo test > parent/child/file
'''

dir('parent') {
 withCredentials([
usernamePassword(credentialsId: 
'docker-repository', usernameVariable: 'DOCKER_REPOSITORY_USR', 
passwordVariable: 'DOCKER_REPOSITORY_PSW'),
]) {
sh 'ls -l child'
}
}
}
}

The last sh step would fail - the dir context is lost.

If I put `dir` closer to its context, it works:

node {
stage("Test") {
sh '''
mkdir -p parent/child
echo test > parent/child/file
'''

withCredentials([
usernamePassword(credentialsId: 
'docker-repository', usernameVariable: 'DOCKER_REPOSITORY_USR', 
passwordVariable: 'DOCKER_REPOSITORY_PSW'),
]) {
dir('parent') {
sh 'ls -l child'
}
}
}
}

Since this impacts many many pipelines, it is a big regression for us?

Does anybody know if this is known regression? I could not find any post 
nor ticket about this.

Thanks,
Damien

-- 
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/d57326a1-a342-4836-9d11-b3abf7e5ca4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Scan Repository Triggers project settings not taken into account by repositories

[Damien Coraboeuf]

Hi,

resolved (while writing the post).

One has to look at "Child Scan Triggers" at parent level - not at "Scan 
Organization Folder Triggers"

BR
Damien

On Wednesday, 15 May 2019 14:26:30 UTC+2, Damien Coraboeuf wrote:
>
> Hi,
>
> We're using Jenkins 2.164.3, with the latest version of all our plugins. 
> Everything is driven by SCM events (GitHub or Bitbucket server).
>
> We'd like very much to disable the "Branch indexing" - we've indeed done 
> it at project folder level, but this settings is not propagated at 
> repository level.
>
> Project level:
>
>
> Repository level:
>
>
> This is really a pain since this creates a surge of new builds every day, 
> for very little use.
>
> Thanks for any help,
> Damien
>

-- 
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/03a018b5-b75d-4c8e-b588-0852f02fde91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Scan Repository Triggers project settings not taken into account by repositories

[Damien Coraboeuf]

Hi,

We're using Jenkins 2.164.3, with the latest version of all our plugins. 
Everything is driven by SCM events (GitHub or Bitbucket server).

We'd like very much to disable the "Branch indexing" - we've indeed done it 
at project folder level, but this settings is not propagated at repository 
level.

Project level:


Repository level:


This is really a pain since this creates a surge of new builds every day, 
for very little use.

Thanks for any help,
Damien

-- 
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/5ddc9a3e-963d-4f62-858d-6f9c43f1c660%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: plugin to scan the Jenkins console log and determine the type of the failure

[damien . coraboeuf]

If you use MongoDB as backend for the storage of rules and failures (see 
plugin documentation), you can then have some graphs and stats. I don't 
know exactly what you're looking for, but it's very handy.

On Friday, September 28, 2018 at 3:36:14 PM UTC+2, pbasan...@gmail.com 
wrote:
>
> Thanks for you reply ..is there a way to count the Number of Jobs on each 
> category.
>
> On Thursday, September 27, 2018 at 4:48:09 PM UTC+5:30, Damien Coraboeuf 
> wrote:
>>
>> https://plugins.jenkins.io/build-failure-analyzer ?
>>
>> On Thu, Sep 27, 2018 at 12:10 PM  wrote:
>>
>>> Hi 
>>>
>>> Is there a plugin to scan the Jenkins console log and determine the type 
>>> of the failure (Infrastructure / Artifactory etc..)? and take action .. 
>>> instead of marking the build as failed /warning.
>>>
>>> Regards,
>>> Basanta
>>>
>>> -- 
>>> 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/2055fe5b-d379-489c-b511-82eb42873fc1%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/2055fe5b-d379-489c-b511-82eb42873fc1%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/c606f510-88c9-4861-80d2-3c5438a413e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: plugin to scan the Jenkins console log and determine the type of the failure

[Damien Coraboeuf]

https://plugins.jenkins.io/build-failure-analyzer ?

On Thu, Sep 27, 2018 at 12:10 PM  wrote:

> Hi
>
> Is there a plugin to scan the Jenkins console log and determine the type
> of the failure (Infrastructure / Artifactory etc..)? and take action ..
> instead of marking the build as failed /warning.
>
> Regards,
> Basanta
>
> --
> 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/2055fe5b-d379-489c-b511-82eb42873fc1%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/CAPD6afOc0ZeMCwyjguYQY9n_CD%3DuUJ3zXk9omGHx7GVf5H%3D_dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configuration as code and preservation of credentials

[Damien Coraboeuf]

Hi Nicolas,

Thanks for your feedback.

In our case, we're using CasC to maintain and push known and tested
versions of a Jenkins master into a production environment, but we wanted
to still accept some degree of freedom, esp. when it comes to credential
management.

An alternative is to use an external mgt system like Vault (I think it's
possible to use Vault as a backend for Jenkins credentials but this remains
to be tested).

Or I could drop the CasC file for the credentials, and do it using Groovy
init.d files, as I did in the (bad) old times :)

Best regards,
Damien Coraboeuf

On Tue, Sep 25, 2018 at 10:28 PM nicolas de loof 
wrote:

> A feature we'd like to investigate for JCasC is to make the web UI
> read-only once configured from yaml
> The specific sample of credentials could be adapted to support "preserve
> existing entries" but we have no way to support this in a generic way
> Also, JCasC is designed to support re-creating an equivalent jenkins
> master from scratch, so from this point of view this would make no sense.
>
> Le mar. 25 sept. 2018 à 22:07,  a écrit :
>
>> But many things are otherwise preserved. I feel the implementation of the
>> credentials configuration is doing a none vs. all approach, not taking into
>> account existing entries:
>>
>> In SystemCredentialsProviderConfigurator:
>>
>> target.setDomainCredentialsMap(DomainCredentials.asMap(value))
>>
>>
>> Maybe this code could be replaced to preserve existing entries.
>>
>>
>> On Tuesday, September 25, 2018 at 10:03:00 PM UTC+2,
>> damien.c...@collibra.com wrote:
>>>
>>> I've created the PR at
>>> https://github.com/jenkinsci/configuration-as-code-plugin/pull/556 to
>>> show an unit test reproducing the issue.
>>>
>>> On Tuesday, September 25, 2018 at 9:04:31 PM UTC+2,
>>> damien.c...@collibra.com wrote:
>>>>
>>>> Hi,
>>>>
>>>> We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code
>>>> is a list of credentials (some SSH keys, some user/passwords, etc.) common
>>>> to all our instances but we let also the administrators of a Jenkins
>>>> instance define their own credential entries.
>>>>
>>>> However, when the Jenkins instance is restarted, only the credential
>>>> entries defined by the CasC files are kept, and all the ones which were
>>>> added manually are lost.
>>>>
>>>> Is there a way to prevent this?
>>>>
>>>> Thanks,
>>>> Damien Coraboeuf
>>>>
>>> --
>> 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/fb5e1d2b-4df3-4950-902d-5f18490b2ea5%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/fb5e1d2b-4df3-4950-902d-5f18490b2ea5%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Nicolas De Loof
>
> --
> 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/CANMVJzn_LpJBVQbjHKGLmF51oAsyWW7E%2BNxng9sB-KCHKtb%2BWQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzn_LpJBVQbjHKGLmF51oAsyWW7E%2BNxng9sB-KCHKtb%2BWQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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/CAPD6afPKoZun3Bu0JHQyQuQKTNU9cvjyUiy%2B_N2Ah2t0C42L7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configuration as code and preservation of credentials

[damien . coraboeuf]

But many things are otherwise preserved. I feel the implementation of the 
credentials configuration is doing a none vs. all approach, not taking into 
account existing entries:

In SystemCredentialsProviderConfigurator:

target.setDomainCredentialsMap(DomainCredentials.asMap(value))


Maybe this code could be replaced to preserve existing entries.


On Tuesday, September 25, 2018 at 10:03:00 PM UTC+2, 
damien.c...@collibra.com wrote:
>
> I've created the PR at 
> https://github.com/jenkinsci/configuration-as-code-plugin/pull/556 to 
> show an unit test reproducing the issue.
>
> On Tuesday, September 25, 2018 at 9:04:31 PM UTC+2, 
> damien.c...@collibra.com wrote:
>>
>> Hi,
>>
>> We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is 
>> a list of credentials (some SSH keys, some user/passwords, etc.) common to 
>> all our instances but we let also the administrators of a Jenkins instance 
>> define their own credential entries.
>>
>> However, when the Jenkins instance is restarted, only the credential 
>> entries defined by the CasC files are kept, and all the ones which were 
>> added manually are lost.
>>
>> Is there a way to prevent this?
>>
>> Thanks,
>> Damien Coraboeuf
>>
>

-- 
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/fb5e1d2b-4df3-4950-902d-5f18490b2ea5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configuration as code and preservation of credentials

[damien . coraboeuf]

I've created the PR at 
https://github.com/jenkinsci/configuration-as-code-plugin/pull/556 to show 
an unit test reproducing the issue.

On Tuesday, September 25, 2018 at 9:04:31 PM UTC+2, 
damien.c...@collibra.com wrote:
>
> Hi,
>
> We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is a 
> list of credentials (some SSH keys, some user/passwords, etc.) common to 
> all our instances but we let also the administrators of a Jenkins instance 
> define their own credential entries.
>
> However, when the Jenkins instance is restarted, only the credential 
> entries defined by the CasC files are kept, and all the ones which were 
> added manually are lost.
>
> Is there a way to prevent this?
>
> Thanks,
> Damien Coraboeuf
>

-- 
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/0ac89ce5-a270-43f9-a791-0f2041bf261d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Configuration as code and preservation of credentials

[damien . coraboeuf]

Hi,

We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is a 
list of credentials (some SSH keys, some user/passwords, etc.) common to 
all our instances but we let also the administrators of a Jenkins instance 
define their own credential entries.

However, when the Jenkins instance is restarted, only the credential 
entries defined by the CasC files are kept, and all the ones which were 
added manually are lost.

Is there a way to prevent this?

Thanks,
Damien Coraboeuf

-- 
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/2ab722d3-c851-4764-89a3-733d6cbb5391%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean link from a legacy build page shows 404 error

[damien . coraboeuf]

I've followed instructions 
at https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache 
and in particular, I've set the following options:

  ProxyPass/ http://jenkins:8080/ Keepalive=On retry=1 
timeout=6 nocanon
  ProxyPassReverse / http://jenkins:8080/ Keepalive=On
  ProxyRequests Off
  AllowEncodedSlashes On

Nocanon, ProxyRequests off and AllowEncodedSlashes On

Now, my Blue Ocean URLs are working fine.

Thanks,
Damien

On Thursday, September 6, 2018 at 9:02:49 AM UTC+2, 
damien.c...@collibra.com wrote:
>
> I could not reproduce the issue when running with the same setup locally 
> (we're defining the complete setup as code, so it's easy to reproduce 
> locally). So I fear this has to do with some proxy settings. But on the 
> proxy logs, nothing.
>
> On Thursday, September 6, 2018 at 8:29:13 AM UTC+2, George Cimpoies wrote:
>>
>> Tried to replicate the scenario but couldn't reproduce your issue, in my 
>> case it just opens the appropriate blue ocean section of the pipeline job. 
>> Using  Jenkins ver. 2.130 .
>>
>> On Wed, Sep 5, 2018 at 9:02 PM  wrote:
>>
>>> Hi,
>>>
>>> In version of Jenkins 2.121.3, with Blue Ocean 1.8.2, I have the 
>>> following behaviour:
>>>
>>> * from the Blue Ocean dashboard, I can navigate to a pipeline page
>>> * now using the legacy UI, I navigate to the same pipeline page, and 
>>> then click on the "Open Blue Ocean" link - I get a 404 exception
>>>
>>> The two links seem the same:
>>>
>>> * 
>>> https://jenkins/blue/organizations/jenkins/CPROD%2Fproject/detail/master/29/pipeline
>>>  
>>> --> OK
>>> * 
>>> https://jenkins/blue/organizations/jenkins/CPROD%2Fproject/detail/master/29 
>>> --> 404
>>>
>>> So the second URL misses "/pipeline" at the end. Fine. If I add it, it 
>>> fails the same way, with 404.
>>>
>>> Even weirder, if I refresh the first page (the one I got to from the 
>>> Blue Ocean dashboard), I get also a 404 error.
>>>
>>> I do not have any stack trace in the server logs.
>>>
>>> I did not see any existing error about this.
>>>
>>> Any help would be welcome.
>>>
>>> Thanks,
>>> Damien
>>>
>>> -- 
>>> 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/eb6ce27d-f643-4f64-88e9-ebb5a06f7350%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> -- 
>> George Cimpoies
>> R • Itiviti
>> Software Engineer
>>
>> Mobile: +40 751 048 489
>> george@ullink.com
>>
>> 1 Victor Deleu Street | Cluj-Napoca, Cluj 400112
>>
>>
>> Visit: itiviti.com  / ullink.com 
>>  »
>> Read the latest news from Itiviti » 
>>
>> *The information contained in or attached to this email is strictly 
>> confidential. If you are not the intended recipient, please notify us 
>> immediately by telephone and return the message to us.*
>>
>>
>> *Email communications by definition contain personal information. The 
>> ITIVITI group of companies (of which ULLINK forms part) is subject to 
>> European data protection regulations. ULLINK’s Privacy Policy is available 
>> at www.ullink.com . ULLINK expects the recipient of 
>> this email to be compliant with ULLINK’s Privacy Policy and applicable 
>> regulations. Please advise us immediately at datapro...@ullink.com if you 
>> are not compliant with these.*
>>
>

-- 
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/90af0c36-e189-4cf4-8096-ae95144a1391%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean link from a legacy build page shows 404 error

[damien . coraboeuf]

I could not reproduce the issue when running with the same setup locally 
(we're defining the complete setup as code, so it's easy to reproduce 
locally). So I fear this has to do with some proxy settings. But on the 
proxy logs, nothing.

On Thursday, September 6, 2018 at 8:29:13 AM UTC+2, George Cimpoies wrote:
>
> Tried to replicate the scenario but couldn't reproduce your issue, in my 
> case it just opens the appropriate blue ocean section of the pipeline job. 
> Using  Jenkins ver. 2.130 .
>
> On Wed, Sep 5, 2018 at 9:02 PM > 
> wrote:
>
>> Hi,
>>
>> In version of Jenkins 2.121.3, with Blue Ocean 1.8.2, I have the 
>> following behaviour:
>>
>> * from the Blue Ocean dashboard, I can navigate to a pipeline page
>> * now using the legacy UI, I navigate to the same pipeline page, and then 
>> click on the "Open Blue Ocean" link - I get a 404 exception
>>
>> The two links seem the same:
>>
>> * 
>> https://jenkins/blue/organizations/jenkins/CPROD%2Fproject/detail/master/29/pipeline
>>  
>> --> OK
>> * 
>> https://jenkins/blue/organizations/jenkins/CPROD%2Fproject/detail/master/29 
>> --> 404
>>
>> So the second URL misses "/pipeline" at the end. Fine. If I add it, it 
>> fails the same way, with 404.
>>
>> Even weirder, if I refresh the first page (the one I got to from the Blue 
>> Ocean dashboard), I get also a 404 error.
>>
>> I do not have any stack trace in the server logs.
>>
>> I did not see any existing error about this.
>>
>> Any help would be welcome.
>>
>> Thanks,
>> Damien
>>
>> -- 
>> 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/eb6ce27d-f643-4f64-88e9-ebb5a06f7350%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> George Cimpoies
> R • Itiviti
> Software Engineer
>
> Mobile: +40 751 048 489
> george@ullink.com 
>
> 1 Victor Deleu Street | Cluj-Napoca, Cluj 400112
>
>
> Visit: itiviti.com  / ullink.com 
>  »
> Read the latest news from Itiviti » 
>
> *The information contained in or attached to this email is strictly 
> confidential. If you are not the intended recipient, please notify us 
> immediately by telephone and return the message to us.*
>
>
> *Email communications by definition contain personal information. The 
> ITIVITI group of companies (of which ULLINK forms part) is subject to 
> European data protection regulations. ULLINK’s Privacy Policy is available 
> at www.ullink.com . ULLINK expects the recipient of 
> this email to be compliant with ULLINK’s Privacy Policy and applicable 
> regulations. Please advise us immediately at datapro...@ullink.com 
>  if you are not compliant with these.*
>

-- 
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/5eef4075-dd0e-4611-b3df-e1a5ff30d366%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Blue Ocean link from a legacy build page shows 404 error

[damien . coraboeuf]

Hi,

In version of Jenkins 2.121.3, with Blue Ocean 1.8.2, I have the following 
behaviour:

* from the Blue Ocean dashboard, I can navigate to a pipeline page
* now using the legacy UI, I navigate to the same pipeline page, and then 
click on the "Open Blue Ocean" link - I get a 404 exception

The two links seem the same:

* 
https://jenkins/blue/organizations/jenkins/CPROD%2Fproject/detail/master/29/pipeline
 
--> OK
* https://jenkins/blue/organizations/jenkins/CPROD%2Fproject/detail/master/29 
--> 404

So the second URL misses "/pipeline" at the end. Fine. If I add it, it 
fails the same way, with 404.

Even weirder, if I refresh the first page (the one I got to from the Blue 
Ocean dashboard), I get also a 404 error.

I do not have any stack trace in the server logs.

I did not see any existing error about this.

Any help would be welcome.

Thanks,
Damien

-- 
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/eb6ce27d-f643-4f64-88e9-ebb5a06f7350%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin disappeared from http://updates.jenkins-ci.org/download/plugins/

[Damien Coraboeuf]

Actually, it has even disappeared from the list of plugins 
at https://plugins.jenkins.io/ ...

It was still there on February 2nd...

On Monday, May 22, 2017 at 7:13:23 PM UTC+2, Damien Coraboeuf wrote:
>
> Hi,
>
> I've published a new version of the Ontrack plug-in and it is available in 
> the Maven repo at 
> http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ontrack/2.30.1/, 
> but the plug-in group has mysteriously disappeared from 
> http://updates.jenkins-ci.org/download/plugins/ ...
>
> This is of course blocking since it prevents the plugin to be downloaded :(
>
> Anything I'm missing here?
>
> Thanks,
> Damien.
>

-- 
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/1882b2f5-8d85-4866-92f6-0b8889dfdbde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugin disappeared from http://updates.jenkins-ci.org/download/plugins/

[Damien Coraboeuf]

Hi,

I've published a new version of the Ontrack plug-in and it is available in 
the Maven repo 
at http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ontrack/2.30.1/, 
but the plug-in group has mysteriously disappeared 
from http://updates.jenkins-ci.org/download/plugins/ ...

This is of course blocking since it prevents the plugin to be downloaded :(

Anything I'm missing here?

Thanks,
Damien.

-- 
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/0dd85e96-8e73-4c85-9dc0-84ea1da10153%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins LTS and Docker 1.13

[Damien Coraboeuf]

Hi,

We deploy Jenkins 2.32.2 on a single Docker host, version 1.13.1, with a 
volume mapped on the host. No swarm here.

And we also use Docker from the builds themselves, on slaves, but using 
only native accesses (no Jenkins plugin, or only Gradle/Maven plugins).

On Sunday, 19 February 2017 14:23:26 UTC+1, rene@wescale.fr wrote:
>
>
> Hello Damien,
>
>   So apparently you have been using Jenkins LTS 2.32.2 with Docker 1.13.1, 
> please can you advise or share on your setup, regarding the name and the 
> version of the docker plugin you are using ?  more specificaly do you use 
> docker 1.13 feature like swarm mode or  docker service in compose file ? 
> what generaly the setup ? 
>
>
> Le samedi 18 février 2017 18:49:44 UTC+1, Damien Coraboeuf a écrit :
>>
>> I've used Jenkins LTS 2.32.2 with Docker 1.13.1 without any issue. What 
>> is exactly your issue?
>>
>> On Friday, 17 February 2017 08:55:01 UTC+1, Baptiste Mathus wrote:
>>>
>>>
>>>
>>> Le 9 févr. 2017 4:38 PM, "Omeka" <exup...@gmail.com> a écrit :
>>>
>>> Previously the current LTS of jenkins would not work with docker 1.12 
>>> because of this issue 
>>> https://github.com/maxfields2000/dockerjenkins_tutorial/issues/20
>>> Has anyway here tested jenkins LTS with the Docker 1.13? 
>>>
>>> Is there a way to get around the issue with another docker plugin?
>>>
>>>
>>> Can help if you start giving the plugins and LTS version you're 
>>> referring to.
>>>
>>>
>>> On my setup we would to experiment with docker swarm mode which is a 
>>> 1.12+ feature.
>>>
>>> -- 
>>> 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/dda0da4c-04f5-4042-9f14-92494e23ef3f%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/dda0da4c-04f5-4042-9f14-92494e23ef3f%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/66fae4fe-23df-471f-99bf-3617e16d0cb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disabling shallow clone using the GitHub organisation

[Damien Coraboeuf]

Small precision: better using "git checkout -B ${BRANCH_NAME}" in case the 
workspace is not discarded

On Saturday, 18 February 2017 19:26:58 UTC+1, Damien Coraboeuf wrote:
>
> Using "git checkout -b ${BRANCH_NAME}" as a first shell step before the 
> actual build is a very elegant trick.
>
> Thanks Mark!
> Best regards,
> Damien.
>
> On Saturday, 18 February 2017 19:14:12 UTC+1, Mark Waite wrote:
>>
>> The git plugin defaults to performing a checkout with a detached head at 
>> the SHA1 hash to be built.  There is a plugin option "LocalBranch" which 
>> can assign the name of the local branch to be created at that SHA1.  If 
>> that's not available from the declarative pipeline, you may be able to 
>> perform a "git checkout -b branch_name" in your build step.
>>
>> Mark Waite
>>
>> On Sat, Feb 18, 2017 at 11:10 AM Damien Coraboeuf <damien.c...@gmail.com> 
>> wrote:
>>
>>> Hi Mark,
>>>
>>> I'm also using the Pipeline Model Definition plug-in, and I think this 
>>> is the culprit in this story. Using the model definition, I do not see any 
>>> way to specify the "checkout scm" (as I would do in a "regular" pipeline 
>>> definition).
>>>
>>> I'm using a versioning Gradle plugin and its output shows that we are 
>>> using either a shallow clone or a detached head. I need the target branch 
>>> to be checked out as a local branch.
>>>
>>> Best regards,
>>> Damien.
>>>
>>>
>>> On Sat, Feb 18, 2017 at 7:06 PM, Mark Waite <mark.ea...@gmail.com> 
>>> wrote:
>>>
>>>> What are you observing that makes you think that shallow clone is 
>>>> always enabled?
>>>>
>>>> The git plugin and all my work with GitHub Organization Folders 
>>>> indicates that shallow clone is disabled by default for all git plugin 
>>>> usage, including GitHub Organization Folders.
>>>>
>>>> I run a GitHub Organization Folder configuration for Jenkins git plugin 
>>>> and Jenkins git client plugin development changes from my forks at 
>>>> https://github.com/MarkEWaite/git-client-plugin.  If I clone that 
>>>> repository with a shallow clone, there are unit tests which fail because 
>>>> the tests rely on a full local history of the repository.
>>>>
>>>> Are you performing a "checkout scm" (or similar) in your Jenkinsfile so 
>>>> that each job has its own working copy of the repository?  If so, are you 
>>>> enabling shallow clone in that checkout?  If not, then you need to change 
>>>> to use "checkout scm" in each Jenkinsfile.
>>>>
>>>> Mark Waite
>>>>
>>>> On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf <
>>>> damien.c...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> In order to compute versions correctly (using 
>>>>> https://github.com/nemerosa/versioning), I need my projects not to be 
>>>>> checked out using a shallow clone option.
>>>>>
>>>>> The Organization plug-in (
>>>>> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin)
>>>>>  
>>>>> does not seem to allow to disable this option. Or is it something we can 
>>>>> change using the Pipeline Model Definition plug-in syntax?
>>>>>
>>>>> Thanks,
>>>>> Damien.
>>>>>
>>>>> -- 
>>>>> 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/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> -- 
>>>> You received this message because you are subscribed to a topic in the 
>>>> Google Groups "Jenkins Users" group.
>>>> To unsubscribe from this topic, vis

Re: Disabling shallow clone using the GitHub organisation

[Damien Coraboeuf]

Using "git checkout -b ${BRANCH_NAME}" as a first shell step before the 
actual build is a very elegant trick.

Thanks Mark!
Best regards,
Damien.

On Saturday, 18 February 2017 19:14:12 UTC+1, Mark Waite wrote:
>
> The git plugin defaults to performing a checkout with a detached head at 
> the SHA1 hash to be built.  There is a plugin option "LocalBranch" which 
> can assign the name of the local branch to be created at that SHA1.  If 
> that's not available from the declarative pipeline, you may be able to 
> perform a "git checkout -b branch_name" in your build step.
>
> Mark Waite
>
> On Sat, Feb 18, 2017 at 11:10 AM Damien Coraboeuf <damien.c...@gmail.com 
> > wrote:
>
>> Hi Mark,
>>
>> I'm also using the Pipeline Model Definition plug-in, and I think this is 
>> the culprit in this story. Using the model definition, I do not see any way 
>> to specify the "checkout scm" (as I would do in a "regular" pipeline 
>> definition).
>>
>> I'm using a versioning Gradle plugin and its output shows that we are 
>> using either a shallow clone or a detached head. I need the target branch 
>> to be checked out as a local branch.
>>
>> Best regards,
>> Damien.
>>
>>
>> On Sat, Feb 18, 2017 at 7:06 PM, Mark Waite <mark.ea...@gmail.com 
>> > wrote:
>>
>>> What are you observing that makes you think that shallow clone is always 
>>> enabled?
>>>
>>> The git plugin and all my work with GitHub Organization Folders 
>>> indicates that shallow clone is disabled by default for all git plugin 
>>> usage, including GitHub Organization Folders.
>>>
>>> I run a GitHub Organization Folder configuration for Jenkins git plugin 
>>> and Jenkins git client plugin development changes from my forks at 
>>> https://github.com/MarkEWaite/git-client-plugin.  If I clone that 
>>> repository with a shallow clone, there are unit tests which fail because 
>>> the tests rely on a full local history of the repository.
>>>
>>> Are you performing a "checkout scm" (or similar) in your Jenkinsfile so 
>>> that each job has its own working copy of the repository?  If so, are you 
>>> enabling shallow clone in that checkout?  If not, then you need to change 
>>> to use "checkout scm" in each Jenkinsfile.
>>>
>>> Mark Waite
>>>
>>> On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf <damien.c...@gmail.com 
>>> > wrote:
>>>
>>>> Hi,
>>>>
>>>> In order to compute versions correctly (using 
>>>> https://github.com/nemerosa/versioning), I need my projects not to be 
>>>> checked out using a shallow clone option.
>>>>
>>>> The Organization plug-in (
>>>> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin)
>>>>  
>>>> does not seem to allow to disable this option. Or is it something we can 
>>>> change using the Pipeline Model Definition plug-in syntax?
>>>>
>>>> Thanks,
>>>> Damien.
>>>>
>>>> -- 
>>>> 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/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-users/TIK6DERVZqQ/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-use...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmrWTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmrWTrnK7J7OfjAk9fPcM

Re: Disabling shallow clone using the GitHub organisation

[Damien Coraboeuf]

Hi Mark,

I'm also using the Pipeline Model Definition plug-in, and I think this is
the culprit in this story. Using the model definition, I do not see any way
to specify the "checkout scm" (as I would do in a "regular" pipeline
definition).

I'm using a versioning Gradle plugin and its output shows that we are using
either a shallow clone or a detached head. I need the target branch to be
checked out as a local branch.

Best regards,
Damien.


On Sat, Feb 18, 2017 at 7:06 PM, Mark Waite <mark.earl.wa...@gmail.com>
wrote:

> What are you observing that makes you think that shallow clone is always
> enabled?
>
> The git plugin and all my work with GitHub Organization Folders indicates
> that shallow clone is disabled by default for all git plugin usage,
> including GitHub Organization Folders.
>
> I run a GitHub Organization Folder configuration for Jenkins git plugin
> and Jenkins git client plugin development changes from my forks at
> https://github.com/MarkEWaite/git-client-plugin.  If I clone that
> repository with a shallow clone, there are unit tests which fail because
> the tests rely on a full local history of the repository.
>
> Are you performing a "checkout scm" (or similar) in your Jenkinsfile so
> that each job has its own working copy of the repository?  If so, are you
> enabling shallow clone in that checkout?  If not, then you need to change
> to use "checkout scm" in each Jenkinsfile.
>
> Mark Waite
>
> On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf <
> damien.corabo...@gmail.com> wrote:
>
>> Hi,
>>
>> In order to compute versions correctly (using https://github.com/
>> nemerosa/versioning), I need my projects not to be checked out using a
>> shallow clone option.
>>
>> The Organization plug-in (https://wiki.jenkins-ci.org/
>> display/JENKINS/GitHub+Organization+Folder+Plugin) does not seem to
>> allow to disable this option. Or is it something we can change using the
>> Pipeline Model Definition plug-in syntax?
>>
>> Thanks,
>> Damien.
>>
>> --
>> 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/69ac8ef3-010a-4a6f-8874-
>> 10a4b632dd6d%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/TIK6DERVZqQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAO49JtF7Hd1XVatjf5q4caTV6KLmr
> WTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmrWTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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/CAMbUmAEfvgh-nG-Ss49k6Nf69D0f%2Bgbk%2B9UJPyYYe8GY5hMhkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins configuration from script

[Damien Coraboeuf]

At my client (big scale), the Jenkins master is provisioned using Groovy 
script files in the /var/lib/jenkins/init.groovy.d directory. Any script in 
this directory is run at Jenkins startup.

It is then just a matter of calling the Jenkins Java API to provision 
everything you need (credentials, tools, plugin configurations, etc.). 
That's some work to do, but on the other hand, it is only code and you can 
test it automatically before going in production.

On Friday, 17 February 2017 00:44:03 UTC+1, Andrew Hammond wrote:
>
> I'm doing something similar. My current "solution" is as follows:
>
> 1) Jenkins master is run in a docker container. The dockerfile includes a 
>
> RUN /usr/local/bin/install-plugins.sh your plugins listed here
>
> Currently I have only the following plugins:
> blueocean (I know it's beta, but it make jenkins actually usable, so...)
> digitalocean-plugin (master is in DO, and build agents are spun up there 
> on demand)
> docker-build-step (we want to create docker images and push them to 
> dockerhub...)
> github-oauth (we have an organization on gh: use that to determine who 
> people are)
> github-branch-source (automatically scan repos in that organization and 
> detect Jenkinsfiles)
>
> 2) Absolutely minimal configuration in the Jenkins master. That means all 
> builds are driven by the Jenkinsfile in the repo with the code.
>
> I'm trying to get scm-sync-configuration plugin working now, but I'm 
> realizing that maybe it's not even worth trying. I think I'll just go with 
> snapshotting the filesystem.
>
> A
>
>
> On Thursday, November 3, 2016 at 3:42:29 AM UTC-7, Tomasz Szandała wrote:
>>
>> Greetings All,
>> I am working on new Jenkins usage model for my Team.
>> My idea is to:
>> 1. Create new cloud instance
>> 2. Configure it and install Jenkins using Ansible
>> 3. Configure Jenkins using some kind of script
>> 4. Create and configure few projcts - I have them in DSL scripts 
>> currently.
>>
>> My problem is point nr 3.:
>> I need to:
>> a. Configure LDAP
>> b. Add nodes
>> c. Install needed plugins.
>>
>> So far I've found script to add nodes, but don't know how to use it from 
>> command line...
>>
>> Anyone knows where to look for guides about my problem?
>>
>> Thank You in advance,
>> Tomek
>>
>

-- 
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/afa96bee-0eb0-4f61-a25d-4e411a3cdd80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins LTS and Docker 1.13

[Damien Coraboeuf]

I've used Jenkins LTS 2.32.2 with Docker 1.13.1 without any issue. What is 
exactly your issue?

On Friday, 17 February 2017 08:55:01 UTC+1, Baptiste Mathus wrote:
>
>
>
> Le 9 févr. 2017 4:38 PM, "Omeka"  a 
> écrit :
>
> Previously the current LTS of jenkins would not work with docker 1.12 
> because of this issue 
> https://github.com/maxfields2000/dockerjenkins_tutorial/issues/20
> Has anyway here tested jenkins LTS with the Docker 1.13? 
>
> Is there a way to get around the issue with another docker plugin?
>
>
> Can help if you start giving the plugins and LTS version you're referring 
> to.
>
>
> On my setup we would to experiment with docker swarm mode which is a 1.12+ 
> feature.
>
> -- 
> 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/dda0da4c-04f5-4042-9f14-92494e23ef3f%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/fc6a8f40-6857-4975-a708-0b6277c1490b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build project inside docker

[Damien Coraboeuf]

The `cd` in the first shell step will change the directory only in the 
first shell step.

You should group shell steps together:

sh '''\

cd usr/local/src/freeswitch-1.4.26

./rebootstrap

./configure
make

'''

Additionally, should not you use cd /usr/local/src/freeswitch-1.4.26 and 
not cd usr/local/src/freeswitch-1.4.26?

Best regards,
Damien.

On Saturday, 18 February 2017 11:26:17 UTC+1, Ruchir Brahmbhatt wrote:
>
> Hi,
>
> I'm trying to build a project inside docker container so that all 
> dependencies required for project are available and doesn't require 
> installation in jenkins system. Below is my Jenkinsfile.
>
> node{stage ('Build'){ checkout scm 
> docker.image('bettervoice/freeswitch-container:1.6.9').inside {
> sh 'cd usr/local/src/freeswitch-1.4.26'
>
> sh './rebootstrap'
>
> sh './configure' sh 'make' } } }
>
>
> But I get error as below.
>
> [st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A]
>  Running shell script
> + usr/local/src/freeswitch-1.4.26/rebootstrap
> /var/lib/jenkins/workspace/st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A@tmp/durable-776c465c/script.sh:
>  2: 
> /var/lib/jenkins/workspace/st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A@tmp/durable-776c465c/script.sh:
>  usr/local/src/freeswitch-1.4.26/rebootstrap: not found
>
>
> Any hints on what is wrong with the file?
>
>

-- 
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/732ba5c5-41d2-41e5-ba15-451d44d998e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: declarative pipeline - gradle build tool not working

[Damien Coraboeuf]

Question: why can't you use the Gradle wrapper? This allows you to rely 
only on a JDK. No need to rely on a Gradle installation.

On Thursday, 16 February 2017 09:34:34 UTC+1, Bill Dennis wrote:
>
> Yes, I did all that gradle configuration. 'GRADLE_LATEST' is the label we 
> used for our gradle installation. We name it that way so every time we 
> update to the latest gradle, we don't need to change all our jobs that we 
> want to be on the latest gradle version. We also use gradle version 
> specific labels for jobs that are sensitive to the version. It shouldn't be 
> a problem here. 
>
> Thanks, 
> Bill 
>

-- 
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/61a1fecb-e16c-4e89-9bc5-f27f16e4d8a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Using agent dockerfile AND label in a declarative pipeline

[Damien Coraboeuf]

Hi,

I'm starting to migrate some projects to the declarative pipeline model. In 
particular, we want to build on an agent designated by the "docker" label 
(which runs a Docker daemon) and then, I want to build inside a Docker 
container described by my Dockerfile.

Doing this:

pipeline {
   agent {
 label "docker"
 dockerfile true
   }
}

This generates an error:

Only one agent type is allowed per agent section


Now, what should be the best approach to solve this, I think, common 
pattern?

I will try using agent+label, and then using docker+build+inside in steps, 
but would not it more elegant to allow to use both a label and a Dockerfile 
in the agent declaration?

Thanks you for any feedback,
Damien.

-- 
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/c3f4d258-9b63-4744-9b50-47da546bcdb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker in Docker in Jenkins Pipeline - how to access the Docker host?

[Damien Coraboeuf]

I finally answered my own question and documented 
here: https://nemerosa.ghost.io/2016/09/27/docker-in-docker-in-jenkins-pipeline/

I hope it helps other people.

Best regards,
Damien.

On Monday, 26 September 2016 21:27:00 UTC+2, Damien Coraboeuf wrote:
>
> Hi,
>
> After having struggled, I decided to create a simplified version of a 
> pipeline, which highlights the issue.
>
> Environment: Linux, Jenkins 2.23, latest versions of the pipeline 
> components.
>
> Given the pipeline definition at 
> https://github.com/nemerosa/jenkins-docker:
>
>1. I build a Docker image which allows to run Postgres PSQL client, 
>Docker & Docker Compose
>2. I run it with '--volume=/var/run/docker.sock:/var/run/docker.sock' 
>as arguments, to be able to run in the same Docker environment
>3. I run a serie a bash commands inside this container
>4. the first action I do is to create a Postgres container using 
>Docker Compose
>5. I can get the port of the created Postgres container, no problem
>6. I then try to connect to the Postgres container - but which host 
>can I use?
>
> As mentioned, this is a simplification of a more complex case, but the 
> general idea is a build which creates its own containers (like a database) 
> and tries to connect to it to perform some tests. But this build runs 
> itself in Docker container and does not seem able to reach the other 
> containers on the specified port. I've tried localhost, ${NODE_NAME}. 
> Nothing was worked so far.
>
> The 
> https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Custom+Build+Environment+Plugin
>  
> is supposed to put DOCKER_HOST available for such a purpose, but this does 
> not seem available any longer when in the pipeline.
>
> Can someone help me resolve this problem?
>
> Thanks,
> Damien.
>

-- 
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/6d93d9ff-32d3-4898-9edd-75e697919eb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Docker in Docker in Jenkins Pipeline - how to access the Docker host?

[Damien Coraboeuf]

Hi,

After having struggled, I decided to create a simplified version of a 
pipeline, which highlights the issue.

Environment: Linux, Jenkins 2.23, latest versions of the pipeline 
components.

Given the pipeline definition at https://github.com/nemerosa/jenkins-docker:

   1. I build a Docker image which allows to run Postgres PSQL client, 
   Docker & Docker Compose
   2. I run it with '--volume=/var/run/docker.sock:/var/run/docker.sock' as 
   arguments, to be able to run in the same Docker environment
   3. I run a serie a bash commands inside this container
   4. the first action I do is to create a Postgres container using Docker 
   Compose
   5. I can get the port of the created Postgres container, no problem
   6. I then try to connect to the Postgres container - but which host can 
   I use?

As mentioned, this is a simplification of a more complex case, but the 
general idea is a build which creates its own containers (like a database) 
and tries to connect to it to perform some tests. But this build runs 
itself in Docker container and does not seem able to reach the other 
containers on the specified port. I've tried localhost, ${NODE_NAME}. 
Nothing was worked so far.

The 
https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Custom+Build+Environment+Plugin
 
is supposed to put DOCKER_HOST available for such a purpose, but this does 
not seem available any longer when in the pipeline.

Can someone help me resolve this problem?

Thanks,
Damien.

-- 
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/1cd96d96-c0aa-4b0a-b250-81bded535e7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

maven.jenkins-ci.org connection error

[Damien Coraboeuf]

Hi,

When trying to deploy a plugin, I get the following error:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on 
project ontrack: Failed to deploy artifacts: Could not transfer artifact 
org.jenkins-ci.plugins:ontrack:hpi:2.22.2 from/to maven.jenkins-ci.org 
(http://maven.jenkins-ci.org:8081/content/repositories/releases): Connect to 
maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24] failed: 
Connection refused -> [Help 1]


Is there some outage? Or has something changed recently?

Thanks,
Damien Coraboeuf.

-- 
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/8cca92bf-f108-417c-b58e-8acc0c005c06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

CloudBees Docker Custom Build Environment Plugin

[Damien Coraboeuf]

Hi,

I have the following scenario, which does not sound so exotic:

* I'm using the CloudBees Docker Custom Build Environment Plugin (v1.2)
* a Docker container is defined and run, with a local JVM 
(see 
https://github.com/nemerosa/ontrack/blob/57471f8222a602b59b0729ae69113cb1babaa649/seed/env/Dockerfile)
* in my Jenkins job, I run a shell to run Gradle, providing the path to JVM 
in the container, using ./gradlew 
... -Dorg.gradle.java.home=/usr/lib/jvm/java-8-openjdk-amd64

However, when running the job, I still get the following error:

ERROR: JAVA_HOME is set to an invalid directory: /usr/lib/jvm/java-8-oracle


This Java home is the one from the *Jenkins master*. The JAVA_HOME is set 
by the job and inherited by the job, and finally available in the 
container...

I wanted to know if you had any example of running a Gradle based job using 
the JVM you define in your Docker file.

Thanks,
Damien.

-- 
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/9d899696-fe38-4bd1-b11c-e077cda23e52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CloudBees Docker Custom Build Environment Plugin

[Damien Coraboeuf]

Well, a bit classic: I just found the answer after having posted the topic 
:)

Instead of using the org.gradle.java.home property, I explicitly declare 
the JAVA_HOME in my build shell:

export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
./gradlew ...

Damien.

On Saturday, 27 June 2015 17:29:31 UTC+2, Damien Coraboeuf wrote:

 Hi,

 I have the following scenario, which does not sound so exotic:

 * I'm using the CloudBees Docker Custom Build Environment Plugin (v1.2)
 * a Docker container is defined and run, with a local JVM (see 
 https://github.com/nemerosa/ontrack/blob/57471f8222a602b59b0729ae69113cb1babaa649/seed/env/Dockerfile
 )
 * in my Jenkins job, I run a shell to run Gradle, providing the path to 
 JVM in the container, using ./gradlew 
 ... -Dorg.gradle.java.home=/usr/lib/jvm/java-8-openjdk-amd64

 However, when running the job, I still get the following error:

 ERROR: JAVA_HOME is set to an invalid directory: /usr/lib/jvm/java-8-oracle


 This Java home is the one from the *Jenkins master*. The JAVA_HOME is set 
 by the job and inherited by the job, and finally available in the 
 container...

 I wanted to know if you had any example of running a Gradle based job 
 using the JVM you define in your Docker file.

 Thanks,
 Damien.


-- 
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/b50f227c-d631-415a-824e-097229cd8cbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.