RE: Email notification recipients are not saved

[Alex Earl]

Can you upload you global and job config XML files somewhere?

Sent from my Windows Phone
--
From: Antti Ollilainen
Sent: 5/20/2013 23:11
To: jenkinsci-users@googlegroups.com
Cc: Antti Ollilainen
Subject: Re: Email notification recipients are not saved

It's Jenkins 1.515 on Windows Server 2008, running standalone, started as a
service. The job type is a Maven 2/3 project. I am using environment
variables defined in Configure System --> Global Properties as the email
notification recipients. I've tried this with the latest Chrome and IE10.

On Tuesday, May 21, 2013 9:03:58 AM UTC+3, slide wrote:
>
> I don't know what "Build Settings" is, what type of job are you using?
> Free style? Maven? Something else? Also, can you remind me what version of
> Jenkins you are using?
>
> Sent from my Windows Phone
> --
> From: Antti Ollilainen
> Sent: 5/20/2013 22:39
> To: jenkins...@googlegroups.com 
> Subject: Re: Email notification recipients are not saved
>
> Thanks, that works for email-ext. But there's another problem with that:
> when I enter job configuration and save the project again the
>  element in the email-ext block in config.xml is emptied.
>
> However, I might have found a workaround: when I set BOTH "Build Settings"
> and a "Post-build action" "Email notification" with the same variable the
> config.xml  element value stays even when I edit and save the
> project again. Now the first one tries to send email to $VARIABLE but the
> second one gets the expansion right.
>
> The element in config.xml is the same for both: . Is it
> possible that there's a bug in Jenkins where one configuration element
> value overwrites the other?
>
> On Monday, May 20, 2013 5:17:11 PM UTC+3, slide wrote:
>>
>> For email-ext, you would use ${ENV, var="YOUR_VAR"}
>>
>> Sent from my Windows Phone
>> --
>> From: Antti Ollilainen
>> Sent: 5/20/2013 6:53
>> To: jenkins...@googlegroups.com
>> Subject: Email notification recipients are not saved
>>
>> Hi list,
>>
>> I'm having a problem with Jenkins not saving the notification email
>> recipients for a job.
>>
>> My setup: Jenkins 1.515 on Windows Server 2008, running standalone,
>> started as a service. The job type is a Maven 2/3 project. I am using
>> environment variables defined in Configure System --> Global Properties as
>> my email notification recipients. The browser I use is the latest Chrome
>> but the problem was same with IE10.
>>
>> There are two possibilities for specifying the repicipients in the job
>> configuration: a checkbox in "Build Settings" and adding a "Post-build
>> action" "Email notification".
>>
>> The Build Settings creates a  block in the job config.xml:
>> 
>>   
>> 
>>   $PROJECT1_MEMBERS
>>   false
>>   false
>>   true
>> 
>>   
>> 
>>
>> The "recipients" value IS saved correctly when using the Build Settings
>> checkbox but environment variables are not expanded. Console log shows:
>> 
>> Sending e-mails to: $PROJECT1_MEMBERS
>> Finished: FAILURE
>> 
>>
>> When an email is configured by adding a Post-build action a 
>> block is created in the config.xml:
>> 
>>   
>> 
>>   
>>   false
>>   false
>> 
>>   
>> 
>>
>> As you can see the  element is empty. Of course when running
>> a job no emails are sent...
>>
>> The email-ext plugin is even worse: the first time I add an "Editable
>> Email Notification" as a post-build action it does save the recipient in
>> its  element but the second time I edit the project the
>> recipients are lost... There was a bug for something similar in JIRA (
>> https://issues.jenkins-ci.org/browse/JENKINS-15442) but it's marked as
>> "cannot reproduce" and closed.
>>
>> Is there any way I can use an environment variable as the notification
>> email recipient list in Jenkins? This is currently working in our old
>> Hudson but I'm trying to migrate to Jenkins.
>>
>> Best regards,
>> Antti
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"J

Re: Email notification recipients are not saved

[Antti Ollilainen]

It's Jenkins 1.515 on Windows Server 2008, running standalone, started as a 
service. The job type is a Maven 2/3 project. I am using environment 
variables defined in Configure System --> Global Properties as the email 
notification recipients. I've tried this with the latest Chrome and IE10.

On Tuesday, May 21, 2013 9:03:58 AM UTC+3, slide wrote:
>
> I don't know what "Build Settings" is, what type of job are you using? 
> Free style? Maven? Something else? Also, can you remind me what version of 
> Jenkins you are using?
>
> Sent from my Windows Phone
> --
> From: Antti Ollilainen
> Sent: 5/20/2013 22:39
> To: jenkins...@googlegroups.com 
> Subject: Re: Email notification recipients are not saved
>
> Thanks, that works for email-ext. But there's another problem with that: 
> when I enter job configuration and save the project again the 
>  element in the email-ext block in config.xml is emptied.
>
> However, I might have found a workaround: when I set BOTH "Build Settings" 
> and a "Post-build action" "Email notification" with the same variable the 
> config.xml  element value stays even when I edit and save the 
> project again. Now the first one tries to send email to $VARIABLE but the 
> second one gets the expansion right.
>
> The element in config.xml is the same for both: . Is it 
> possible that there's a bug in Jenkins where one configuration element 
> value overwrites the other?
>
> On Monday, May 20, 2013 5:17:11 PM UTC+3, slide wrote:
>>
>> For email-ext, you would use ${ENV, var="YOUR_VAR"}
>>
>> Sent from my Windows Phone
>> --
>> From: Antti Ollilainen
>> Sent: 5/20/2013 6:53
>> To: jenkins...@googlegroups.com
>> Subject: Email notification recipients are not saved
>>
>> Hi list,
>>
>> I'm having a problem with Jenkins not saving the notification email 
>> recipients for a job.
>>
>> My setup: Jenkins 1.515 on Windows Server 2008, running standalone, 
>> started as a service. The job type is a Maven 2/3 project. I am using 
>> environment variables defined in Configure System --> Global Properties as 
>> my email notification recipients. The browser I use is the latest Chrome 
>> but the problem was same with IE10.
>>
>> There are two possibilities for specifying the repicipients in the job 
>> configuration: a checkbox in "Build Settings" and adding a "Post-build 
>> action" "Email notification".
>>
>> The Build Settings creates a  block in the job config.xml:
>> 
>>   
>> 
>>   $PROJECT1_MEMBERS
>>   false
>>   false
>>   true
>> 
>>   
>> 
>>
>> The "recipients" value IS saved correctly when using the Build Settings 
>> checkbox but environment variables are not expanded. Console log shows:
>> 
>> Sending e-mails to: $PROJECT1_MEMBERS
>> Finished: FAILURE
>> 
>>
>> When an email is configured by adding a Post-build action a  
>> block is created in the config.xml:
>> 
>>   
>> 
>>   
>>   false
>>   false
>> 
>>   
>> 
>>
>> As you can see the  element is empty. Of course when running 
>> a job no emails are sent...
>>
>> The email-ext plugin is even worse: the first time I add an "Editable 
>> Email Notification" as a post-build action it does save the recipient in 
>> its  element but the second time I edit the project the 
>> recipients are lost... There was a bug for something similar in JIRA (
>> https://issues.jenkins-ci.org/browse/JENKINS-15442) but it's marked as 
>> "cannot reproduce" and closed.
>>
>> Is there any way I can use an environment variable as the notification 
>> email recipient list in Jenkins? This is currently working in our old 
>> Hudson but I'm trying to migrate to Jenkins.
>>
>> Best regards,
>> Antti
>>
>> -- 
>> 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.
>> For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Email notification recipients are not saved

[Alex Earl]

I don't know what "Build Settings" is, what type of job are you using? Free
style? Maven? Something else? Also, can you remind me what version of
Jenkins you are using?

Sent from my Windows Phone
--
From: Antti Ollilainen
Sent: 5/20/2013 22:39
To: jenkinsci-users@googlegroups.com
Subject: Re: Email notification recipients are not saved

Thanks, that works for email-ext. But there's another problem with that:
when I enter job configuration and save the project again the
 element in the email-ext block in config.xml is emptied.

However, I might have found a workaround: when I set BOTH "Build Settings"
and a "Post-build action" "Email notification" with the same variable the
config.xml  element value stays even when I edit and save the
project again. Now the first one tries to send email to $VARIABLE but the
second one gets the expansion right.

The element in config.xml is the same for both: . Is it
possible that there's a bug in Jenkins where one configuration element
value overwrites the other?

On Monday, May 20, 2013 5:17:11 PM UTC+3, slide wrote:
>
> For email-ext, you would use ${ENV, var="YOUR_VAR"}
>
> Sent from my Windows Phone
> --
> From: Antti Ollilainen
> Sent: 5/20/2013 6:53
> To: jenkins...@googlegroups.com 
> Subject: Email notification recipients are not saved
>
> Hi list,
>
> I'm having a problem with Jenkins not saving the notification email
> recipients for a job.
>
> My setup: Jenkins 1.515 on Windows Server 2008, running standalone,
> started as a service. The job type is a Maven 2/3 project. I am using
> environment variables defined in Configure System --> Global Properties as
> my email notification recipients. The browser I use is the latest Chrome
> but the problem was same with IE10.
>
> There are two possibilities for specifying the repicipients in the job
> configuration: a checkbox in "Build Settings" and adding a "Post-build
> action" "Email notification".
>
> The Build Settings creates a  block in the job config.xml:
> 
>   
> 
>   $PROJECT1_MEMBERS
>   false
>   false
>   true
> 
>   
> 
>
> The "recipients" value IS saved correctly when using the Build Settings
> checkbox but environment variables are not expanded. Console log shows:
> 
> Sending e-mails to: $PROJECT1_MEMBERS
> Finished: FAILURE
> 
>
> When an email is configured by adding a Post-build action a 
> block is created in the config.xml:
> 
>   
> 
>   
>   false
>   false
> 
>   
> 
>
> As you can see the  element is empty. Of course when running a
> job no emails are sent...
>
> The email-ext plugin is even worse: the first time I add an "Editable
> Email Notification" as a post-build action it does save the recipient in
> its  element but the second time I edit the project the
> recipients are lost... There was a bug for something similar in JIRA (
> https://issues.jenkins-ci.org/browse/JENKINS-15442) but it's marked as
> "cannot reproduce" and closed.
>
> Is there any way I can use an environment variable as the notification
> email recipient list in Jenkins? This is currently working in our old
> Hudson but I'm trying to migrate to Jenkins.
>
> Best regards,
> Antti
>
> --
> 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 .
> For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

PATH being ignored on SLES 10 with Jenkins ver. 1.466.2

[rusty]

I am running into an interesting problem with jenkins on SLES 10.4.  I have 
two different python versions installed because I need python2.6 and not 
2.4 for portability reasons that are not important.
Obviosly, I set up path variables on the machine so that jenkins would 
build using python2.6 and not 2.4 I have set a node variable
PATH 
/usr/local/bin/python:/usr/local/bin/:$PATH:/usr/local/bin/python:/usr/local/bin/
I have set the .bashrc file
I have set the /etc/profile
yet the path returned, even after a machine restart,disconnect-reconnect or 
both, jenkins always returns the path...
PATH /usr/bin:/bin:/usr/sbin:/sbin
But running a simple job of :
import os
import sys
print sys.executable
print os.getenv("PATH", None)
print sys.path
import automate
Returns

*23:11:38* [sysn0t4] $ python /tmp/hudson3083762089535439523.py*23:11:38* 
/usr/local/bin/python*23:11:38* 
/usr/local/bin/python:/usr/local/bin/:/usr/local/bin/python:/usr/local/bin/:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin/python:/usr/local/bin/:/usr/local/bin/python:/usr/local/bin/*23:11:38*
 ['/tmp', '/usr/lib/python24.zip', '/usr/lib64/python2.4', 
'/usr/lib64/python2.4/plat-linux2', '/usr/lib64/python2.4/lib-tk', 
'/usr/lib64/python2.4/lib-dynload', '/usr/lib64/python2.4/site-packages',


What on earth is going on  acording to the path returned. 
/usr/local/bin/python (python2.6) should have been found first, but it 
isn't.  How do I insert python 2.6 onto the path correctly?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Email notification recipients are not saved

[Antti Ollilainen]

Thanks, that works for email-ext. But there's another problem with that: 
when I enter job configuration and save the project again the 
 element in the email-ext block in config.xml is emptied.

However, I might have found a workaround: when I set BOTH "Build Settings" 
and a "Post-build action" "Email notification" with the same variable the 
config.xml  element value stays even when I edit and save the 
project again. Now the first one tries to send email to $VARIABLE but the 
second one gets the expansion right.

The element in config.xml is the same for both: . Is it 
possible that there's a bug in Jenkins where one configuration element 
value overwrites the other?

On Monday, May 20, 2013 5:17:11 PM UTC+3, slide wrote:
>
> For email-ext, you would use ${ENV, var="YOUR_VAR"}
>
> Sent from my Windows Phone
> --
> From: Antti Ollilainen
> Sent: 5/20/2013 6:53
> To: jenkins...@googlegroups.com 
> Subject: Email notification recipients are not saved
>
> Hi list,
>
> I'm having a problem with Jenkins not saving the notification email 
> recipients for a job.
>
> My setup: Jenkins 1.515 on Windows Server 2008, running standalone, 
> started as a service. The job type is a Maven 2/3 project. I am using 
> environment variables defined in Configure System --> Global Properties as 
> my email notification recipients. The browser I use is the latest Chrome 
> but the problem was same with IE10.
>
> There are two possibilities for specifying the repicipients in the job 
> configuration: a checkbox in "Build Settings" and adding a "Post-build 
> action" "Email notification".
>
> The Build Settings creates a  block in the job config.xml:
> 
>   
> 
>   $PROJECT1_MEMBERS
>   false
>   false
>   true
> 
>   
> 
>
> The "recipients" value IS saved correctly when using the Build Settings 
> checkbox but environment variables are not expanded. Console log shows:
> 
> Sending e-mails to: $PROJECT1_MEMBERS
> Finished: FAILURE
> 
>
> When an email is configured by adding a Post-build action a  
> block is created in the config.xml:
> 
>   
> 
>   
>   false
>   false
> 
>   
> 
>
> As you can see the  element is empty. Of course when running a 
> job no emails are sent...
>
> The email-ext plugin is even worse: the first time I add an "Editable 
> Email Notification" as a post-build action it does save the recipient in 
> its  element but the second time I edit the project the 
> recipients are lost... There was a bug for something similar in JIRA (
> https://issues.jenkins-ci.org/browse/JENKINS-15442) but it's marked as 
> "cannot reproduce" and closed.
>
> Is there any way I can use an environment variable as the notification 
> email recipient list in Jenkins? This is currently working in our old 
> Hudson but I'm trying to migrate to Jenkins.
>
> Best regards,
> Antti
>
> -- 
> 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 .
> For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: SSH credentials on build slave

[Alex Grönholm]

21.05.2013 00:09, Chanda Unmack kirjoitti:




On Mon, May 20, 2013 at 12:38 PM, Alex Grönholm 
mailto:alex.gronh...@nextday.fi>> wrote:


20.05.2013 19:03, Chanda Unmack kirjoitti:

I had a similar situation with git - I found the best way to see
what's going on is to set up a test job that does a ssh -vvv to
the git server (Mercurial in your case)
That showed me which keys it was using and whether or not it
actually used the .ssh/config file

Apparently Mercurial uses TortoisePlink.exe for SSH connections.
I'm not quite sure where to put my mercurial.ini so it will be
used for Jenkins activities (the build slave service is running as
the "Local System account")


In my searches I found an article that showed the "Local System 
account" home directory to be in C:\Windows\SysWOW64\config\systemprofile
But, I also had set the Environment variables in the node definition 
to set the HOME variable to be c:\jenkins so that I could set the .ssh 
up there. Doing the ssh -vvv verified that it was using that directory 
and the key file within.
I did see pages on getting Plink ssh working, but didn't bookmark them 
as it didn't apply to me - I'm sure a quick search would turn those up


The problem seems to be that if anything goes wrong, tortoiseplink will 
try to display an error dialog, which in a headless environment causes 
it to silently hang.
Makes it really hard to diagnose. The furthest I got was running hg 
clone manually (using plink) but it just freezes completely after 
authenticating, no errors, nothing. I have no clue how to debug this 
now. Everything works smoothly when I do it manually from the command 
line, but not when done remotely by Jenkins. Adding -batch in the plink 
arguments didn't help either.



hth
chanda


On Sat, May 18, 2013 at 2:30 PM, Alex Grönholm
mailto:alex.gronh...@nextday.fi>> wrote:

I have a Jenkins installation on a Linux box and a Windows 7
build slave for building Windows-only projects. Trouble is, I
can't get the slave to check out the source repository with
Mercurial. It always hangs, possibly due to SSH waiting for
password input even though it's running in a headless
environment. I have the proper SSH key installed on the
master, but I don't think the slave can utilize it. What
would be the best approach to this problem?
-- 


--
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/E-bTVhv3dvY/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

Mass Jenkins job updates

[Bob Bick]

Hi,

We have many Jenkins jobs defined that were copied from a "template" Jenkins 
job. Now, I discovered that I'd like to add a new build step to most (not all) 
of the jobs.

There seems to be several ways to modify the jobs:

1)  Brute force - Edit each job by clicking the Jenkins "Job Configure" 
button for each job. (Yuck)

2)  Groovy Script Console - This has the downside that I could screw up the 
configurations if I have a bug in the groovy script.

3)  Job DSL Plugin

4)  Jenkins Enterprise Templates - Not really sure whether this can even be 
done.

5)  Manually edit config.xml files

6)  Other???

Before investing time in coming up with a solution, I would like to know how 
other people have addressed mass updates to Jenkins jobs; and what worked well 
(or not so well).

Any feedback/guidance would be much appreciated.

Thanks,

Bob

*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

How to check job status via jenkins-cli.jar on a slave and send it back to Jenkins Server ?

[Z W]

Hi All

We like to find the job status or exit status of the job run using
the jenkins-cli.jar on a distributed build environment with slaves.

How do we do that ?

Thank you.
Sincerely

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Tutorial: Jenkins Plugin to integrate Jenkins and Nexus Repository

[Izet Salihbegovic]

Hi Marcel

Great work on your explanations but I hit the snag.  Cant find one 
dependency anwhere.
Using Professional Edition, Version: 2.4.0-09
Here is what I dont have

org.sonatype.nexus
*nexus-custom-metadata-plugin-client*
1.0


On Monday, August 6, 2012 5:43:00 AM UTC-7, Marcel Birkner wrote:
>
> Hi,
>
> I was looking for a way to add some metadata to build artifacts after they 
> are deployed to Nexus / Artifactory. Since both tools offer a 
> metadata-plugin for the Pro Editions I decided to write my own Jenkins 
> Plugin that calls the Nexus REST API to add some metadata to the deployed 
> artifact. Turns out, writing Jenkins plugins is not that hard thanks to 
> some great documentation and the Maven hpi plugin that creates the project 
> skeleton.
>
> I wrote up my experience when developing the plugin and posted the project 
> on github. 
>
>
>- Jenkins - Nexus 
> Tutorial
>- Sourcecode on 
> Github
>
>
> I hope you find the article helpful in creating your own Jenkins plugins 
> in the future.
>
> Greetings,
> Marcel
>
>
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: SSH credentials on build slave

[Chanda Unmack]

On Mon, May 20, 2013 at 12:38 PM, Alex Grönholm wrote:

>  20.05.2013 19:03, Chanda Unmack kirjoitti:
>
> I had a similar situation with git - I found the best way to see what's
> going on is to set up a test job that does a ssh -vvv to the git server
> (Mercurial in your case)
> That showed me which keys it was using and whether or not it actually used
> the .ssh/config file
>
> Apparently Mercurial uses TortoisePlink.exe for SSH connections. I'm not
> quite sure where to put my mercurial.ini so it will be used for Jenkins
> activities (the build slave service is running as the "Local System
> account")
>

In my searches I found an article that showed the "Local System account"
home directory to be in C:\Windows\SysWOW64\config\systemprofile
But, I also had set the Environment variables in the node definition to set
the HOME variable to be c:\jenkins so that I could set the .ssh up there.
Doing the ssh -vvv verified that it was using that directory and the key
file within.
I did see pages on getting Plink ssh working, but didn't bookmark them as
it didn't apply to me - I'm sure a quick search would turn those up

 hth
> chanda
>
>
> On Sat, May 18, 2013 at 2:30 PM, Alex Grönholm 
> wrote:
>
>> I have a Jenkins installation on a Linux box and a Windows 7 build slave
>> for building Windows-only projects. Trouble is, I can't get the slave to
>> check out the source repository with Mercurial. It always hangs, possibly
>> due to SSH waiting for password input even though it's running in a
>> headless environment. I have the proper SSH key installed on the master,
>> but I don't think the slave can utilize it. What would be the best approach
>> to this problem?
>> --
>>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: SSH credentials on build slave

[Alex Grönholm]

20.05.2013 19:03, Chanda Unmack kirjoitti:
I had a similar situation with git - I found the best way to see 
what's going on is to set up a test job that does a ssh -vvv to the 
git server (Mercurial in your case)
That showed me which keys it was using and whether or not it actually 
used the .ssh/config file
Apparently Mercurial uses TortoisePlink.exe for SSH connections. I'm not 
quite sure where to put my mercurial.ini so it will be used for Jenkins 
activities (the build slave service is running as the "Local System 
account").


hth
chanda


On Sat, May 18, 2013 at 2:30 PM, Alex Grönholm 
mailto:alex.gronh...@nextday.fi>> wrote:


I have a Jenkins installation on a Linux box and a Windows 7 build
slave for building Windows-only projects. Trouble is, I can't get
the slave to check out the source repository with Mercurial. It
always hangs, possibly due to SSH waiting for password input even
though it's running in a headless environment. I have the proper
SSH key installed on the master, but I don't think the slave can
utilize it. What would be the best approach to this problem?
-- 
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
.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/E-bTVhv3dvY/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: SSH credentials on build slave

[Alex Grönholm]

20.05.2013 19:03, Chanda Unmack kirjoitti:
I had a similar situation with git - I found the best way to see 
what's going on is to set up a test job that does a ssh -vvv to the 
git server (Mercurial in your case)
That showed me which keys it was using and whether or not it actually 
used the .ssh/config file
Trouble is, I have not installed ssh, there is no "ssh" command on PATH, 
so I have no clue where mercurial gets its ssh from. Strangely, it still 
works if I enter the password when it asks for it!


hth
chanda


On Sat, May 18, 2013 at 2:30 PM, Alex Grönholm 
mailto:alex.gronh...@nextday.fi>> wrote:


I have a Jenkins installation on a Linux box and a Windows 7 build
slave for building Windows-only projects. Trouble is, I can't get
the slave to check out the source repository with Mercurial. It
always hangs, possibly due to SSH waiting for password input even
though it's running in a headless environment. I have the proper
SSH key installed on the master, but I don't think the slave can
utilize it. What would be the best approach to this problem?
-- 
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
.
For more options, visit https://groups.google.com/groups/opt_out.

--
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/E-bTVhv3dvY/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

How to set up Jenkins on Mac Pro with Parallels vm slaves?

[David Burson]

Hi,

I'm new to Jenkins (and to CI), and need to set up Jenkins on a beefy Mac 
Pro.  The plan is to use a dozen or so virtual machines as dedicated 
slaves.  We want a Subversion commit to trigger building on each of these 
vm's.  I believe I understand how to configure Jenkins and create the jobs 
to start when someone checks code into our Subversion repository, and 
stagger the Quiet periods for the jobs so they don't all start at once.

My question is:  on the build machine (Mac Pro running OS X Mountain Lion) 
do I have to use VirtualBox for the slaves, or can I just as easily use 
Parallels?  I can't figure out how to make Jenkins automatically start a 
Parallels vm, copy the artifacts to the master after the build is done, and 
finally stop the vm.

Thanks,
David

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: SSH credentials on build slave

[Chanda Unmack]

I had a similar situation with git - I found the best way to see what's
going on is to set up a test job that does a ssh -vvv to the git server
(Mercurial in your case)
That showed me which keys it was using and whether or not it actually used
the .ssh/config file

hth
chanda


On Sat, May 18, 2013 at 2:30 PM, Alex Grönholm wrote:

> I have a Jenkins installation on a Linux box and a Windows 7 build slave
> for building Windows-only projects. Trouble is, I can't get the slave to
> check out the source repository with Mercurial. It always hangs, possibly
> due to SSH waiting for password input even though it's running in a
> headless environment. I have the proper SSH key installed on the master,
> but I don't think the slave can utilize it. What would be the best approach
> to this problem?
>
> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Job Config History Plugin and Jenkins Enterprise from CloudBees

[teilo]

Hi Bob,

I am heavily using CB Enterprise plugins.  (Note Folders is not an 
enterprise plugin but one of the cloudbees free as-in-beer ones)

I have found most plugins now work.  Over the couple of years I have found 
some incompatabilities with plugins.

When I have previously found issues cloudbees have been pretty responsive 
in fixing the issue in the plugin (if its on their list[1]).

/James

[1] 
http://wiki.cloudbees.com/bin/download/Jenkins+Enterprise/WebHome/CertifiedPlugins.pdf

On Monday, 20 May 2013 16:30:12 UTC+1, Bob Bick wrote:
>
>  Hi,
>
>  
>
> We are using Jenkins Enterprise from CloudBees and have jobs contained 
> within CloudBees Folders.
>
>  
>
> The JobConfigHistory plugin ( 
> https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin ) works 
> fine for jobs that are at the root level; however, if the job is under a 
> CloudBees folder, the JobConfigHistory plugin does not work.
>
>  
>
> Has anyone else ran into this issue? Any workaround?
>
>  
>
> As a Jenkins newbie administrator, I am starting to re-think whether to 
> use Jenkins Enterprise CloudBees features since generic Jenkins plugins may 
> have issues.  Is that a valid concern? Are other Jenkins administrators 
> avoiding Jenkins Enterprise CloudBees features because some plugins may not 
> play well with CloudBees?
>
>  
>
> Any guidance on avoiding CloudBees features would be much appreciated.
>
>  
>
> Thanks,
>
>  
>
> Bob
>
>  
>  
>
> *** *** ***
> This message contains information which may be confidential and 
> privileged. Unless you are the addressee (or authorized to receive for the 
> addressee), you may not use, copy or disclose to anyone the message or any 
> information contained in the message. If you have received the message in 
> error,  please advise the sender by reply e-mail and delete the message.
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Job Config History Plugin and Jenkins Enterprise from CloudBees

[Bob Bick]

Hi,

We are using Jenkins Enterprise from CloudBees and have jobs contained within 
CloudBees Folders.

The JobConfigHistory plugin ( 
https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin ) works 
fine for jobs that are at the root level; however, if the job is under a 
CloudBees folder, the JobConfigHistory plugin does not work.

Has anyone else ran into this issue? Any workaround?

As a Jenkins newbie administrator, I am starting to re-think whether to use 
Jenkins Enterprise CloudBees features since generic Jenkins plugins may have 
issues.  Is that a valid concern? Are other Jenkins administrators avoiding 
Jenkins Enterprise CloudBees features because some plugins may not play well 
with CloudBees?

Any guidance on avoiding CloudBees features would be much appreciated.

Thanks,

Bob


*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Multiple Jenkins Instances, Single CIFS file system.

[Eric Krystof]

Mark, Rob, thanks for the insight.

It was all about the disk space, and for us it's not as cheap as we'd like. 
 We were able to procure a few extra hundred GB which helps.  It was more 
of a thought in case we couldn't.  Nevertheless, thanks for your replies, 
and, based on your responses, I'm glad we no longer need to go down this 
road as we'd run into the same issues you described.

Cheers,

Eric R. Krystof

On Monday, May 20, 2013 7:07:07 AM UTC-5, Mandeville, Rob wrote:
>
>  The other question is, what sort of horsepower do you need?  Are you 
> CPU-bound or I/O bound?  The setup that you describe will allow you to 
> leverage the CPU and memory of the slave systems, but if you’re I/O bound, 
> your jobs will all be waiting on the same disk platters.  I once had (not 
> even using Jenkins) four build and test servers all using the same NFS 
> directory (NFS like CIFS for Unix).  The build servers were fine, but the 
> NFS server was brought to its knees.
>
>  
>
> Your directory X scares me, or maybe I’m not reading it right.  Each slave 
> has its own unique “remote FS root”, so anything being done there will be 
> isolated from work on the other slaves.  By directory X, do you mean that 
> you want the master and slaves to all work on the same filesystem, or 
> literally the same directories?  If they’re all going to be working on the 
> same directories, then the jobs will interfere with each other and you’ll 
> have race conditions.  If you mean that they’re all using different 
> directories in the same filesystem, then just worry about being I/O bound.
>
>  
>
> --Rob
>
>  
>  
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Mark Waite
> *Sent:* Friday, May 17, 2013 11:51 PM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: Multiple Jenkins Instances, Single CIFS file system.
>  
>  
>  
> I think it could be made to work with enough exploring and experimenting, 
> but it seems to me like you're using something expensive (human time, 
> thought, planning, diagnosis) in order to conserve something that is 
> relatively inexpensive (hard drive capacity).  Why not just buy more hard 
> disc space, avoid the complexity and reduce the network traffic?
>  
>  
>  
> I think you're probably also sacrificing execution time in your desire to 
> save disc space.  In my case, execution time is the most critical aspect of 
> the Jenkins jobs, because we can only provide feedback to users as fast as 
> we can cycle through the jobs.
>  
>  
>  
> I'm sure there are cases where the trade-offs you're considering are 
> exactly the right trade-offs (for example, massive video production where 
> you cannot afford to have more than a single copy of the workspace, a 
> monster finite element analysis job where a single set of working files may 
> overwhelm your capacity, etc.).
>  
>  
>  
> Mark Waite
>  
>  
>--
>  
> *From:* Eric Krystof >
> *To:* jenkins...@googlegroups.com  
> *Sent:* Friday, May 17, 2013 7:07 PM
> *Subject:* Multiple Jenkins Instances, Single CIFS file system.
>  
>  
>  
> Discussing an interesting scenario with my tech lead at work today.  Might 
> try this out but was looking for any definitive remarks indicating we may 
> be trying to divide by zero.
>  
>  
>  
> We need to build up a few slaves since our single instance is becoming 
> overwhelmed.  The thought was that since this is entirely local 
> network-wise that we possibly try this:
>  
>  
>  
> Master system with all jobs and workspaces in directory X.
>  
>  
>  
> Slaves setup to mount X as CIFS to run their jobs on.
>  
>  
>  
> We need the horsepower, not the space, so we're trying not to waste it, 
> hence the CIFS idea (which could add to build time, which could be 
> acceptable).
>  
>  
>  
> So I'm wondering... is that too far off the rails?  Would we need to 
> segregate jobs to run only on certain slaves?  Does the shared mount bring 
> along issues of configurations being overwritten or not read properly by 
> each Jenkins instance?
>  
>  
>  
> Thanks for pondering.
>  
> -- 
> 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 .
> For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>  The information in this message is for the intended recipient(s) only 
> and may be the proprietary and/or confidential property of Litle & Co., 
> LLC, and thus protected from disclosure. If you are not the intended 
> recipient(s), or an e

Re: Pass exit variables to down stream jobs.

[C. Alex Roeber]

Yes and thank you.


On Fri, May 17, 2013 at 8:10 AM, Erick Dovale  wrote:

> Are you using the jenkins cloud formation plugin for this?
>
>
> On Thu, Feb 14, 2013 at 2:09 PM,  wrote:
>
>> and to any one else in the plugins list it is:
>> Jenkins Parameterized Trigger 
>> plugin
>>
>>
>> On Thursday, February 14, 2013 11:08:22 AM UTC-8, c.alex...@gmail.comwrote:
>>>
>>> OK, I did find it, so thank you to all for the support.
>>>
>>> On Thursday, February 14, 2013 10:40:12 AM UTC-8, c.alex...@gmail.comwrote:

 Thanks and yep it is not in the plugin list...
 So could some one send me a link to the ".hpi file to install a plugin
 from outside the central plugin repository"
 I do not want to compile it from source.

 On Thursday, February 14, 2013 10:22:39 AM UTC-8, William Soula wrote:
>
>  It's actually called Parameterized Trigger 
> Pluginnot
>  trigger parameterized builds.  If you can't see it then I don't know
> what to say, it should be there.  I already have it installed so I can't
> test if it is there or not.
>
> Will
>
> On 02/14/2013 11:03 AM, c.alex...@gmail.com wrote:
>
> Thank you,
> I think I found an issue:
> I have Jenkins ver. 1.501  which I just
> upgraded and I have updated my plugin list.
> I do not see that plugin.
>
> On Thursday, February 14, 2013 8:19:26 AM UTC-8, William Soula wrote:
>>
>> You could output the variables to a file and then use the trigger
>> parameterized builds plugin to trigger downstream jobs and add a 
>> parameter
>> from properties file section to pass the properties to the downstream
>> builds:
>>
>> https://wiki.jenkins-ci.org/**display/JENKINS/Parameterized+**
>> Trigger+Plugin
>>
>> Will
>>
>> On 02/13/2013 04:33 PM, c.alex...@gmail.com wrote:
>>
>> If this is a known item I apologize.
>> I am using the Jenkins system to build environments in AWS using
>> Cloud Formation templates.
>> I need to know how to take the CF outputs and pass them to the next
>> job.
>> Example:
>> Build a VPC, Subnet, etc.
>> Then pass the VPC, Subnet IDs in to the build frontend web server
>> CF template so they are created in the new Subnet and VPC.
>>
>>  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-use...@googlegroups.**com.
>> For more options, visit 
>> https://groups.google.com/**groups/opt_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.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> 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/7vI4bp7SBZw/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Later
Alex

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Email notification recipients are not saved

[Alex Earl]

For email-ext, you would use ${ENV, var="YOUR_VAR"}

Sent from my Windows Phone
--
From: Antti Ollilainen
Sent: 5/20/2013 6:53
To: jenkinsci-users@googlegroups.com
Subject: Email notification recipients are not saved

Hi list,

I'm having a problem with Jenkins not saving the notification email
recipients for a job.

My setup: Jenkins 1.515 on Windows Server 2008, running standalone, started
as a service. The job type is a Maven 2/3 project. I am using environment
variables defined in Configure System --> Global Properties as my email
notification recipients. The browser I use is the latest Chrome but the
problem was same with IE10.

There are two possibilities for specifying the repicipients in the job
configuration: a checkbox in "Build Settings" and adding a "Post-build
action" "Email notification".

The Build Settings creates a  block in the job config.xml:

  

  $PROJECT1_MEMBERS
  false
  false
  true

  


The "recipients" value IS saved correctly when using the Build Settings
checkbox but environment variables are not expanded. Console log shows:

Sending e-mails to: $PROJECT1_MEMBERS
Finished: FAILURE


When an email is configured by adding a Post-build action a 
block is created in the config.xml:

  

  
  false
  false

  


As you can see the  element is empty. Of course when running a
job no emails are sent...

The email-ext plugin is even worse: the first time I add an "Editable Email
Notification" as a post-build action it does save the recipient in its
 element but the second time I edit the project the
recipients are lost... There was a bug for something similar in JIRA (
https://issues.jenkins-ci.org/browse/JENKINS-15442) but it's marked as
"cannot reproduce" and closed.

Is there any way I can use an environment variable as the notification
email recipient list in Jenkins? This is currently working in our old
Hudson but I'm trying to migrate to Jenkins.

Best regards,
Antti

-- 
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.
For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

Email notification recipients are not saved

[Antti Ollilainen]

Hi list,

I'm having a problem with Jenkins not saving the notification email 
recipients for a job.

My setup: Jenkins 1.515 on Windows Server 2008, running standalone, started 
as a service. The job type is a Maven 2/3 project. I am using environment 
variables defined in Configure System --> Global Properties as my email 
notification recipients. The browser I use is the latest Chrome but the 
problem was same with IE10.

There are two possibilities for specifying the repicipients in the job 
configuration: a checkbox in "Build Settings" and adding a "Post-build 
action" "Email notification".

The Build Settings creates a  block in the job config.xml:

  

  $PROJECT1_MEMBERS
  false
  false
  true

  


The "recipients" value IS saved correctly when using the Build Settings 
checkbox but environment variables are not expanded. Console log shows:

Sending e-mails to: $PROJECT1_MEMBERS
Finished: FAILURE


When an email is configured by adding a Post-build action a  
block is created in the config.xml:

  

  
  false
  false

  


As you can see the  element is empty. Of course when running a 
job no emails are sent...

The email-ext plugin is even worse: the first time I add an "Editable Email 
Notification" as a post-build action it does save the recipient in its 
 element but the second time I edit the project the 
recipients are lost... There was a bug for something similar in JIRA (
https://issues.jenkins-ci.org/browse/JENKINS-15442) but it's marked as 
"cannot reproduce" and closed.

Is there any way I can use an environment variable as the notification 
email recipient list in Jenkins? This is currently working in our old 
Hudson but I'm trying to migrate to Jenkins.

Best regards,
Antti

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re:Git View inside jenkins

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

No, there is no such feature in Jenkins or its plugins, and it really would not 
belong there.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: May 20 2013 09:26:45

Hello guys! Is there any plugin which provides to view git repository in the 
jenkins web-interface?  So, I know about 'Git Plugin' functionality, but it 
provide only URLs to external git-view services. But I want to see git view 
inside jenkins page. Is it possible or not?-- View this message in context: 
http://jenkins.361315.n4.nabble.com/Git-View-inside-jenkins-tp488.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. For more options, 
visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

Git View inside jenkins

[legal90]

Hello guys!
Is there any plugin which provides to view git repository in the jenkins
web-interface?

So, I know about 'Git Plugin' functionality, but it provide only URLs to
external git-view services. But I want to see git view inside jenkins page.
Is it possible or not?



--
View this message in context: 
http://jenkins.361315.n4.nabble.com/Git-View-inside-jenkins-tp488.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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: m2 release plugin versioning policy

[James Nord (jnord)]

From: Hilikus [mailto:thehili...@gmail.com]
Sent: 17 May 2013 18:57
To: jenkinsci-users@googlegroups.com
Cc: James Nord (jnord)
Subject: Re: m2 release plugin versioning policy

when you say it will be coming back you mean what? being able to set a 
different version in the UI for each submodule

[JTN] Yes

or letting maven decide based on the SNAPSHOT version in the pom?

[JTN] if the issues with it can be worked out – and I think I have a plan.

or both?

[JTN] the individual one first, if the plan for using maven works, then using 
maven will be done after (or possibly at the same time).


How complex are the changes?

For the prompt the user – not very, it’s a buncy of Jelly config and moving 
some parameters around (and checking that no new modules have been introduced 
since the last build)

could someone without jenkins plugin experience do it in a couple of days?

[JTN] I would think so – the code did exist and was removed – so there is 
already some guidance on how to do this.

it sounds to me like just a matter of constructing the correct command line 
invocation

[JTN] that’s the easy bit (assuming you’re not on windows and don’t blow the 
command line argument length!).  You need to store the variables in a the 
Action and get them from the post, and have the UI prompt for them.

On Friday, 17 May 2013 12:02:06 UTC-4, James Nord (jnord) wrote:
If you require that functionality you will need to downgrade to an earlier 
version (I think 0.7.1).

The functionality will be coming back but I have no current ETA.
See https://issues.jenkins-ci.org/browse/JENKINS-11466

/James

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Hilikus
Sent: 17 May 2013 16:50
To: jenkins...@googlegroups.com
Subject: m2 release plugin versioning policy

Hello everyone,

It looks like the current behaviour when doing a maven release from jenkins in 
a multi-module project is to assign the version specified in the web ui of 
jenkins to ALL the submodules

e.g in a project like this

1.0.0-SNAPSHOT  (A)
   |...1.0.0-SNAPSHOT (A1)
   |...2.3.0-SNAPSHOT (A2)

if I specify in the ui that the version of the root pom (A in my example) 
should be 1.0.0 then even the second submodule (2.3.0-SNAPSHOT) will be 
released with version 1.0.0, probably due to the -B -DreleaseVersion arguments 
combo. Is there any way to change this behaviour? what I want is to release 
A1=1.0.0, A2=1.0.0 and A3=2.3.0

I see a "default versioning mode" in the configuration that seems to do just 
that; however, 1) it never keeps its state, whatever I change it to, it goes 
back to none 2) it doesn't even look like the actual behaviour is none, since 
none seems to be what I want. The behaviour I see is "specify one version for 
all modules"

I'm using m2release 0.10 and jenkins 1.460


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-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Multiple Jenkins Instances, Single CIFS file system.

[Mandeville, Rob]

The other question is, what sort of horsepower do you need?  Are you CPU-bound 
or I/O bound?  The setup that you describe will allow you to leverage the CPU 
and memory of the slave systems, but if you're I/O bound, your jobs will all be 
waiting on the same disk platters.  I once had (not even using Jenkins) four 
build and test servers all using the same NFS directory (NFS like CIFS for 
Unix).  The build servers were fine, but the NFS server was brought to its 
knees.

Your directory X scares me, or maybe I'm not reading it right.  Each slave has 
its own unique "remote FS root", so anything being done there will be isolated 
from work on the other slaves.  By directory X, do you mean that you want the 
master and slaves to all work on the same filesystem, or literally the same 
directories?  If they're all going to be working on the same directories, then 
the jobs will interfere with each other and you'll have race conditions.  If 
you mean that they're all using different directories in the same filesystem, 
then just worry about being I/O bound.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Friday, May 17, 2013 11:51 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Multiple Jenkins Instances, Single CIFS file system.

I think it could be made to work with enough exploring and experimenting, but 
it seems to me like you're using something expensive (human time, thought, 
planning, diagnosis) in order to conserve something that is relatively 
inexpensive (hard drive capacity).  Why not just buy more hard disc space, 
avoid the complexity and reduce the network traffic?

I think you're probably also sacrificing execution time in your desire to save 
disc space.  In my case, execution time is the most critical aspect of the 
Jenkins jobs, because we can only provide feedback to users as fast as we can 
cycle through the jobs.

I'm sure there are cases where the trade-offs you're considering are exactly 
the right trade-offs (for example, massive video production where you cannot 
afford to have more than a single copy of the workspace, a monster finite 
element analysis job where a single set of working files may overwhelm your 
capacity, etc.).

Mark Waite


From: Eric Krystof mailto:erkrys...@gmail.com>>
To: jenkinsci-users@googlegroups.com
Sent: Friday, May 17, 2013 7:07 PM
Subject: Multiple Jenkins Instances, Single CIFS file system.

Discussing an interesting scenario with my tech lead at work today.  Might try 
this out but was looking for any definitive remarks indicating we may be trying 
to divide by zero.

We need to build up a few slaves since our single instance is becoming 
overwhelmed.  The thought was that since this is entirely local network-wise 
that we possibly try this:

Master system with all jobs and workspaces in directory X.

Slaves setup to mount X as CIFS to run their jobs on.

We need the horsepower, not the space, so we're trying not to waste it, hence 
the CIFS idea (which could add to build time, which could be acceptable).

So I'm wondering... is that too far off the rails?  Would we need to segregate 
jobs to run only on certain slaves?  Does the shared mount bring along issues 
of configurations being overwritten or not read properly by each Jenkins 
instance?

Thanks for pondering.
--
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.
For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
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

Jenkins JIRA and non-closed issues

[Rade Martinović]

Hi all,

I have noticed that there are HUMONGOUS number of issues in Jenkins JIRA 
that are resolved but not closed - try this JQL - 

> status != Closed AND resolution != EMPTY ORDER BY updated ASC, key DESC


I think that it would be much in line with JIRA workflow to close all 
verified and released issue. It's a big job but it would improve statistics 
from the public dashboard (two dimensional stats).

Best,
-- Rade 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.