Use of personal credentials in Jenkins Pipeline (Declarative)

[drew . leske]

Hi all,

I would like to be able to use a personal credential in Jenkins for a 
Pipeline build, and there does not appear to be a way to do this.  My first 
attempt was to call `credentials('cred-id')` but this fails in the build 
with 
`org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: 
'cred-id'`. I then found this issue in Jira: 
https://issues.jenkins-ci.org/browse/JENKINS-32417. 
 The explanation given in closing the ticket:

Indeed after some reasoning this looked as a not-a-defect since personal 
credentials should not appear in a job configuration. Personal credentials, 
as opposite, correctly appear if the build is parametrised with a 
credential parameter: when building a job you can successfully select the 
credentials belonging to your user.

Fair enough.  I then attempted to make the build a parameterized build with 
the credentials selectable on build initiation.  Say I have one set up to 
take a credential as a parameter and then provide this to the pipeline. 
 This leads to syntax errors in the build:

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 10: Internal function call parameters must be strings. @ line 
10, column 26.
   CREDS = credentials(env.LOGIN)


I can access $LOGIN through the pipeline in a script block, but it does not 
appear I can make use of it with `credentials()`.  *Even if I could* I believe 
it would just have the exact same problem as by explicitly naming the 
credential in the pipeline, because the parametrized build does not expose the 
credentials, just the ID.

Is it possible to use personal credentials with declarative pipeline?

Thanks,
Drew.



-- 
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/4a246c6b-988c-4987-8da7-93bf193e8614%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Stickers

[niristotle okram]

On a lighter note: Does sticking a jenkins sticker, increases productivity
or skill level??? 😬😬😬




On Fri, Jul 14, 2017 at 12:31 PM Aldrin Leal  wrote:

> Guys,
>
> (Brazilian living in Envigado here)
>
> If you want you can ship to my mailbox in US so I can get it here with a
> lower cost
>
> On Jul 14, 2017 11:57, "Jason LeMauk" 
> wrote:
>
> Hi Alyssa!
>
>
>
> I just saw some information on LinkedIn actually about Jenkins World. I
> wish I could be there, however I will not be attending this year.
>
> I am located in the North-Eastern United States. Is there an email best to
> reach you at? We’d love to have some dev stickers!
>
>
>
> Thank you for your help,
>
> Jason
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Alyssa Tong
> *Sent:* Friday, July 14, 2017 12:15 PM
> *To:* jenkinsci-users 
> *Subject:* Re: Jenkins Stickers
>
>
>
> Hi Jason,
>
>
>
> can you let me know where you are located? Will you be at Jenkins World
> ? If you are we'll have
> plenty of stickers ready for you.
>
>
>
> thnx
>
> alyssa
>
>
>
> On Wed, Jul 12, 2017 at 9:42 AM, J0991 
> wrote:
>
> hello!
>
> I have been working these past few months to get Jenkins going for our
> companies projects. I'd also love to get a few stickers for the team here.
> If anybody else may have any stickers available my team would gladly take
> them!
>
> Thank you,
> Jason
>
>
>
> --
> View this message in context:
> http://jenkins-ci.361315.n4.nabble.com/Jenkins-Stickers-tp4900135p4900450.html
> Sent from the Jenkins users mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1499877762688-4900450.post%40n4.nabble.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/CAMBsfbtsF9eWpRhTLgWdN83tzX5vdQO_iyZUXdsZd6Na80KB8Q%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/BY2PR12MB0599FD21EC5531E2299DEEE389AD0%40BY2PR12MB0599.namprd12.prod.outlook.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/CALpo8Nvdy2ghZ2vf9-V7HLSQ5%2B0H4BUuk28ECOi35-%3D_W%2Bws8A%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from mobile device, excuse typos if any.

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

RE: Jenkins Stickers

[Aldrin Leal]

Guys,

(Brazilian living in Envigado here)

If you want you can ship to my mailbox in US so I can get it here with a
lower cost

On Jul 14, 2017 11:57, "Jason LeMauk" 
wrote:

Hi Alyssa!



I just saw some information on LinkedIn actually about Jenkins World. I
wish I could be there, however I will not be attending this year.

I am located in the North-Eastern United States. Is there an email best to
reach you at? We’d love to have some dev stickers!



Thank you for your help,

Jason





*From:* jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@
googlegroups.com] *On Behalf Of *Alyssa Tong
*Sent:* Friday, July 14, 2017 12:15 PM
*To:* jenkinsci-users 
*Subject:* Re: Jenkins Stickers



Hi Jason,



can you let me know where you are located? Will you be at Jenkins World
? If you are we'll have plenty
of stickers ready for you.



thnx

alyssa



On Wed, Jul 12, 2017 at 9:42 AM, J0991 
wrote:

hello!

I have been working these past few months to get Jenkins going for our
companies projects. I'd also love to get a few stickers for the team here.
If anybody else may have any stickers available my team would gladly take
them!

Thank you,
Jason



--
View this message in context: http://jenkins-ci.361315.n4.
nabble.com/Jenkins-Stickers-tp4900135p4900450.html
Sent from the Jenkins users mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-users/1499877762688-4900450.post%40n4.nabble.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/CAMBsfbtsF9eWpRhTLgWdN83tzX5vd
QO_iyZUXdsZd6Na80KB8Q%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/BY2PR12MB0599FD21EC5531E2299DE
EE389AD0%40BY2PR12MB0599.namprd12.prod.outlook.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/CALpo8Nvdy2ghZ2vf9-V7HLSQ5%2B0H4BUuk28ECOi35-%3D_W%2Bws8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins pipeline script params not recognized, bad substitution error

[Kai]

thanks so much, that worked!

On Tuesday, July 11, 2017 at 2:26:40 AM UTC-7, Jakub Pawlinski wrote:
>
> try using double quote:
>
> sh "python deploy.py ${params.version}"
>
> I think single quotes do not evaluate strings
>

-- 
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/0b37a833-0789-4aa2-93f9-58a028109f05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins Stickers

[Jason LeMauk]

Hi Alyssa!

I just saw some information on LinkedIn actually about Jenkins World. I wish I 
could be there, however I will not be attending this year.
I am located in the North-Eastern United States. Is there an email best to 
reach you at? We’d love to have some dev stickers!

Thank you for your help,
Jason


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Alyssa Tong
Sent: Friday, July 14, 2017 12:15 PM
To: jenkinsci-users 
Subject: Re: Jenkins Stickers

Hi Jason,

can you let me know where you are located? Will you be at Jenkins 
World? If you are we'll have 
plenty of stickers ready for you.

thnx
alyssa

On Wed, Jul 12, 2017 at 9:42 AM, J0991 
mailto:jason.lem...@csquaredsystems.com>> 
wrote:
hello!

I have been working these past few months to get Jenkins going for our
companies projects. I'd also love to get a few stickers for the team here.
If anybody else may have any stickers available my team would gladly take
them!

Thank you,
Jason



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Jenkins-Stickers-tp4900135p4900450.html
Sent from the Jenkins users mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1499877762688-4900450.post%40n4.nabble.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/CAMBsfbtsF9eWpRhTLgWdN83tzX5vdQO_iyZUXdsZd6Na80KB8Q%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/BY2PR12MB0599FD21EC5531E2299DEEE389AD0%40BY2PR12MB0599.namprd12.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Stickers

[Alyssa Tong]

Hi Jason,

can you let me know where you are located? Will you be at Jenkins World
? If you are we'll have plenty
of stickers ready for you.

thnx
alyssa

On Wed, Jul 12, 2017 at 9:42 AM, J0991 
wrote:

> hello!
>
> I have been working these past few months to get Jenkins going for our
> companies projects. I'd also love to get a few stickers for the team here.
> If anybody else may have any stickers available my team would gladly take
> them!
>
> Thank you,
> Jason
>
>
>
> --
> View this message in context: http://jenkins-ci.361315.n4.
> nabble.com/Jenkins-Stickers-tp4900135p4900450.html
> Sent from the Jenkins users mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/1499877762688-4900450.post%40n4.nabble.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/CAMBsfbtsF9eWpRhTLgWdN83tzX5vdQO_iyZUXdsZd6Na80KB8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hard] problem building github tags

[Mark Waite]

On Friday, July 14, 2017 at 7:56:00 AM UTC-8, Samuel Henrique wrote:
>
> Hello,
>
> I'm trying to make jenkins trigger a build whenever a new tag is pushed to 
> my git repo.
>
> I already made it to trigger builds when a tag pointing to a new commit is 
> pushed, by setting:
>
> *refspec:* +refs/tags/*:refs/remotes/origin/tags/*
>> *branch specifier:* **
>
>
> The problem is that the builds are not triggered when i tag some commit 
> that already has another tag, even if its an annotated tag.
>
> The use case is as follows:
>
> 1)We need devs to be able to deploy our webapp by tagging releases on 
> github (mostly in other branches than master), like tag: v1.0.0 (the 
> previous tag was v0.9.9).
> 2)We need to be able to rollback deploys, by tagging again previous 
> releases (rollbacks will be always tagging commits on master), like tag: 
> v0.9.9-rollback [ponting to the same commit as v0.9.9).
> 3)We also need to follow some process that would allow fresh servers to 
> retrieve the same deployed release as the other servers (dealing with 
> autoscalling/dynamic inventory)
>
> The 3rd item is easily solvable by configuring capistrano to self-deploy 
> the last tag (sorting tags by taggerdate) on server startup (so new 
> machines will fetch rollbacks too).
>
> The 1st item is already good, as jenkins always trigger a build when a tag 
> ponting to a new commit is pushed.
>
> My problem is with rollbacks (2nd item), jenkins will receive the git 
> hook, poll the repository but won't trigger the build, it detects the new 
> tag but it acts as it already built that.
>
> I've searched online and from what i read, i think the git plugin is 
> checking the hash the tag points to, not the hash from the tag itself, thus 
> it doesn't detect a change. Can somebody confirm if i'm right, or if the 
> problem is is another plugin?
>
>
That is correct.  The git plugin assumes that once it has built a commit, 
then it does not need to build it again.

There are alternatives that may allow you to force a build of an already 
built commit.  For instance, you could parameterize a build to take the tag 
of the commit to build as an argument, then invoke it with a POST from the 
"curl" command to build that specific tag.  That isn't as elegant as the 
webhook technique that you're trying to use, since it requires that you 
create something that detects the creation of a new tag, then when the new 
tag is detected, it calls that curl command.

Mark Waite
 

> Any help is highly appreciated.
>

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

[hard] problem building github tags

[Samuel Henrique]

Hello,

I'm trying to make jenkins trigger a build whenever a new tag is pushed to 
my git repo.

I already made it to trigger builds when a tag pointing to a new commit is 
pushed, by setting:

*refspec:* +refs/tags/*:refs/remotes/origin/tags/*
> *branch specifier:* **


The problem is that the builds are not triggered when i tag some commit 
that already has another tag, even if its an annotated tag.

The use case is as follows:

1)We need devs to be able to deploy our webapp by tagging releases on 
github (mostly in other branches than master), like tag: v1.0.0 (the 
previous tag was v0.9.9).
2)We need to be able to rollback deploys, by tagging again previous 
releases (rollbacks will be always tagging commits on master), like tag: 
v0.9.9-rollback [ponting to the same commit as v0.9.9).
3)We also need to follow some process that would allow fresh servers to 
retrieve the same deployed release as the other servers (dealing with 
autoscalling/dynamic inventory)

The 3rd item is easily solvable by configuring capistrano to self-deploy 
the last tag (sorting tags by taggerdate) on server startup (so new 
machines will fetch rollbacks too).

The 1st item is already good, as jenkins always trigger a build when a tag 
ponting to a new commit is pushed.

My problem is with rollbacks (2nd item), jenkins will receive the git hook, 
poll the repository but won't trigger the build, it detects the new tag but 
it acts as it already built that.

I've searched online and from what i read, i think the git plugin is 
checking the hash the tag points to, not the hash from the tag itself, thus 
it doesn't detect a change. Can somebody confirm if i'm right, or if the 
problem is is another plugin?

Any help is highly appreciated.

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

Re: Jenkins Distributed Builds: Permission tiers for project-based matrix authorization strategy

[Artur Szostak]

I think you want to look into the following instead of the matrix based 
strategy:
https://wiki.jenkins.io/display/JENKINS/Role+Strategy+Plugin


From: jenkinsci-users@googlegroups.com  on 
behalf of Jason LeMauk 
Sent: 14 July 2017 15:06:46
To: jenkinsci-users@googlegroups.com
Subject: Jenkins Distributed Builds: Permission tiers for project-based matrix 
authorization strategy

Hello Jenkins Community!
I had some questions for those of you fairly experienced with administering / 
maintaining a Jenkins distributed build system.
I have a single Jenkins Master, and three or four Jenkins SSH Agents / Slaves 
running in VirtualBox (Jenkins host machine is running Ubuntu 14.04 LTS as well 
as the Jenkins Agents / Slave virtual machines).
The goal with the distributed build system is to achieve separate build / test 
/ deployment environments for each project. The concern that having all the 
software installed on the same machine (Jenkins host machine), could 
potentially pose issues for Jenkins Master’s machine as well as software needed 
to build / test / deploy one team’s applications could affect other teams and 
hold them up unnecessarily.

·My question is what is the best method for authorization strategy when 
dealing with multiple teams in a Jenkins Distributed Builds setup?
We are going to be using LDAP for our security realm (via the LDAP plugin), if 
that makes any difference. My obvious initial thoughts are to use the 
project-based matrix authorization strategy:

1.  Ideally I’d like to have our global Jenkins Administrators setup with 
permissions to perform any actions within Jenkins globally..

2.  I’d like to have a lower level administrator (Project Administrators, 
likely team leads), who are granted all permissions on a job / project basis. 
Jenkins Global Administrators decide the permissions for these users.

3.  The last tier of users are average Jenkins Users. The permissions for 
these users would be set by Project Administrators as they see fit. I believe 
Global Jenkins Administrators would need to add the users and then Jenkins 
Project Level Administrators can assign permissions for their team’s project / 
job.
So in the Jenkins distributed build system we have three tiers of users, each 
with lesser permissions than the last:

1.  Global Jenkins Administrators: Manages Project Level Administrators and 
Average Jenkins Users

2.  Project Level Administrators Manages Average Jenkins Users for their 
project / job.

3.  Average Jenkins Users: Lowest level user with the most restrictive 
permissions. Doesn’t not manage Jenkins for any other users.

-Is this a typical setup when administering Jenkins Distributed Build 
system with multiple teams involved?

-Am I understanding the user of the Project-based matrix authorization 
strategy correctly?

-Does anybody have any experience with a different access control 
approach?
Thank you to anyone who has any experience with maintaining a distributed build 
system involving several teams!

-J

--
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/BY2PR12MB0599D6E9BBB864A9B4DD177889AD0%40BY2PR12MB0599.namprd12.prod.outlook.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/d105f7f066be401792a1d72a04dc23fa%40partner.eso.org.
For more options, visit https://groups.google.com/d/optout.

Jenkins Distributed Builds: Permission tiers for project-based matrix authorization strategy

[Jason LeMauk]

Hello Jenkins Community!
I had some questions for those of you fairly experienced with administering / 
maintaining a Jenkins distributed build system.
I have a single Jenkins Master, and three or four Jenkins SSH Agents / Slaves 
running in VirtualBox (Jenkins host machine is running Ubuntu 14.04 LTS as well 
as the Jenkins Agents / Slave virtual machines).
The goal with the distributed build system is to achieve separate build / test 
/ deployment environments for each project. The concern that having all the 
software installed on the same machine (Jenkins host machine), could 
potentially pose issues for Jenkins Master's machine as well as software needed 
to build / test / deploy one team's applications could affect other teams and 
hold them up unnecessarily.

*My question is what is the best method for authorization strategy when 
dealing with multiple teams in a Jenkins Distributed Builds setup?
We are going to be using LDAP for our security realm (via the LDAP plugin), if 
that makes any difference. My obvious initial thoughts are to use the 
project-based matrix authorization strategy:

1.  Ideally I'd like to have our global Jenkins Administrators setup with 
permissions to perform any actions within Jenkins globally..

2.  I'd like to have a lower level administrator (Project Administrators, 
likely team leads), who are granted all permissions on a job / project basis. 
Jenkins Global Administrators decide the permissions for these users.

3.  The last tier of users are average Jenkins Users. The permissions for 
these users would be set by Project Administrators as they see fit. I believe 
Global Jenkins Administrators would need to add the users and then Jenkins 
Project Level Administrators can assign permissions for their team's project / 
job.
So in the Jenkins distributed build system we have three tiers of users, each 
with lesser permissions than the last:

1.  Global Jenkins Administrators: Manages Project Level Administrators and 
Average Jenkins Users

2.  Project Level Administrators Manages Average Jenkins Users for their 
project / job.

3.  Average Jenkins Users: Lowest level user with the most restrictive 
permissions. Doesn't not manage Jenkins for any other users.

-Is this a typical setup when administering Jenkins Distributed Build 
system with multiple teams involved?

-Am I understanding the user of the Project-based matrix authorization 
strategy correctly?

-Does anybody have any experience with a different access control 
approach?
Thank you to anyone who has any experience with maintaining a distributed build 
system involving several teams!

-J

-- 
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/BY2PR12MB0599D6E9BBB864A9B4DD177889AD0%40BY2PR12MB0599.namprd12.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins non blocking triggered projects

[tuk]

Hi

Can anyone let me know if it is even possible to achieve this?

Thanks,

On Thursday, 13 July 2017 15:00:55 UTC+5:30, tuk wrote:
>
> Cross-posting from stackoverflow 
> 
>
> We have a parent build which triggers multiple child builds. Now all the 
> child builds are blocking as shown below:-
>
>
> 
>
>
>
>
>
>
>
> Is there a way we can make some of the child builds non-blocking (may be 
> by some callback means or some other) and also get the status of the child 
> build in parent build?
>

-- 
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/7d551060-06da-4a61-b98d-549b5bc0ab8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.