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
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/p
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
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 fro
19, 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&#x
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
ech
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.
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
l
ote:
>
> 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 2
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 /warnin
se 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 Coraboe
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
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
&
nkins 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 Us
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
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
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
Hi,
You can put this in a `script` section, and put what you need in
environment variables for the rest of the stages / steps:
steps {
script {
...
def shortGitCommit = "${gitCommit[0..10]}" as String
env.SHORT_GIT_COMMIT = shortGitCommit
...
}
echo "Short Git Com
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 av
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 cou
pecificaly 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
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
_name" in your build step.
>
> Mark Waite
>
> On Sat, Feb 18, 2017 at 11:10 AM Damien Coraboeuf > 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 m
gt; 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
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
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,
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
> be
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/
the Docker daemon, I also declare a
.dockerignore file which contains only:
*
!Dockerfile
This way, only the Dockerfile itself is sent to the build context for the
image.
Best regards,
Damien.
On Wednesday, 15 February 2017 21:30:16 UTC+1, Damien Coraboeuf wrote:
>
> Hi,
>
> I'
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 in
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 {
agen
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
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 ima
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.
--
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://git
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/Do
36 matches
Mail list logo
