date:20161005

Re: Did the Jenkins version numbers just change?

2016-10-05 Thread Baptiste Mathus

For future reference, also
https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line

Le 5 oct. 2016 10:34 PM, "Sunil Shah"  a écrit :

> Ah thanks, that makes sense!
>
> On Wednesday, October 5, 2016 at 12:17:32 PM UTC-7, Stephen Connolly wrote:
>>
>> Perfectly normal.
>>
>> LTS versions are based on weekly releases.
>>
>> After 3 LTS releases, the next weekly is selected.
>>
>> (There was a critical issue in 2.7.3 hence a 2.7.4 shortly followed, but
>> that was the end of the line for the 2.7.x series, so now the next stage
>> let.line was selected as 2.19.x... In approx 3 months we will have
>> something like 2.29.x or 2.33.x depending on what the various weekly
>> releases look like at the time)
>>
>> On Wednesday 5 October 2016, Sunil Shah  wrote:
>>
>>> It looks like the LTS version just went from 2.7.4 to 2.19.1. Was there
>>> a reason for this change (or any documentation/discussion around it)?
>>>
>>> [image: Inline image 1]
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/CAD7EdumKTiaqoOt%2BxPM_jKEg1kcn_fp%
>>> 3DgBNtz9%3DN9gFbQa_fEA%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Sent from my phone
>>
> --
> 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/e133fb70-3d8a-433f-a925-3abe8328458a%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/CANWgJS43gJvXnKyyf9gwxNsR5QAjA%2BQSUFwrrkMLwQsE9-tk4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: special Characters significance

2016-10-05 Thread Baptiste Mathus

Where?

Le 5 oct. 2016 6:06 AM, "amol malokar"  a écrit :

> TEMPFOLDER=\\TEST\DATA\AD
>
> was interpreted to:
>
> \TESTDATAAD
>
>
> Updated the Jenkins and Saw this change was happening.
>
> --
> Regards,
> Amol
>
> --
> 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/CAKO2pR%3DsCW56t8zg2ADo_Py%3D%
> 2BTrifRU5eb4K4SYchD1rZ5dnXA%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/CANWgJS5OAQK3-B3Pmx37Yv_NU2bgAXGm9omCUfxcsVBbnud_Cw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Secure Jenkins and mutlibranch github pipeline trigger

2016-10-05 Thread Corey Wei

Hi Lionel,

I just tested this on Jenkins 2.19.1. 
Looks like "Re-register hooks for all jobs" is not working for my 
multibranch job. Is there anything I am missing?

Thanks

On Monday, May 9, 2016 at 9:08:52 PM UTC+8, Lionel Orellana wrote:
>
>
> Apologies for my rather disorganised thought process in this thread.  
>
> I just found the 'Re-register hooks for all jobs' in the global config 
> (GitHub Servers Advanced options). That created the hooks correctly for me 
> without any additional configuration in the multibranch job. 
>
> Thanks.
>
> On Saturday, 7 May 2016 16:38:49 UTC+10, Lionel Orellana wrote:
>>
>> Well seems like the solution would for the GitHub Plugin to support 
>> Multibranch pipelines
>>
>> On Saturday, 7 May 2016 12:29:22 UTC+10, Lionel Orellana wrote:
>>>
>>> Hi All
>>>
>>> How can I trigger a build on a multibranch pipeline where there is a 
>>> push in github and Jenkins requires authentication.
>>>
>>> I tried "Trigger builds remotely (e.g., from scripts)" but the token 
>>> generated here isn't enough for a github webhook to authenticate with 
>>> Jenkins.  Github throws "Authentication required". This is using  a 
>>> webhook like /job//build?token=some token  where 
>>> the token matches what's in the "Trigger builds remotely" configuration.
>>>
>>> Thanks
>>>
>>> Lionel.
>>>
>>>  
>>>
>>

-- 
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/7d523677-1684-4d78-8c54-94c8ff5659d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Config.xml of the job gets lost/deleted randomnly on jenkins restart or saving the configuration after changing it

2016-10-05 Thread touseef yousuf

Im currently facing an issue where the config.xml of my created jobs gets 
deleted randomly on Jenkins restart and the job is no longer available on 
the view,even the job folder is present on file system *but without 
config.xml *.I have no idea what leads to this randomn disappearance of the 
config.xml 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/6205536d-53ad-4000-89c5-376c83f7e0c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

triggering jenkins downstream project as per my parameter selection

2016-10-05 Thread sundar rajan

Greetings All , 

I have project EG : master & individual project A , B ,C 

>From master --> i need to have multiple choice option --> A B C 

If i select A & B --> In my down stream A & B prject has to run .

Conclusion : User have to select the multiple downstream project from the 
upstream project in GUI . 

-- 
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/1a41870e-fa14-41b8-b950-4cbe533169da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updating jenkins version in docker image cause exit 143

2016-10-05 Thread YusufSalahAdDin

Ok, i run it with parameter *-d *and i have this:

salahaddin@TulipanROG  ~/Proyectos/uzmantech/jenkins   master ●  
docker-compose up 
-d 
 ✓  4169  18:55:31 
Starting jenkins_data_1
Starting jenkins_slave_1
Starting jenkins_master_1
Starting jenkins_nginx_1
 salahaddin@TulipanROG  ~/Proyectos/uzmantech/jenkins   master ●  
docker-compose 
ps  
  
 ✓  4170  18:56:47 
  NameCommand   State  
Ports
---
jenkins_data_1 echo Data container for Je ...   Exit 
0  
jenkins_master_1   /bin/tini -- /usr/local/bi ...   Up   
0.0.0.0:5->5/tcp, 8080/tcp 
jenkins_nginx_1nginxUp   443/tcp, 
0.0.0.0:80->80/tcp
jenkins_slave_1/bin/bashExit 
0  

But browser can access to localhost.

El miércoles, 5 de octubre de 2016, 18:13:33 (UTC-5), YusufSalahAdDin 
escribió:
>
> I have this in bash:
>
>  docker-compose 
>> up   
>>
>>  1 ↵  4159  18:11:07 
>> Creating jenkins_slave_1
>> Creating jenkins_data_1
>> Creating jenkins_master_1
>> Creating jenkins_nginx_1
>> Attaching to jenkins_slave_1, jenkins_data_1, jenkins_master_1, 
>> jenkins_nginx_1
>> data_1| Data container for Jenkins
>> jenkins_data_1 exited with code 0
>> jenkins_slave_1 exited with code 0
>>
>
>
> El miércoles, 5 de octubre de 2016, 16:02:44 (UTC-5), Daniel Beck escribió:
>>
>> Anything interesting getting logged during startup? 
>>
>> > On 05.10.2016, at 22:55, YusufSalahAdDin  wrote: 
>> > 
>> > Hi guys! 
>> > 
>> > I have the next problem: 
>> > 
>> > I built an image with Jenkins 2.23 and run it, all is well. 
>> > 
>> > Today i want update jenkins to 2.24, so, i change some lines in the 
>> docker file, change version to 2.24 and update sha. 
>> > 
>> > I built it, all is well, but when i up the machine, well, i have an 
>> error 143: 
>> > docker-compose ps   
>>   ✓  4135  15:48:39 
>> >   NameCommandState Ports 
>> >  
>> > jenkins_data_1 echo Data container for Je ...   Exit 0   
>> > jenkins_master_1   /bin/tini -- /usr/local/bi ...   Exit 143 
>> > jenkins_nginx_1nginxExit 0   
>> > jenkins_slave_1/bin/bashExit 0   
>> > 
>> > Why? 
>> > 
>> > Can anyone help me. 
>> > 
>> > -- 
>> > 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/e57d4497-0f78-41ce-9c42-a8698361e5bb%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/3f8a1981-d9bd-40b3-aacc-b65d9ee9dce6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updating jenkins version in docker image cause exit 143

2016-10-05 Thread YusufSalahAdDin

I have this in bash:

 docker-compose 
> up
>   
>  1 ↵  4159  18:11:07 
> Creating jenkins_slave_1
> Creating jenkins_data_1
> Creating jenkins_master_1
> Creating jenkins_nginx_1
> Attaching to jenkins_slave_1, jenkins_data_1, jenkins_master_1, 
> jenkins_nginx_1
> data_1| Data container for Jenkins
> jenkins_data_1 exited with code 0
> jenkins_slave_1 exited with code 0
>


El miércoles, 5 de octubre de 2016, 16:02:44 (UTC-5), Daniel Beck escribió:
>
> Anything interesting getting logged during startup? 
>
> > On 05.10.2016, at 22:55, YusufSalahAdDin  > wrote: 
> > 
> > Hi guys! 
> > 
> > I have the next problem: 
> > 
> > I built an image with Jenkins 2.23 and run it, all is well. 
> > 
> > Today i want update jenkins to 2.24, so, i change some lines in the 
> docker file, change version to 2.24 and update sha. 
> > 
> > I built it, all is well, but when i up the machine, well, i have an 
> error 143: 
> > docker-compose ps   
>   ✓  4135  15:48:39 
> >   NameCommandState Ports 
> >  
> > jenkins_data_1 echo Data container for Je ...   Exit 0   
> > jenkins_master_1   /bin/tini -- /usr/local/bi ...   Exit 143 
> > jenkins_nginx_1nginxExit 0   
> > jenkins_slave_1/bin/bashExit 0   
> > 
> > Why? 
> > 
> > Can anyone help me. 
> > 
> > -- 
> > 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/e57d4497-0f78-41ce-9c42-a8698361e5bb%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/77841f61-b883-4f5d-a523-28fe0d9ab7f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AWS CodeDeploy Plugin Credentials Access Key/Secret Key set to Jenkins Admin U/P

2016-10-05 Thread Go Mezant

Hello,

Trying to set up Jenkins on an EC2 with Code Pipeline. Using Jenkins v2.24

The Plugin has a captions that says: 

*If keys are not specified, *the plugin will use the default credentials 
providers and pull from one of: Environment variables, credentials profile, 
or IAM instance role. The latter is recommended if running on an EC2 
instance.

I have set up an Amazon IAM User/Role and the Instance Profile so that 
Jenkins can pick up that key automatically. 

But when I go to Jenkins\Configure for the plugin, and I clear the Jenkins 
Admin user and password from the 
AWS Access Key and AWS Secret Key, then I save, the U/P automatically come 
back.

Being new to Jenkins, I'm not sure if I'm missing a setting somewhere else.

How can I get Jenkins to not automatically use the Jenkins Admin User and 
Password so I can leave the AWS Access Key and AWS Secret Key fields blank,
thus allowing Jenkins to pick up the keys from the profile instead??

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/a41f3938-2ce2-4d60-ade3-7f4f10e7a805%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Update jenkins version in a docker container

2016-10-05 Thread YusufSalahAdDin

Hi guys

I'm new in jenkins with docker, so, i thanks any help to me.

I want to know: How can we update jenkins in a existed docker container?

You know, i don't want lose my configuration, projects, build reports and 
etc., but i don't know how update jenkins in docker. 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/710ae6c5-e7ae-4c02-9c4c-ee74d172635e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updating jenkins version in docker image cause exit 143

2016-10-05 Thread YusufSalahAdDin

No, nothing, but the problem persist, i deleted all container and compose 
up again, and doesn't works, now i'm trying killing the docker machine and 
create again.

El miércoles, 5 de octubre de 2016, 16:02:44 (UTC-5), Daniel Beck escribió:
>
> Anything interesting getting logged during startup? 
>
> > On 05.10.2016, at 22:55, YusufSalahAdDin  > wrote: 
> > 
> > Hi guys! 
> > 
> > I have the next problem: 
> > 
> > I built an image with Jenkins 2.23 and run it, all is well. 
> > 
> > Today i want update jenkins to 2.24, so, i change some lines in the 
> docker file, change version to 2.24 and update sha. 
> > 
> > I built it, all is well, but when i up the machine, well, i have an 
> error 143: 
> > docker-compose ps   
>   ✓  4135  15:48:39 
> >   NameCommandState Ports 
> >  
> > jenkins_data_1 echo Data container for Je ...   Exit 0   
> > jenkins_master_1   /bin/tini -- /usr/local/bi ...   Exit 143 
> > jenkins_nginx_1nginxExit 0   
> > jenkins_slave_1/bin/bashExit 0   
> > 
> > Why? 
> > 
> > Can anyone help me. 
> > 
> > -- 
> > 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/e57d4497-0f78-41ce-9c42-a8698361e5bb%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/e6b8e8d9-da42-4e71-b445-cd5611ac1e19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updating jenkins version in docker image cause exit 143

2016-10-05 Thread Daniel Beck

Anything interesting getting logged during startup?

> On 05.10.2016, at 22:55, YusufSalahAdDin  wrote:
> 
> Hi guys!
> 
> I have the next problem:
> 
> I built an image with Jenkins 2.23 and run it, all is well.
> 
> Today i want update jenkins to 2.24, so, i change some lines in the docker 
> file, change version to 2.24 and update sha.
> 
> I built it, all is well, but when i up the machine, well, i have an error 143:
> docker-compose ps 
> ✓  4135  15:48:39 
>   NameCommandState Ports 
> 
> jenkins_data_1 echo Data container for Je ...   Exit 0   
> jenkins_master_1   /bin/tini -- /usr/local/bi ...   Exit 143 
> jenkins_nginx_1nginxExit 0   
> jenkins_slave_1/bin/bashExit 0  
> 
> Why?
> 
> Can anyone help me.
> 
> -- 
> 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/e57d4497-0f78-41ce-9c42-a8698361e5bb%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/7BE9CBB9-4DE9-4AA1-B506-17CA9E7970F4%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Updating jenkins version in docker image cause exit 143

2016-10-05 Thread YusufSalahAdDin

Hi guys!

I have the next problem:

I built an image with Jenkins 2.23 and run it, all is well.

Today i want update jenkins to 2.24, so, i change some lines in the docker 
file, change version to 2.24 and update sha.

I built it, all is well, but when i up the machine, well, i have an error 
143:

> docker-compose 
> ps
> 
>  ✓  4135  15:48:39 
>   NameCommandState Ports 
> 
> jenkins_data_1 echo Data container for Je ...   Exit 0   
> jenkins_master_1   /bin/tini -- /usr/local/bi ...   Exit 143 
> jenkins_nginx_1nginxExit 0   
> jenkins_slave_1/bin/bashExit 0  
>

Why?

Can anyone help me.

-- 
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/e57d4497-0f78-41ce-9c42-a8698361e5bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Did the Jenkins version numbers just change?

2016-10-05 Thread Sunil Shah

Ah thanks, that makes sense!

On Wednesday, October 5, 2016 at 12:17:32 PM UTC-7, Stephen Connolly wrote:
>
> Perfectly normal.
>
> LTS versions are based on weekly releases.
>
> After 3 LTS releases, the next weekly is selected.
>
> (There was a critical issue in 2.7.3 hence a 2.7.4 shortly followed, but 
> that was the end of the line for the 2.7.x series, so now the next stage 
> let.line was selected as 2.19.x... In approx 3 months we will have 
> something like 2.29.x or 2.33.x depending on what the various weekly 
> releases look like at the time)
>
> On Wednesday 5 October 2016, Sunil Shah > 
> wrote:
>
>> It looks like the LTS version just went from 2.7.4 to 2.19.1. Was there a 
>> reason for this change (or any documentation/discussion around it)?
>>
>> [image: Inline image 1]
>>
>> -- 
>> 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/CAD7EdumKTiaqoOt%2BxPM_jKEg1kcn_fp%3DgBNtz9%3DN9gFbQa_fEA%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Sent from my phone
>

-- 
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/e133fb70-3d8a-433f-a925-3abe8328458a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git plugin polling

2016-10-05 Thread Mark Waite

On Wed, Oct 5, 2016 at 9:29 AM  wrote:

> Our git server is set up to notify our jenkins instance whenever a commit
> was received by using cURL by saying checking poll SCM for changes and
> adding an empty schedule. As our developer count has grown we've noticed a
> slow increase in backlog, and it seems to be that while there is a build
> the git plugin won't be poll for changes. When the build finishes it'll
> poll fine.
>
> It's set up to only build from branches with a certain prefix - is that
> what's preventing concurrent polling?
>
>
Unfortunately, no, building branches with a certain prefix is not what
blocks git plugin polling (on a specific job) while the job is running.
https://issues.jenkins-ci.org/browse/JENKINS-25304 indicates that if there
is a wildcard in the branch to be built, then polling will block on that
job until the job completes.

Mark Waite


> Patrick Rose
>
> --
> 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/94e91126-b500-4de6-9a60-79bce3e20e9e%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/CAO49JtGuH1-CUN7gKekfsvW6_gxgtTnx2gxfHUtop7_evctTmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Git plugin polling

2016-10-05 Thread prose

Our git server is set up to notify our jenkins instance whenever a commit 
was received by using cURL by saying checking poll SCM for changes and 
adding an empty schedule. As our developer count has grown we've noticed a 
slow increase in backlog, and it seems to be that while there is a build 
the git plugin won't be poll for changes. When the build finishes it'll 
poll fine.

It's set up to only build from branches with a certain prefix - is that 
what's preventing concurrent polling?

Patrick Rose

-- 
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/94e91126-b500-4de6-9a60-79bce3e20e9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to limited user to certain jobs

2016-10-05 Thread Mark Bidewell

The Role Strategy plugin might be more what you are looking for for Access 
Control

https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin


On Wednesday, October 5, 2016 at 5:27:43 AM UTC-4, stanle...@servicemax.com 
wrote:
>
> Hello, all
>
> I am trying to limited some user to access certain jobs, and cannot see 
> other jobs which are not related to them.
>
> I am using the "Project-based Matrix Authorization Strategy" to access 
> control, and it seems I cannot get what I want by this.
> Also I try to create user view, but which is not shown by default to that 
> user too.
>
> I tried to look at plugins, but it seems I didn't find a proper one.
>
> Anyone has met the same problem and how did you configure it?
>
>
> Thanks in advance.
>
> Thanks,
> Stanley
>
>

-- 
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/bec477c6-4068-4072-8ce5-f40a2c7153ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to limited user to certain jobs

2016-10-05 Thread Indra Gunawan (ingunawa)

Try this ownership plugin  : 
https://wiki.jenkins-ci.org/display/JENKINS/Ownership+Plugin


From: 
mailto:jenkinsci-users@googlegroups.com>> on 
behalf of "stanley.s...@servicemax.com" 
mailto:stanley.s...@servicemax.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Wednesday, October 5, 2016 at 2:27 AM
To: Jenkins Users 
mailto:jenkinsci-users@googlegroups.com>>
Subject: How to limited user to certain jobs

Hello, all

I am trying to limited some user to access certain jobs, and cannot see other 
jobs which are not related to them.

I am using the "Project-based Matrix Authorization Strategy" to access control, 
and it seems I cannot get what I want by this.
Also I try to create user view, but which is not shown by default to that user 
too.

I tried to look at plugins, but it seems I didn't find a proper one.

Anyone has met the same problem and how did you configure it?


Thanks in advance.

Thanks,
Stanley


--
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/6026b142-0209-465a-8605-9d2ce779feae%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/D41A52B3.5E0CA%25ingunawa%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Re: Creating groovy script to configure slave node properties >> "Restrict jobs execution at node"

2016-10-05 Thread Amit Ghatwal

Hi Indra,

Got it working with the below changes to my groovy script . Copying the 
updated script for benefit of others

import jenkins.model.*
import hudson.model.*
import hudson.slaves.*
import hudson.plugins.sshslaves.*

import com.synopsys.arc.jenkinsci.plugins.jobrestrictions.nodes.
JobRestrictionProperty;
import com.synopsys.arc.jenkinsci.plugins.jobrestrictions.restrictions.job.
StartedByUserRestriction;
import com.synopsys.arc.jenkinsci.plugins.jobrestrictions.util.UserSelector;
import java.util.List;

List usersList;

UserSelector  u1 = new UserSelector ("user1");
List userlist = new LinkedList();
userlist.add(u1);

StartedByUserRestriction startuserrect = new StartedByUserRestriction(
userlist, false, false,false );

JobRestrictionProperty jobrestrict = new JobRestrictionProperty(
startuserrect);

List restrictlist = new LinkedList();
restrictlist.add(jobrestrict);


  Slave slave = new DumbSlave(
"agent-node",
"Agent node description",
"/home/jenkins",
"1",
Node.Mode.NORMAL,
"agent-node-label",
new SSHLauncher("172.17.1.55",22,"root","root","","","",
"",""),
new RetentionStrategy.Always(),
restrictlist)
  Jenkins.instance.addNode(slave)


Thanks for all the guidance and pointing out the detailed steps.

Thanks and regards,
Amit


On Wednesday, 5 October 2016 12:04:11 UTC+5:30, Amit Ghatwal wrote:
>
> Hi Indra ,
>
> You've have hit the nail on its head , you have perfectly summarized my 
> requirements and precisely what i intent to achieve via a groovy script.
>
> import jenkins.model.*
> import hudson.model.*
> import hudson.slaves.*
> import hudson.plugins.sshslaves.*
> import java.util.ArrayList;
> import hudson.slaves.EnvironmentVariablesNodeProperty.Entry;
>
>
> import com.synopsys.arc.jenkinsci.plugins.jobrestrictions.nodes.
> JobRestrictionProperty; 
>
> import com.synopsys.arc.jenkinsci.plugins.jobrestrictions.Messages;
> import com.synopsys.arc.jenkinsci.plugins.jobrestrictions.restrictions.
> JobRestriction;
> import com.synopsys.arc.jenkinsci.plugins.jobrestrictions.restrictions.
> JobRestrictionBlockageCause;
> import hudson.Extension;
> import hudson.model.Node;
> import hudson.model.Queue;
> import hudson.model.queue.CauseOfBlockage;
> import hudson.slaves.NodeProperty;
> import hudson.slaves.NodePropertyDescriptor;
> import org.kohsuke.stapler.DataBoundConstructor;
>
>   List env = new ArrayList();
>   env.add(new Entry("key1","value1"))
>   env.add(new Entry("key2","value2"))
>   EnvironmentVariablesNodeProperty envPro = new 
> EnvironmentVariablesNodeProperty(env);
>   Slave slave = new DumbSlave(
> "agent-node","Agent node description",
> "/home/jenkins",
> "1",
> Node.Mode.NORMAL,
> "agent-node-label",
> new SSHLauncher("agenNode",22,"user","password","","",
> "","",""),
> new RetentionStrategy.Always(),
> new LinkedList())
>   slave.getNodeProperties().add(envPro)
>   Jenkins.instance.addNode(slave)
>
> I am actually kind of new to "groovy" , if u don't mind , as referred by 
> you in above points : 1,2,3,4,5 is perfectly what i need , but if you could 
> help in editing above groovy code to incorporate the points 1-5 as 
> mentioned by you would be helpful.
>
> Appreciate your time and help.
> Thanks and regards,
> Amit
>
> On Wednesday, 5 October 2016 11:12:23 UTC+5:30, Indra Gunawan (ingunawa) 
> wrote:
>>
>> Hi Amit,
>>
>> The 
>> https://github.com/jenkinsci/job-restrictions-plugin/blob/master/src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/nodes/JobRestrictionProperty.java
>>  class 
>> clearly extends NodeProperty.
>> 1. You need to instantiate a new JobRestrictionProperty class giving to 
>> it a new instance of jobRestriction class.
>>
>> 2. You are saying you want to Restrict jobs execution at node just for 
>> User?   Do you want to configure “Started by User”?
>> I assume you do, therefore you then browse to 
>> https://github.com/jenkinsci/job-restrictions-plugin/blob/master/src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction.java
>> This class extends AbstractUserCauseRestriction which extends 
>> jobRestriction so this class is a subclass of JobRestriction.
>> You need to instantiate a new StartedByUserRestriction class giving it : 
>>  (list of UserSelector, false, false, false).  <==  I presume you just want 
>> the list of users able to run job on the node, with no Upstream Job started 
>> by user or AutoRun or started by Anonymous User.
>>
>> 3. You pass in “StartedByUserRestriction" class created when you 
>> instantiate the new “JobRestrictionProperty" class.
>>
>> 4. Then you create a new LinkList and you add the JobRestrictionProperty 
>> class ins

How to limited user to certain jobs

2016-10-05 Thread stanley . shen

Hello, all

I am trying to limited some user to access certain jobs, and cannot see 
other jobs which are not related to them.

I am using the "Project-based Matrix Authorization Strategy" to access 
control, and it seems I cannot get what I want by this.
Also I try to create user view, but which is not shown by default to that 
user too.

I tried to look at plugins, but it seems I didn't find a proper one.

Anyone has met the same problem and how did you configure it?


Thanks in advance.

Thanks,
Stanley

-- 
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/6026b142-0209-465a-8605-9d2ce779feae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Passwordless SSH using LSF-cloud

2016-10-05 Thread Thomas Dack

So we recently set up a new Jenkins instance implemented onto our LSF batch 
system, and we are currently trying to set it up so that it can submit jobs 
to the queue. As Jenkins exists within the batch system itself we'd ideally 
like to do this without giving the Jenkins user a password, as it only 
needs to SSH into itself, preferably either having it not require a 
password at all or use a key pair. At current the LSF-cloud plugin requires 
a password and we cannot see a way to use it without one without modifying 
the plugin itself. Does anyone have any pointers of other things to try or 
will it be a case of modifying the plugin?

Cheers,

Tom

-- 
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/2c5a41e1-b5b9-4d17-97b9-ede7c2aa95c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Did the Jenkins version numbers just change?

Re: special Characters significance

Re: Secure Jenkins and mutlibranch github pipeline trigger

Config.xml of the job gets lost/deleted randomnly on jenkins restart or saving the configuration after changing it

triggering jenkins downstream project as per my parameter selection

Re: Updating jenkins version in docker image cause exit 143

Re: Updating jenkins version in docker image cause exit 143

AWS CodeDeploy Plugin Credentials Access Key/Secret Key set to Jenkins Admin U/P

Update jenkins version in a docker container

Re: Updating jenkins version in docker image cause exit 143

Re: Updating jenkins version in docker image cause exit 143

Updating jenkins version in docker image cause exit 143

Re: Did the Jenkins version numbers just change?

Re: Git plugin polling

Git plugin polling

Re: How to limited user to certain jobs

Re: How to limited user to certain jobs

Re: Creating groovy script to configure slave node properties >> "Restrict jobs execution at node"

How to limited user to certain jobs

Passwordless SSH using LSF-cloud

20 matches

Site Navigation

Mail list logo

Footer information