Gerrit Trigger Password Troubles

[Justin Fehr]

Hi all. Disclaimer, Im new to Jenkins. Anyways I am trying to set up 
Jenkins with the Gerrit Trigger to run builds as patch sets are pushed to 
our gerrit server.  I go through the settings and set up the connection and 
test the connection. the connection is successful. Then I save my settings 
which takes me back to the gerrit trigger page. When I open the settings I 
just saved and test the connection it fails. When I re-enter the ssh 
keyfile password and test again it works. From my testing I can conclude 
that the problem is from saving it seems to be changing or corrupting the 
password. Similarly I am seeing the same issue with the rest api http 
password. I have tried this with 1.631 and 1.632 current core releases, as 
well as 1.625 of the LTS version. My gerrit trigger version is 2.16.0 any 
help would be greatly appreciated. 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/e2fd0ec4-ae71-47e3-adc1-53615096ae95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to get upstream/downstream job info using Groovy Scripts ?

[Baptiste Mathus]

Le 7 oct. 2015 8:36 AM, "Baptiste Mathus"  a écrit :
>
> Hi,
> This is going to be very simple if you have some general have knowledge.

Hum. F You Autocorrect. I meant "Java knowledge".

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

Not receiving emails from any builds

[Renuka Radhakrishnan]

Hello,

My Jenkins is running in GCE, I have set up email notification through 
SendGrid. Email notifications from builds were working fine until early 
this week. It stopped working after I restarted my Jenkins. Now the test 
email works, but I don't receive any emails from the builds. I am using the 
Extended email notification plugin. Has anyone seen this ? I looked at the 
Jenkins logs and don't see any error there.

Thanks,
Renuka.

-- 
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/4ce4dd69-1d23-46cd-829c-d4c84f599a07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not receiving emails from any builds

[Slide]

Can you enable debug mode in the global config and then see what appears in
the build log?

On Wed, Oct 7, 2015, 18:02 Renuka Radhakrishnan  wrote:

> Hello,
>
> My Jenkins is running in GCE, I have set up email notification through
> SendGrid. Email notifications from builds were working fine until early
> this week. It stopped working after I restarted my Jenkins. Now the test
> email works, but I don't receive any emails from the builds. I am using the
> Extended email notification plugin. Has anyone seen this ? I looked at the
> Jenkins logs and don't see any error there.
>
> Thanks,
> Renuka.
>
> --
> 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/4ce4dd69-1d23-46cd-829c-d4c84f599a07%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/CAPiUgVctcpKZ8Bx53pkBHOAXVyx5r232BHiy4LaaJoUUTDd3Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New stuff for Jenkins GUI

[Maciej Jaros]

Gus Reiber (2015-09-23 20:26):

Hey all,
   This likely isn't a news flash for most of you, but the Jenkins GUI 
isn't great, but what might be news is that there is an active effort 
to make it a lot better. As part of that effort, I will be pushing out 
content, showing prototypes, concepts, and the occasional critique of 
the current GUI. The goal of this media push by me is to get you to 
holler back and help steer the effort towards actual improvements that 
matter to real users.


Last JUC: https://www.youtube.com/watch?v=wIOD622KqlE


I like the direction set in the presentation, but it would great if you 
could work more on the configuration page of jobs. You can see how 
important it is just browsing through all the plugins that attempt to 
fix problem of changing job configurations (e.g. Job DSL plugin).


For me it would help a lot if I would be able to collapse build steps. 
The more complicated the job is the more steps there are and it becomes 
harder and harder to change its flow. Smart collapsing would allow to 
easily glance through the configuration and add new step in the middle 
of the process. I've made a proof-of-concept of this smart collapsing 
and attached it to this issue:

https://issues.jenkins-ci.org/browse/JENKINS-27484?filter=-2

Please have look and good luck :-). I know changing GUI of old software 
is always hard on many levels ;-).


Regards,
Nux.

--
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/5614E984.7070908%40mol.com.pl.
For more options, visit https://groups.google.com/d/optout.

Re: Simple Plugin Theme Store

[Oleg Nenashev]

+1 for the idea.

I would vote to use a GitHub organization as a repo. Related thread: 
https://mail.google.com/mail/u/0/#inbox/15040c942f2816bf

In such case I see the following advantages:

   - You get a "repository" out of the box including project README pages, 
   etc. => Minimal efforts
   - Each theme can be stored as a separate repository and maintained 
   individually.
   - Existing theme repositories may be easily forked
   - Snippets from GitHub may be used directly
  - You can present a list of Snippets in Simple Theme Plugin
  - You can use GitHub stars as a community rating for sorting
   - You can version themes using GitHub releases or Git tags tags
   
We could use the existing Jenkins CI org, but probably a new organization 
is better due to the indexing advantages.

Best regards,
Oleg

воскресенье, 27 сентября 2015 г., 14:55:42 UTC+3 пользователь Victor 
Martinez написал:
>
> Hi,
>
>  Actually I like that idea! I believe you could something similar to the 
> scriptler approach (
> https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin) which is 
> based on a particular central catalog:
>   - http://scriptlerweb.appspot.com/ (actually is not accessible anymore 
> for some reason)
>   - https://github.com/jenkinsci/jenkins-scripts/
>
>  But that's also true, as Baptiste mentioned, Jenkins community is 
> thinking to move forward to another 2.X version which might also affect the 
> UI. 
>
> Anyway, I like your idea so let's see what' the community think and 
> probably it's worth to ask in the Jenkins Development group too.
>
> Cheers
>
> On Sunday, 6 September 2015 18:38:10 UTC+2, Lewis England wrote:
>>
>> Hi everybody, 
>>
>> I'm a guy who loves customisation, and the Jenkins Simple Theme Plugin 
>> was a wonderful thing for me. 
>> I have been using it for a while and found out many wonderful things that 
>> I can tweak and theme.
>>
>> However, it has come to my attention that there is no central theme 
>> repository or theme catalogue for this plugin. 
>> This is where I feel I can step in, but I'd like to get an idea on 
>> interest.
>>
>> MY PLAN:
>>  - Create a database and interface for completed / WIP Jenkins Themes 
>> (names, descriptions, screenshots)
>>  - Allow users to upload to it (ZIP file with CSS, JS and other theme 
>> files)
>>  - Allow links back to the original source, guessing GitHub, for 
>> community contribution (and other classic GitHub uses)
>>  - Ratings, comments, tags and all the other standard stuff.
>>
>> REASON:
>> Jenkins is a highly versatile system and I'm sure that those who are 
>> installing the Simple Theme plugin are the kind of people who are not a fan 
>> of the default UI.
>> Also, I personally am not too keen on searching around the internet for 
>> theme ideas / source to get started with. 
>>
>> Please let me know who is interested in this idea / who would like to 
>> help out.
>>
>>

-- 
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/79c8a77a-271c-45e4-8727-bdf7af624548%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Simple Plugin Theme Store

[Oleg Nenashev]

Added jenkinsci-dev to Cc

среда, 7 октября 2015 г., 12:11:32 UTC+3 пользователь Oleg Nenashev написал:
>
> +1 for the idea.
>
> I would vote to use a GitHub organization as a repo. Related thread: 
> https://mail.google.com/mail/u/0/#inbox/15040c942f2816bf
>
> In such case I see the following advantages:
>
>- You get a "repository" out of the box including project README 
>pages, etc. => Minimal efforts
>- Each theme can be stored as a separate repository and maintained 
>individually.
>- Existing theme repositories may be easily forked
>- Snippets from GitHub may be used directly
>   - You can present a list of Snippets in Simple Theme Plugin
>   - You can use GitHub stars as a community rating for sorting
>- You can version themes using GitHub releases or Git tags tags
>
> We could use the existing Jenkins CI org, but probably a new organization 
> is better due to the indexing advantages.
>
> Best regards,
> Oleg
>
> воскресенье, 27 сентября 2015 г., 14:55:42 UTC+3 пользователь Victor 
> Martinez написал:
>>
>> Hi,
>>
>>  Actually I like that idea! I believe you could something similar to the 
>> scriptler approach (
>> https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin) which is 
>> based on a particular central catalog:
>>   - http://scriptlerweb.appspot.com/ (actually is not accessible anymore 
>> for some reason)
>>   - https://github.com/jenkinsci/jenkins-scripts/
>>
>>  But that's also true, as Baptiste mentioned, Jenkins community is 
>> thinking to move forward to another 2.X version which might also affect the 
>> UI. 
>>
>> Anyway, I like your idea so let's see what' the community think and 
>> probably it's worth to ask in the Jenkins Development group too.
>>
>> Cheers
>>
>> On Sunday, 6 September 2015 18:38:10 UTC+2, Lewis England wrote:
>>>
>>> Hi everybody, 
>>>
>>> I'm a guy who loves customisation, and the Jenkins Simple Theme Plugin 
>>> was a wonderful thing for me. 
>>> I have been using it for a while and found out many wonderful things 
>>> that I can tweak and theme.
>>>
>>> However, it has come to my attention that there is no central theme 
>>> repository or theme catalogue for this plugin. 
>>> This is where I feel I can step in, but I'd like to get an idea on 
>>> interest.
>>>
>>> MY PLAN:
>>>  - Create a database and interface for completed / WIP Jenkins Themes 
>>> (names, descriptions, screenshots)
>>>  - Allow users to upload to it (ZIP file with CSS, JS and other theme 
>>> files)
>>>  - Allow links back to the original source, guessing GitHub, for 
>>> community contribution (and other classic GitHub uses)
>>>  - Ratings, comments, tags and all the other standard stuff.
>>>
>>> REASON:
>>> Jenkins is a highly versatile system and I'm sure that those who are 
>>> installing the Simple Theme plugin are the kind of people who are not a fan 
>>> of the default UI.
>>> Also, I personally am not too keen on searching around the internet for 
>>> theme ideas / source to get started with. 
>>>
>>> Please let me know who is interested in this idea / who would like to 
>>> help out.
>>>
>>>

-- 
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/4aa89fc4-97c1-4283-9ffb-7d2fb666d537%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New stuff for Jenkins GUI

[Gus Reiber]

Awesome Maciej,
Yeah, a collapsible job config page is something I think is important
and attainable in a reasonable time window. It was my hope it could have
made the November LTS, but we didn't quite get there. I am excited to apply
your script and have a look.

On Wed, Oct 7, 2015 at 2:44 AM, Maciej Jaros  wrote:

> Gus Reiber (2015-09-23 20:26):
>
> Hey all,
>This likely isn't a news flash for most of you, but the Jenkins GUI
> isn't great, but what might be news is that there is an active effort to
> make it a lot better. As part of that effort, I will be pushing out
> content, showing prototypes, concepts, and the occasional critique of the
> current GUI. The goal of this media push by me is to get you to holler back
> and help steer the effort towards actual improvements that matter to real
> users.
>
> Last JUC: https://www.youtube.com/watch?v=wIOD622KqlE
>
>
> I like the direction set in the presentation, but it would great if you
> could work more on the configuration page of jobs. You can see how
> important it is just browsing through all the plugins that attempt to fix
> problem of changing job configurations (e.g. Job DSL plugin).
>
> For me it would help a lot if I would be able to collapse build steps. The
> more complicated the job is the more steps there are and it becomes harder
> and harder to change its flow. Smart collapsing would allow to easily
> glance through the configuration and add new step in the middle of the
> process. I've made a proof-of-concept of this smart collapsing and attached
> it to this issue:
> https://issues.jenkins-ci.org/browse/JENKINS-27484?filter=-2
>
> Please have look and good luck :-). I know changing GUI of old software is
> always hard on many levels ;-).
>
> Regards,
> Nux.
>
> --
> 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/IHUWQ47B9OA/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/5614E984.7070908%40mol.com.pl
> 
> .
>
> 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/CAOcHHXz%2BP_kFuZWPinD%3DGW-A76uGXPmyFkbwgA3%2BUscBNU3CRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: iframes no longer displayed after Jnekins upgrade (1.557)

[Jacqueline Taing]

Hi,

I have not gotten this to work with Xframe Filter Plugin.

For ALLOW-FROM, is this the domain of the URL for the iframe or something 
else? 

Thanks,
-jacqui

On Monday, April 7, 2014 at 3:15:38 AM UTC-7, pablaasmo wrote:
>
> On 07. april 2014 11:48, Glenn Halstead wrote: 
> > Hi folks, 
> > 
> > We upgraded Jenkins to version 1.557.  We were on 1.554 afaik.  I had 
> > html pages from job archives displayed in view using an iframe.  These 
> > are no longer displayed.  An example of the code I used in the view is 
> > below: 
> > 
> > #frame { width: 1200px; height: 650px; border: 0px; } 
> >  > 
> src="job/__TCHarvester_Summary_Report/lastSuccessfulBuild/artifact/JenkinsUtils/folders.summary.html">
>  
>
> > 
> > Has anyone else seen similar issues? 
> > 
>
> Hi, 
> we had the same issue. 
> For a solution that showed webpages from our Jenkins master in a frame, 
> we used the plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/XFrame+Filter+Plugin to 
> solve the problem. 
>
> On the config for the plugin we added 
> ALLOW-FROM http://server.that-requests.com/ 
>
> But we also have the problem where we have an iframe in the description 
> of a project at the Jenkins master. Which I guess is more in the same 
> problem that you have. 
>
> We have not solved that problem yet :-( 
>
> Per A. 
>
>
>
>
>

-- 
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/a9e73572-16c5-48d8-bd66-84a8b42fc13b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to get upstream/downstream job info using Groovy Scripts ?

[Baptiste Mathus]

Hi,
This is going to be very simple if you have some general have knowledge.

In the groovy script, start with something along Jenkins.instance.
getItem(yourJobName) that will return a job instance.

Then look through the public javadoc to find what you want.

Hope it'll get you started.

Cheers
Le 6 oct. 2015 6:17 PM, "Shafi ulla"  a écrit :

> Am looking for groovy script
> given the job name as input,
> output : to list its upstream or downstream jobs.
>
> Any suggestion on how to do this ?
>
> --
> 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/fd15dff5-e221-414c-a0c7-d63051892c93%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/CANWgJS7qXEMqCCuMP%2BzrO9%2Bp%2B%3DReVWTjNcYTDp0-wCtHgP2rzQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Using environment variable SVN_REVISION_n in a workflow build

[Peter Marcoen]

In my previous freestyle projects after checking out from multiple 
repositories I could use the environment variable ${SVN_REVISION_1} to get 
the revision number of the first repository.

If, however, I use the following groovy script in a workflow job, I get 
"null" back.
Am I doing something wrong here?

node('unix') {
checkout([$class: 'SubversionSCM', locations: [[local: 'dir1', remote: 
'http://subversion.xxx.com/svn/xxx/trunk']]])
checkout([$class: 'SubversionSCM', locations: [[local: 'dir2', remote: 
'http://subversion.xxx.com/svn/yyy/trunk']]])
sh "echo ${env.SVN_REVISION}" sh "echo ${env.SVN_REVISION_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/5250704e-82f0-4f7c-982a-08a50f760f84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New stuff for Jenkins GUI

[milki milk]

On Wednesday, October 7, 2015 at 8:04:01 AM UTC-7, Gus Reiber wrote:
>
> Awesome Maciej,
> Yeah, a collapsible job config page is something I think is important 
> and attainable in a reasonable time window. It was my hope it could have 
> made the November LTS, but we didn't quite get there. I am excited to apply 
> your script and have a look.
>

I don't like collapsible job configs if it means hiding even more 
information. I already have issues with all the 'Advanced' tabs from all 
the plugins. We have a lot of non-Jenkins-experts and more seasoned admins 
 that administer Jenkins jobs. And more often than not, jobs are 
misconfigured because they can't find options or don't realize there are 
default behaviours that were hidden under all these tabs.

I find myself looking at the documentation in Jenkins Job Builder and 
Jenkins Job DSL to find job/plugin configuration rather than trying to find 
out by clicking all the buttons and tabs to expand all the hidden options.

-milki

-- 
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/d43d3479-5cb1-4191-a4cd-7f475da36b6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Templates Plugin (Jenkins Enterprise)

[Brian Ray]

Aha. Got it.

On Tuesday, October 6, 2015 at 11:06:33 AM UTC-7, Daniel Beck wrote:
>
>
> On 06.10.2015, at 18:52, Brian Ray  
> wrote: 
>
> > Not to drag the thread off-topic, but could you elaborate on any 
> security issues with Job DSL? I experimented with it a while back, and 
> CloudBees is going to demo Job Templates to my shop in the near future, but 
> is there something that makes Job DSL inherently less secure-able than the 
> latter? 
> > 
> > For example, couldn't you just use project-based security to lock down 
> the Job DSL job that creates and updates the spawned jobs? 
>
> The problem is that a user with Job/Configure on a single freestyle job 
> can add a Job DSL build step there, and wreaks havoc on your instance.

-- 
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/291d4a1e-9f71-430c-9017-a5a85dad6871%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Test email broken

[Ashish Yadav]

I am currently using Jenkins version 1.596.1 and Mailer plugin version 1.15. I 
am not able to send any email. This was working prior to the upgrade. Now I am 
getting javax.mail.AuthenticationFailedException: 535 5.7.8 Error: 
authentication failed

-- 
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/D23AD62C.117C4%25ashish.yadav%40firemon.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins Console output

[Jayaprakash D B]

Hi,

This looks like there is a problem connecting to remote host using SSH..
Try connecting to remote host manually and check if you are able to
successfully connect and transfer files using SCP.

Thanks,
JP

On Tuesday 6 October 2015, GBANE FETIGUE  wrote:

>
> Hey guys
>
> I am having some issues after running this job is giving me this error. I
> am not a jenkins expert ; here is the output also i to debug with the
> option - but is it's not working. could someone help me
>
> Started by user Fetigue Gbane 
> Building on master in workspace 
> /var/lib/jenkins/jobs/server-dev-cs-com-server/workspace
> [workspace] $ /bin/bash /tmp/hudson1559079971890511064.sh
> ff8e897c828dfd304e210a893bc095df7a9158c4-2015-09-28_02-44-55--47
>
> PLAY [Deploy to com servers] 
> **
>
> GATHERING FACTS 
> ***
> fatal: [172.16.39.215] => SSH encountered an unknown error during the 
> connection. We recommend you re-run the command using -, which will 
> enable SSH debugging output to help diagnose the issue
>
> TASK: [nodejs_app | Put upstart script in place] 
> **
> FATAL: no hosts matched or all hosts have already failed -- aborting
>
>
> PLAY RECAP 
> 
>to retry, use: --limit 
> @/var/lib/jenkins/deploy_com_release_group.retry
>
> 172.16.39.215  : ok=0changed=0unreachable=1failed=0
>
> Build step 'Execute shell' marked build as failure
> Finished: FAILURE
>
>
> --
> 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/8a018838-43cd-4b30-92eb-33fa786b1296%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/CALFtzb1JRcos_zvEWeU2Wk9EhbU3TEKdXs5cX%2Be8uJuQBv2AVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

j_acegi_security_check login error

[Charles Choi]

I am using:
Jenkins ver. 1.609.3
Matrix Authorization Strategy Plugin 1.2 

I use Windows SG to control access.  I added a SG.  There is one user in 
the SG, he is not able to login and get error: 
http://:8080/j_acegi_security_check.
If I add him as individual user, he has access.

What is causing this issue?
It is a nightmare to manage just one user.

-- 
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/feded1f1-8925-40ec-955f-72a7635bf2ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.