Re: Wrong output on .../job/*/maven

[Cyrille Le Clerc]

Hi Aaron,

- Why do I sometimes get duplicate artifacts? They are not duplicated on 
> disk. In the console log, I just see a single invocation of 
> artifactsPublisher but sometimes, it reports the same artifact several 
> times.


Can you share the Jenkinsfile and the logs of your build? Usually artifact 
are displayed several time because "mvn package" or more than "package" 
("install" or "deploy")  is called several times in the build (e.g. 
invoking "mvn test" then "mvn deploy")
 

> - Why isn't C listed as "Downstream Job" of B?


Can you please share screenshots of the "/maven" tab of both job "B" and 
"C"?
By default, downstream pipeline triggers only work when a pipeline 
is"success" or "unstable" and when the "mvn" goal is "deploy". This means 
that by default, "mvn package" or "mvn install" would not trigger a 
downstram pipeline.
 

> - How can I collect more information to debug this?


Please see new FAQ entry 
https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowcanItroubleshootproblemsoftriggerofdownstreampipelines
 

On Monday, March 18, 2019 at 3:15:26 PM UTC, Aaron Digulla wrote:
>
> I have three projects in my example, A, B and C.
>
> A is built on another Jenkins PROD. It's deployed to Nexus.
>
> B depends on A. It's built on Jenkins TEST.
>
> C depends on B. It's also built on Jenkins TEST.
>
> All three projects have a SNAPSHOT version.
>
> The web page .../job/*/maven of B shows me:
>
> - All artifacts of B twice (*.jar, *.jar, *-sources.jar, *-sources.jar, 
> *-test-sources.jar, *-test-sources.jar, *.pom, *.pom, *-tests.jar, 
> *-tests.jar)
> - No "Upstream Builds"
> - No "Downstream Jobs"
> - A is listed as dependency
>
> I'd expect each artifact of B once and C as downstream job. Not sure about 
> dependencies but seeing A here would be nice even though it's built on 
> another Jenkins.
>
> The web page .../job/*/maven of C shows me:
>
> - Just some duplicate artifacts. This is a multi-module build. I'm seeing 
> the root POM twice, everything else just once.
> - No "Upstream Builds"
> - No "Downstream Jobs"
> - A and B are listed as dependencies.
>
> As far as I can tell, the two jobs use the same Jenkins Pipeline. They are 
> both of type "Multibranch Pipeline".
>
> B gets deployed to Nexus when I build the "master" and release branches 
> but not for feature branches. C only gets deployed to Nexus when it's a 
> release branch.
>
> I'm admin on Jenkins TEST, so I'm pretty sure it's not a ITEM.Read 
> permission issue.
>
> There is no config option "Build whenever a SNAPSHOT dependency is built" 
> for the jobs B or C. I can see the option when I click "View Configuration" 
> in .../job/*/master/configure
>
> Questions:
>
> - Why do I sometimes get duplicate artifacts? They are not duplicated on 
> disk. In the console log, I just see a single invocation of 
> artifactsPublisher but sometimes, it reports the same artifact several 
> times.
> - Why isn't C listed as "Downstream Job" of B?
> - How can I collect more information to debug this?
>
> Regards,
>
> -- 
> Aaron Digulla
>

-- 
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/b83b080e-eac7-417b-acdc-74319c4aa9a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Performance loading slow

[Victor Martinez]

There are a couple of interesting articles/presentations to configure the 
JVM accordingly, see the below reply:
- https://groups.google.com/d/msg/jenkinsci-users/T7F9FHzSYtY/xq5k9JdjBAAJ

Cheers

-- 
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/5bc7be6c-6354-480e-ba9c-6a0e007a3e2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

JRE version requirement

[Basil Crow]

Per the "Upgrading Jenkins Java version from 8 to 11" page [1]:

> All agents must be running on the same JVM version as the master (because of
> how masters and agents communicate). If you're upgrading your Jenkins master
> to run on Java 11, you also need to upgrade the JVM on your agents.

Per the "Java requirements" page [2]:

> If you use Swarm Plugin to create agents, JRE version must be equal to the
> version of the master

Why is there a requirement for agents to be running on the same JRE version as
the master? Is this because backwards-incompatible changes have been made to
serializable classes in the Java 11 runtime? If so, could someone please
elaborate?

Thanks,
Basil

[1] https://jenkins.io/doc/administration/requirements/upgrade-java-guidelines/
[2] https://jenkins.io/doc/administration/requirements/java/

-- 
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/CAFwNDjqajNX-EDiX2a2UsLfufn1jCa5jpEx3gD%3DWk%2BkYGiNQyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[t3knoid]

I added the following item: 
Git for Windows Installation and Windows Certificate Stores


On Monday, March 18, 2019 at 2:02:52 PM UTC-4, Mark Waite wrote:
>
> That's a very useful result.  Thanks for discovering it.  Would you be 
> willing to put a note into the git plugin wiki page describing what you saw 
> and how to resolve it?
>
> We've had other surprises like that (credentials manager, for example), 
> and the wiki page has been a good place to put the information until the 
> time when the plugin finds a better way to prevent the problem or warn 
> users about the problem.
>
> Mark Waite
>
> On Mon, Mar 18, 2019 at 11:01 AM t3knoid > 
> wrote:
>
>> I figured out why this was happening. It's user error :-). When 
>> installing git for windows, make sure to use "Use the native Windows Secure 
>> Channel library" option during installation.
>>
>>
>>
>> On Saturday, March 16, 2019 at 12:15:51 PM UTC-4, t3knoid wrote:
>>>
>>> I have a new Jenkins server that has not used git for checking out. I 
>>> tried using a simple git checkout, just using a freestyle project. For some 
>>> reason I get a "Getting "Couldn't find any revision to build" whenever I 
>>> try to check out. Using an older server checks out the same repo just 
>>> fine...also using a new freestyle job.
>>>
>>> Using the new server, I checked out something from github, and that 
>>> worked fine. The server I am using is internal. It is using Bitbucket. I 
>>> don't really think that should make a difference.
>>>
>> -- 
>> 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/5ee800b6-bd9a-4f31-a804-28341b1212db%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Thanks!
> Mark Waite
>

-- 
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/ba85743c-a2ae-48ea-af18-aece9c7f360b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[t3knoid]

Yeah sure. That's a good idea.

On Monday, March 18, 2019 at 2:02:52 PM UTC-4, Mark Waite wrote:
>
> That's a very useful result.  Thanks for discovering it.  Would you be 
> willing to put a note into the git plugin wiki page describing what you saw 
> and how to resolve it?
>
> We've had other surprises like that (credentials manager, for example), 
> and the wiki page has been a good place to put the information until the 
> time when the plugin finds a better way to prevent the problem or warn 
> users about the problem.
>
> Mark Waite
>
> On Mon, Mar 18, 2019 at 11:01 AM t3knoid > 
> wrote:
>
>> I figured out why this was happening. It's user error :-). When 
>> installing git for windows, make sure to use "Use the native Windows Secure 
>> Channel library" option during installation.
>>
>>
>>
>> On Saturday, March 16, 2019 at 12:15:51 PM UTC-4, t3knoid wrote:
>>>
>>> I have a new Jenkins server that has not used git for checking out. I 
>>> tried using a simple git checkout, just using a freestyle project. For some 
>>> reason I get a "Getting "Couldn't find any revision to build" whenever I 
>>> try to check out. Using an older server checks out the same repo just 
>>> fine...also using a new freestyle job.
>>>
>>> Using the new server, I checked out something from github, and that 
>>> worked fine. The server I am using is internal. It is using Bitbucket. I 
>>> don't really think that should make a difference.
>>>
>> -- 
>> 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/5ee800b6-bd9a-4f31-a804-28341b1212db%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Thanks!
> Mark Waite
>

-- 
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/02f71d36-8551-4bb7-8556-301427d36ab8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[Mark Waite]

That's a very useful result.  Thanks for discovering it.  Would you be
willing to put a note into the git plugin wiki page describing what you saw
and how to resolve it?

We've had other surprises like that (credentials manager, for example), and
the wiki page has been a good place to put the information until the time
when the plugin finds a better way to prevent the problem or warn users
about the problem.

Mark Waite

On Mon, Mar 18, 2019 at 11:01 AM t3knoid  wrote:

> I figured out why this was happening. It's user error :-). When installing
> git for windows, make sure to use "Use the native Windows Secure Channel
> library" option during installation.
>
>
>
> On Saturday, March 16, 2019 at 12:15:51 PM UTC-4, t3knoid wrote:
>>
>> I have a new Jenkins server that has not used git for checking out. I
>> tried using a simple git checkout, just using a freestyle project. For some
>> reason I get a "Getting "Couldn't find any revision to build" whenever I
>> try to check out. Using an older server checks out the same repo just
>> fine...also using a new freestyle job.
>>
>> Using the new server, I checked out something from github, and that
>> worked fine. The server I am using is internal. It is using Bitbucket. I
>> don't really think that should make a difference.
>>
> --
> 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/5ee800b6-bd9a-4f31-a804-28341b1212db%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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/CAO49JtFzsQeHisBvY5bXMaXmGTSd7r2D%2Br93hvSkaCFvK%2BOrbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Containerized Jenkins master and agents

[Daniele Riccucci]

Hello,

thank you for the reply. I did try, however there are a few reasons why 
that didn't work for me:


* the jnlp-agent-docker, being based on openjdk at its root, doesn't 
have several build tools more readily available on other images


* the agent specifically has the jnlp-slave built-in which eases 
communication, most images would require `docker attach`


* the official jenkins/jenkins image doesn't seem to be natively able to 
run docker containers, for example the following pipeline:


pipeline {
agent {
docker {
image "golang:1.12-alpine"
}
}
stages {
stage('Build') {
steps {
git 'fails when it tries to execute the `docker login` command as it's not 
present.
This forced me to use the jnlp-agent which *does* have the docker 
command and mounts the /run/docker.sock from the host (or connects via TLS)


* such a workaround however does not support launching a second 
container and would require a different, customized image for every 
pipeline as a "Docker Agent template" configured in Jenkins, which is 
very cumbersome


It is very possible I'm missing something or misconfigured my Jenkins 
master but this is what I'm experiencing.


Regards,
Daniele

On 18/03/19 08:43, nicolas de loof wrote:

Hi.

Why do you use some "jnlp-agent-docker" agent as you then switch to 
another one, based on a docker image ? Why not just use the later for 
the whole build ?


Le lun. 18 mars 2019 à 07:20, Daniele Riccucci > a écrit :


Hello,
I recently switched to running Jenkins from host machine to a docker
container (https://hub.docker.com/r/jenkins/jenkins).
I was also using docker agents to build. This is now broken in my
current setup as I'm spinning up a slave container to run pipelines and
issues arise in a situation such as:

pipeline {
      agent { label 'jnlp-agent-docker' }
      // this is the major change as before it was not a container,
      // the label refers to a template with a similar version of
      // https://github.com/jenkinsci/jnlp-agents/ > docker
      stages {
          stage('Build') {
              agent {
                  docker { // could also be dockerfile
                      image ""
                  }
              }
              steps {
                  git 'myrepo'
                  sh "build"
                  archiveArtifacts artifacts: 'dist/**/*'
              }
          }
      }
}

The docker plugin (this one >
http://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin) is obviously
unable to mount workspaces in another container and builds fail.
I would like to avoid adding a new template for this and using
docker in
docker

(https://support.cloudbees.com/hc/en-us/articles/360001566111-Set-up-a-Docker-in-Docker-Agent-Template)

if possible
(https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/),

but I'll adapt to whatever works.

Is there a correct way to build using containers for jenkins, and the
slaves?

Thank you.

-- 
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/9fb2d785-1b74-c0d4-dd05-4b072e8efe59%40posteo.net.
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/CANMVJzmAcGFLmMmHd_TOpYHgZ%2Bw4fz%2BinQS3wEfeSrG-fNGDsg%40mail.gmail.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/1b996b5e-ba29-5c56-e9cf-d281d833b10f%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[t3knoid]

I figured out why this was happening. It's user error :-). When installing 
git for windows, make sure to use "Use the native Windows Secure Channel 
library" option during installation.



On Saturday, March 16, 2019 at 12:15:51 PM UTC-4, t3knoid wrote:
>
> I have a new Jenkins server that has not used git for checking out. I 
> tried using a simple git checkout, just using a freestyle project. For some 
> reason I get a "Getting "Couldn't find any revision to build" whenever I 
> try to check out. Using an older server checks out the same repo just 
> fine...also using a new freestyle job.
>
> Using the new server, I checked out something from github, and that worked 
> fine. The server I am using is internal. It is using Bitbucket. I don't 
> really think that should make a difference.
>

-- 
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/5ee800b6-bd9a-4f31-a804-28341b1212db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wrong output on .../job/*/maven

[Aaron Digulla]

I have three projects in my example, A, B and C.

A is built on another Jenkins PROD. It's deployed to Nexus.

B depends on A. It's built on Jenkins TEST.

C depends on B. It's also built on Jenkins TEST.

All three projects have a SNAPSHOT version.

The web page .../job/*/maven of B shows me:

- All artifacts of B twice (*.jar, *.jar, *-sources.jar, *-sources.jar, 
*-test-sources.jar, *-test-sources.jar, *.pom, *.pom, *-tests.jar, 
*-tests.jar)
- No "Upstream Builds"
- No "Downstream Jobs"
- A is listed as dependency

I'd expect each artifact of B once and C as downstream job. Not sure about 
dependencies but seeing A here would be nice even though it's built on 
another Jenkins.

The web page .../job/*/maven of C shows me:

- Just some duplicate artifacts. This is a multi-module build. I'm seeing 
the root POM twice, everything else just once.
- No "Upstream Builds"
- No "Downstream Jobs"
- A and B are listed as dependencies.

As far as I can tell, the two jobs use the same Jenkins Pipeline. They are 
both of type "Multibranch Pipeline".

B gets deployed to Nexus when I build the "master" and release branches but 
not for feature branches. C only gets deployed to Nexus when it's a release 
branch.

I'm admin on Jenkins TEST, so I'm pretty sure it's not a ITEM.Read 
permission issue.

There is no config option "Build whenever a SNAPSHOT dependency is built" 
for the jobs B or C. I can see the option when I click "View Configuration" 
in .../job/*/master/configure

Questions:

- Why do I sometimes get duplicate artifacts? They are not duplicated on 
disk. In the console log, I just see a single invocation of 
artifactsPublisher but sometimes, it reports the same artifact several 
times.
- Why isn't C listed as "Downstream Job" of B?
- How can I collect more information to debug this?

Regards,

-- 
Aaron Digulla

-- 
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/784f85d4-32f0-422c-8337-477dc36e8cc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Parameter parameter on the basis of other parameter

[Pratik Jain]

Need help with Build with Parameter.

I am having let say 4 features[Features 1,2,3,4]. Each feature is having n 
number of scenarios. 

What I want is if user select feature 1 and 2 then display only scenarios 
of feature1 and 2 of user to selection.

I know about Active choice parameter but it is not helping me much. let me 
know if any other plugin can help me in this.

Thanks

-- 
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/313e3064-2639-45d3-acd5-ce6ac4695615%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: How to Trigger back the Jenkins job from the job who triggered it?

[Daniel Butler]

I’m assuming you’re meaning freestyle jobs? Usually you’d have a parameter in 
Job X with the upstream job name that you can then use in the Parameterized 
Build Trigger to pass the parameter to Job X. 

What will be in place however to stop this ending up in a build loop? Otherwise 
Job B is going to trigger Job X which will trigger Job B which will trigger Job 
X...

Regards,
Daniel.


From: Ramdinesh J P
Sent: 18 March 2019 10:20
To: Jenkins Users
Subject: How to Trigger back the Jenkins job from the job who triggered it?


Here, three different jobs triggers the JOB X. Requirement is, on completion of 
JOB X, it should trigger back the job who triggered it.
For example, if JOB X is triggered by JOB B, it should trigger back only the 
JOB B.
Things I have tried:
1. I have used "build another job" option from Post build action, where I can 
mention the list of jobs needs to be triggered.
2. It is not satisfying my requirement as it is triggering all the JOBS listed 
in the box.
Kindly help !!
-- 
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/f9ad64f3-1ae9-40bd-9148-3721421884e7%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/5c8f8235.1c69fb81.50321.7de6%40mx.google.com.
For more options, visit https://groups.google.com/d/optout.

How to Trigger back the Jenkins job from the job who triggered it?

[Ramdinesh J P]

[image: jenkins_job.PNG]

Here, three different jobs triggers the JOB X. Requirement is, on 
completion of JOB X, it should trigger back the job who triggered it.

For example, if JOB X is triggered by JOB B, it should trigger back only 
the JOB B.

Things I have tried:

   1. 
   
   I have used "build another job" option from Post build action, where I 
   can mention the list of jobs needs to be triggered.
   2. 
   
   It is not satisfying my requirement as it is triggering all the JOBS 
   listed in the box.
   
Kindly help !!

-- 
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/f9ad64f3-1ae9-40bd-9148-3721421884e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Security - Pipeline parameterized credentials can be reused by other users

[kuisathaverat]

Multibranch pipeline with defaults
https://plugins.jenkins.io/pipeline-multibranch-defaults and Pipeline
Github plugin https://github.com/jenkinsci/pipeline-github-plugin  the
first allow you to set a Jenkinsfile by default on Multibranch projects so
you can have the Jenkinsfile outside of the project repo in another repo
that you manage with other permissions, the second allows you to interact
with GitHub, I use it to check permissions and other stuff in GitHub before
to start the build, to trigger build with comments, and check reviews, I
make all this stuff on a pipeline shared library that probably we make
public at some point.


El lun., 18 mar. 2019 a las 6:55, Jenn Briden ()
escribió:

> I am also interested in learning more. My understanding is that this is a
> permissions issue on the Item and not really pipeline. Please correct me if
> I misunderstood.
>
> On Sun, Mar 17, 2019 at 9:11 AM Cyrille Le Clerc 
> wrote:
>
>> @ivan I am very interested in this topic and I get a 404 on your first
>> link. Can you please verify the URL and maybe share a "non mobile" URL.
>>
>> On Saturday, March 16, 2019 at 4:48:12 PM UTC, Ivan Fernandez Calvo wrote:
>>>
>>> By using
>>> https://wiki.jenkins.io/plugins/servlet/mobile?contentId=102662618#content/view/10266261
>>> and removing permissions to configure jobs, maybe build also and allow only
>>> to trigger builds to some people or manage it with comments from GitHub
>>> (see
>>> https://wiki.jenkins.io/plugins/servlet/mobile?contentId=37749162#content/view/37749162)
>>> also on pipeline multibranch projects you ha be options to only trust on
>>> the jenkinsfile from the master branch
>>
>> --
>>
> 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/e5f5fe3b-35a1-44cd-a078-98c463ccc4df%40googlegroups.com
>> 
>> .
>> 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/QS8VKelHR2E/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/CAOC%3D136YKecmM8eQ2frJ9T5%3DD-tNfNCqgvaEzF_G%3Dvkf4Nb_8w%40mail.gmail.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/CAKo5QrrnHSrj2tz6evHkF%2BhWvut5BqriYRupGzzETDYrNx9qpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Containerized Jenkins master and agents

[nicolas de loof]

Hi.

Why do you use some "jnlp-agent-docker" agent as you then switch to another
one, based on a docker image ? Why not just use the later for the whole
build ?

Le lun. 18 mars 2019 à 07:20, Daniele Riccucci  a
écrit :

> Hello,
> I recently switched to running Jenkins from host machine to a docker
> container (https://hub.docker.com/r/jenkins/jenkins).
> I was also using docker agents to build. This is now broken in my
> current setup as I'm spinning up a slave container to run pipelines and
> issues arise in a situation such as:
>
> pipeline {
>  agent { label 'jnlp-agent-docker' }
>  // this is the major change as before it was not a container,
>  // the label refers to a template with a similar version of
>  // https://github.com/jenkinsci/jnlp-agents/ > docker
>  stages {
>  stage('Build') {
>  agent {
>  docker { // could also be dockerfile
>  image ""
>  }
>  }
>  steps {
>  git 'myrepo'
>  sh "build"
>  archiveArtifacts artifacts: 'dist/**/*'
>  }
>  }
>  }
> }
>
> The docker plugin (this one >
> http://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin) is obviously
> unable to mount workspaces in another container and builds fail.
> I would like to avoid adding a new template for this and using docker in
> docker
> (
> https://support.cloudbees.com/hc/en-us/articles/360001566111-Set-up-a-Docker-in-Docker-Agent-Template)
>
> if possible
> (https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/),
>
> but I'll adapt to whatever works.
>
> Is there a correct way to build using containers for jenkins, and the
> slaves?
>
> Thank you.
>
> --
> 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/9fb2d785-1b74-c0d4-dd05-4b072e8efe59%40posteo.net
> .
> 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/CANMVJzmAcGFLmMmHd_TOpYHgZ%2Bw4fz%2BinQS3wEfeSrG-fNGDsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Containerized Jenkins master and agents

[Daniele Riccucci]

Hello,
I recently switched to running Jenkins from host machine to a docker 
container (https://hub.docker.com/r/jenkins/jenkins).
I was also using docker agents to build. This is now broken in my 
current setup as I'm spinning up a slave container to run pipelines and 
issues arise in a situation such as:


pipeline {
agent { label 'jnlp-agent-docker' }
// this is the major change as before it was not a container,
// the label refers to a template with a similar version of
// https://github.com/jenkinsci/jnlp-agents/ > docker
stages {
stage('Build') {
agent {
docker { // could also be dockerfile
image ""
}
}
steps {
git 'myrepo'
sh "build"
archiveArtifacts artifacts: 'dist/**/*'
}
}
}
}

The docker plugin (this one > 
http://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin) is obviously 
unable to mount workspaces in another container and builds fail.
I would like to avoid adding a new template for this and using docker in 
docker 
(https://support.cloudbees.com/hc/en-us/articles/360001566111-Set-up-a-Docker-in-Docker-Agent-Template) 
if possible 
(https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/), 
but I'll adapt to whatever works.


Is there a correct way to build using containers for jenkins, and the 
slaves?


Thank you.

--
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/9fb2d785-1b74-c0d4-dd05-4b072e8efe59%40posteo.net.
For more options, visit https://groups.google.com/d/optout.