Re: Generating parallel flow with Build Flow Plugin
On 16 Jan 2014, at 19:15, Rodrigo García Peláez rodrigogarciapel...@gmail.com
wrote:
Any ideas?
When I run sequentially the GENERIC_DEPLOYMENT job quickly I get the job to
run twice in parallel. The quite period is 0 for this job. But when I do it
from the Build Flow job below it runs them sequentially
Thanks
Rodrigo
Hi,
In order to make your jobs run parallel you need to split them into different
blocks.
E.g.:
parallel (
{
build( “GENERIC_DEPLOYMENT )
},
{
build( “BACKEND_BUILD_TAG:params[BACKEND_BUILD_TAG] )
},
{
build( “BACKEND_SERVER:it) )
}
)
Regards,
Tom De Vylder
--
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: jvm crash...a fatal error. had been detected. ..exception. access violation...server restart. and jenkins. server remains. offline. until manually restarted. through. launch web start
Hi Abc, The format of your message makes it very difficult to read and understand, so it will likely be ignored (remember, we're volunteers on this list). If you want people to help, you need to describe your problem in a way that makes it easy for people to read and understand. The English grammar does not have to be perfect, but you do need to write your thoughts in a logical and clear order. Please repost your questions, and try putting one statement per line. You might also provide some more background. Was this working before? Is this the first time you have run with this JVM version? Matthew -Original Message- From: Abc [mailto:kgpa...@gmail.com] Sent: 17 January 2014 01:25 To: jenkinsci-users@googlegroups.com Subject: jvm crash...a fatal error. had been detected. ..exception. access violation...server restart. and jenkins. server remains. offline. until manually restarted. through. launch web start We have windows. 7machine. 8gb..we launch jenkins. Server using java jdk 1.7 update 45...during the build the jvm crash. Occurs with different plugins and server restarts ...then in jenkins it shows that server is offline.. .we have other servers too but they are not having this issue. ..once the server restarts unless manually I go and restart the jenkins server it remains offline...why is the problem occuring with this server.. .other servers too use java jdk1.7 update 45 to start jenkins server...by they are not going down due to jvm crash. ..how shall I solve this issue. ..please help...there are other applications also running on this server..thanks in advance -- -- 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 get last stable build number through groovy script ?
I am able to get the current build number currentBuildNumber = manager.build.number How to get the lastStableBuild, lastFaledBuildNumber ? Thanks, M -- 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.
Nunit multiple report files
Hello We are using Jenkins to build a Delphi Job. This Job builds an x64 and x86 Tests.exe. Both of them excecute fine and also generate a seperate dunit-report.xml and dunit-report-x64.xml file. If we insert only one of these two files into the Publish NUnit test result report Plugin everything works fine. But if we insert both of them only one is used. No matter how we insert them into the Publish NUnit test result report Plugin. I have tried: **/*report*.xml **/*.xml dunit-report.xml,dunit-report-x64.xml *.xml Every time only one of the two reports is used. Are we doing antyhing wrong? Are we expecting the wrong result? We want to get a second Test Result at the Job Dashboard, so one can see both testresults. Thanks for your help! Regards Matthias -- 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: How to get last stable build number through groovy script ?
For Freestyle jobs at least, it's manager.build.parent.lastStableBuild.number and manager.build.parent.lastFailedBuild.number. Note that this only works like this in Groovy Postbuild Plugin, which has no relation to Groovy Plugin. On 17.01.2014, at 10:56, Maneesh M P maneesh.po...@gmail.com wrote: I am able to get the current build number currentBuildNumber = manager.build.number How to get the lastStableBuild, lastFaledBuildNumber ? Thanks, M -- 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: how to change email address in all job configuration [Email Ext plugin]
You'd have yo get the configured triggers and iterate over them as well.
On Jan 16, 2014 6:16 PM, Maneesh M P maneesh.po...@gmail.com wrote:
I was able to use the below script to iterate through email address, but
the problem is even this doesn't display addresses in the trigger
import hudson.plugins.emailext.*
import hudson.model.*
import hudson.maven.*
import hudson.maven.reporters.*
import hudson.tasks.*
// For each project
for(item in Hudson.instance.items) {
println(JOB : +item.name);
// Find current recipients defined in project
if(!(item instanceof ExternalJob)) {
if(item instanceof MavenModuleSet) {
println(MAVEN MODULE SET);
// Search for Maven Mailer Reporter
println(Reporters);
for(reporter in item.reporters) {
if(reporter instanceof MavenMailer) {
println( reporter : +reporter+ : +reporter.recipients);
}
}
} else
if(item instanceof FreeStyleProject) {
println(FREESTYLE PROJECT);
}
println(Publishers);
for(publisher in item.publishersList) {
// Search for default Mailer Publisher (doesn't exist for Maven
projects)
if(publisher instanceof Mailer) {
println( publisher : +publisher+ : +publisher.recipients);
} else
// Or for Extended Email Publisher
if(publisher instanceof ExtendedEmailPublisher) {
println( publisher : +publisher+ : +publisher.recipientList);
}
}
} else {
println(External Jobs cannot have MailNotificationsRecipients)
}
println(\n===\n);
}
Thanks,
Maneesh
On Thursday, January 16, 2014 5:11:50 PM UTC-8, slide wrote:
The easiest way is to use the script console. You need to iterate through
your projects, get the publisher list, find the email-ext publisher and
then modify the properties you need to for the recipient.
On Jan 16, 2014 4:29 PM, Maneesh M P manees...@gmail.com wrote:
Configure slicing plugin does not display the address specified inside
email triggers
Thanks,
Maneesh
On Thursday, January 16, 2014 3:15:58 PM UTC-8, Daniel Beck wrote:
Configuration Slicing plugin *might* work.
On 17.01.2014, at 00:09, Maneesh M P manees...@gmail.com wrote:
I have more than 300+ jobs configured in my jenkins and I am using
email ext plugin to configure the mail trigger. currently i am in a
situation where I have to change one recipient mail address to something
else
Is there an easy way to do it?
Thanks,
M
--
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
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: Securely obtain the Jenkins package and public key
On Thu, Jan 16, 2014 at 09:33:34AM -0800, Kohsuke Kawaguchi wrote: On 01/16/2014 06:19 AM, Marius Gedminas wrote: What about packaging? The Debian packages available from upstream start the web server on the public IP right from the post-inst script, before you get a chance to set up any security. This allows remote code execution as user jenkins. (The Jenkins package in the Ubuntu archive is configured to start the web server on localhost only, which sounds like a sane mitigation strategy for me.) Yeah, this is a good idea. I filed https://issues.jenkins-ci.org/browse/JENKINS-21417 for this. Perhaps a slight variation of it is to keep listening to these ports like we do today but to show the message saying non-local access is blocked until you acknowledge what you are doing? That way, it would work across platforms and it's less confusing to those who are less experienced in the system administration? Something like that can be packaged as a plugin, which makes the integration process easy --- you can just go create code yourself and other people can try/use it, and we'd only have to bundle it in the core. Hm. Yes, a page explaining what to do would be more user-friendly. E.g. it could tell the admin how to use SSH port-forwarding to connect to the Jenkins and get full access to the configuration pages, or what config files to edit to set a password. (I'm not volunteering to implement this. My familiarity with Java ended with a brief university course in 2000.) Should I file a bug? (I have filed a few bugs about packaging issues (one involving data loss), but haven't seen any response at all after many months, which made me stop caring. I have some small expertise with Debian packaging, and I'm willing to post patches, if I think they will not be silently ignored for months.) OK, our apologies. Do you know which ones they are? We want to take a look. https://issues.jenkins-ci.org/browse/JENKINS-18797 and https://issues.jenkins-ci.org/browse/JENKINS-18798 were the most annoying, with the 1st one clobbering my configuration (luckily, I had a backup). https://issues.jenkins-ci.org/browse/JENKINS-19329 is related to 18798. Perhaps I picked the wrong component? It was the only one that mentioned Debian packaging. Marius Gedminas -- 6 out of 7 dwarves are not Happy. signature.asc Description: Digital signature
JUnit skipped tests NOT appearing in main report columns but appear in packages reports columns
Hi. In our team we are getting JUnit test results reports with Jenkins plugin. But we only get skipped tests (the ones with the Java annotation with @Ignore) at the package level. For the main report result window, we only get Fail and Total. Check these images: *Main Test Result Report* You can see there are 138 skipped tests, but no one is shown at package level in the columns. Only Fail and Total columns are shown: https://lh4.googleusercontent.com/-QI43LNXB3ss/Utkd934LRSI/A5M/3y_LUpuFQhc/s1600/testReportMainWindow.jpg *Package Test Result Report* At the package level, skipped tests are shown indeed in the columns: Failed, Skip and Total https://lh3.googleusercontent.com/-B-F-EbDUaTw/UtkeP5vyjzI/A5U/f_6Sq4unXS0/s1600/testReportPkgWindow.jpg Is it possible to see the Skip column in the Main Test Result Report? Thanks in advance, Tomas. -- 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.
SimpleClearCase-Plugin with Jenkins
Hello all, After having installed this plug-in (SimpleClearCase-Plugin) to integrate Jenkins with UCM Clearcase and to poll the SCM for any changes, I am not sure what values are to be filled in for these options displayed in the job setup. I have referred this URL https://wiki.jenkins-ci.org/display/JENKINS/SimpleClearCase-Plugin Load Rule: Where are the load rules defined in Clearcase and where can we find the appropriate vales? What value should go in here. View Name: I hope this is the View (Dynamic view name in my case) which needs to be polled associated with the Integration stream where final tested changes would be delivered. Branch Name to watch: What value should go in here? Appreciate your valuable inputs (maybe with some mock example as this pertains to the values for a setup which may differ in all cases). Thank You T.S -- 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.
Build Flow causes all executors dead while executing the job
Hi , I am using a build flow plugin to execute sequential jobs But when i execute the master job build flow it runs some of the jobs and suddenly all the threads die giving the below error java.lang.NullPointerException at hudson.model.ParametersAction.getAssignedLabel(ParametersAction.java:128) at hudson.model.Queue$Item.getAssignedLabel(Queue.java:1450) at hudson.model.Node.canTake(Node.java:324) at hudson.model.Queue$JobOffer.canTake(Queue.java:272) at hudson.model.Queue.maintain(Queue.java:1099) at hudson.model.Queue.pop(Queue.java:935) at hudson.model.Executor.grabJob(Executor.java:298) at hudson.model.Executor.run(Executor.java:212) even after restarting the thread nothing happens. Please help Thanks in advance tushanka -- 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.
What exactly is 'response time'?
Hi The 'Manage nodes' page of our Jenkins installation shows widely different response time for our slaves, ranging from 31ms to 12s. The figure at the top of the column is 17min. Our master and most slaves run Linux. All run on an internal network. What exactly does 'response time' indicate in this context? Is 12s something to worry about? What does the top figure (17mins) indicate? Thanks in advance. 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: What exactly is 'response time'?
Hi Stephen Yes, some are VMs. David From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly Sent: 17 January 2014 14:32 To: jenkinsci-users@googlegroups.com Subject: Re: What exactly is 'response time'? Its the time the last ping packet took to route through the remoting layer. 12s does sound a bit bad... the ping may have hit the node when busy archiving artifacts or during a GC pause... or are some of your slaves VMs? On 17 January 2014 14:12, David Aldrich david.aldr...@emea.nec.commailto:david.aldr...@emea.nec.com wrote: Hi The 'Manage nodes' page of our Jenkins installation shows widely different response time for our slaves, ranging from 31ms to 12s. The figure at the top of the column is 17min. Our master and most slaves run Linux. All run on an internal network. What exactly does 'response time' indicate in this context? Is 12s something to worry about? What does the top figure (17mins) indicate? Thanks in advance. 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.commailto:jenkinsci-users%2bunsubscr...@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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. Click herehttps://www.mailcontrol.com/sr/17WGJKyatI3GX2PQPOmvUndZP90azNGYHx!pR6KkiTXWRIPfFQdwYFcJOQNTrtToqA0QORD0PH8KIUtpuCToCg== to report this email as spam. -- 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: What exactly is 'response time'?
Hi Pinging the slave from the master's command line consistently gives a response time of 160ms, as opposed to 12s. BR David From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly Sent: 17 January 2014 14:32 To: jenkinsci-users@googlegroups.com Subject: Re: What exactly is 'response time'? Its the time the last ping packet took to route through the remoting layer. 12s does sound a bit bad... the ping may have hit the node when busy archiving artifacts or during a GC pause... or are some of your slaves VMs? On 17 January 2014 14:12, David Aldrich david.aldr...@emea.nec.commailto:david.aldr...@emea.nec.com wrote: Hi The 'Manage nodes' page of our Jenkins installation shows widely different response time for our slaves, ranging from 31ms to 12s. The figure at the top of the column is 17min. Our master and most slaves run Linux. All run on an internal network. What exactly does 'response time' indicate in this context? Is 12s something to worry about? What does the top figure (17mins) indicate? Thanks in advance. 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.commailto:jenkinsci-users%2bunsubscr...@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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. Click herehttps://www.mailcontrol.com/sr/17WGJKyatI3GX2PQPOmvUndZP90azNGYHx!pR6KkiTXWRIPfFQdwYFcJOQNTrtToqA0QORD0PH8KIUtpuCToCg== to report this email as spam. -- 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: LTS 1.532.2 release date
when it is ready On 17 January 2014 14:39, Guillaume Boucherie guillaume.bouche...@gmail.com wrote: Hi, When did you plan to release version 1.532.2 of Jenkins ? Version 1.532.1 has some really annoying bug. 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. 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: What exactly is 'response time'?
This is a ping through the remoting layer, i.e. how long it takes jenkins to send a simple command there and back. On 17 January 2014 14:36, David Aldrich david.aldr...@emea.nec.com wrote: Hi Pinging the slave from the master’s command line consistently gives a response time of 160ms, as opposed to 12s. BR David *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Stephen Connolly *Sent:* 17 January 2014 14:32 *To:* jenkinsci-users@googlegroups.com *Subject:* Re: What exactly is 'response time'? Its the time the last ping packet took to route through the remoting layer. 12s does sound a bit bad... the ping may have hit the node when busy archiving artifacts or during a GC pause... or are some of your slaves VMs? On 17 January 2014 14:12, David Aldrich david.aldr...@emea.nec.com wrote: Hi The ‘Manage nodes’ page of our Jenkins installation shows widely different response time for our slaves, ranging from 31ms to 12s. The figure at the top of the column is 17min. Our master and most slaves run Linux. All run on an internal network. What exactly does ‘response time’ indicate in this context? Is 12s something to worry about? What does the top figure (17mins) indicate? Thanks in advance. 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. -- 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. Click herehttps://www.mailcontrol.com/sr/17WGJKyatI3GX2PQPOmvUndZP90azNGYHx!pR6KkiTXWRIPfFQdwYFcJOQNTrtToqA0QORD0PH8KIUtpuCToCg==to report this email as spam. -- 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: What exactly is 'response time'?
Then a couple of seconds might not be critical, rather indicative of a poorly resourced VM at the time the ping was measured. If the same slave is consistently showing poor ping times when idle... that would indicate a potential issue On 17 January 2014 14:32, David Aldrich david.aldr...@emea.nec.com wrote: Hi Stephen Yes, some are VMs. David *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Stephen Connolly *Sent:* 17 January 2014 14:32 *To:* jenkinsci-users@googlegroups.com *Subject:* Re: What exactly is 'response time'? Its the time the last ping packet took to route through the remoting layer. 12s does sound a bit bad... the ping may have hit the node when busy archiving artifacts or during a GC pause... or are some of your slaves VMs? On 17 January 2014 14:12, David Aldrich david.aldr...@emea.nec.com wrote: Hi The ‘Manage nodes’ page of our Jenkins installation shows widely different response time for our slaves, ranging from 31ms to 12s. The figure at the top of the column is 17min. Our master and most slaves run Linux. All run on an internal network. What exactly does ‘response time’ indicate in this context? Is 12s something to worry about? What does the top figure (17mins) indicate? Thanks in advance. 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. -- 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. Click herehttps://www.mailcontrol.com/sr/17WGJKyatI3GX2PQPOmvUndZP90azNGYHx!pR6KkiTXWRIPfFQdwYFcJOQNTrtToqA0QORD0PH8KIUtpuCToCg==to report this email as spam. -- 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.
LTS 1.532.2 release date
Hi, When did you plan to release version 1.532.2 of Jenkins ? Version 1.532.1 has some really annoying bug. 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: What exactly is 'response time'?
Its the time the last ping packet took to route through the remoting layer. 12s does sound a bit bad... the ping may have hit the node when busy archiving artifacts or during a GC pause... or are some of your slaves VMs? On 17 January 2014 14:12, David Aldrich david.aldr...@emea.nec.com wrote: Hi The ‘Manage nodes’ page of our Jenkins installation shows widely different response time for our slaves, ranging from 31ms to 12s. The figure at the top of the column is 17min. Our master and most slaves run Linux. All run on an internal network. What exactly does ‘response time’ indicate in this context? Is 12s something to worry about? What does the top figure (17mins) indicate? Thanks in advance. 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. -- 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 not sent by jenkins
Hi the issue was with System Admin E-mail Address , I put correct user now I can receive mails using debug was not that helpful see below output before fixing the issue , couldn't trace out what was the issue Checking if email needs to be generated Email was triggered for: Always Sending email for trigger: Always NOT overriding default server settings, using Mailer to create session messageContentType = text/plain; charset=UTF-8 Adding recipients from recipient list Successfully created MimeMessage Sending email to: xx...@xxx.com -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/not-able-to-send-email-using-jenkins-jobs-tp4686607p4687634.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.
REST API for promoting builds
I read a lot of people talking about the REST API for build promotion, but I can't find any documentation on it. What is the URL/API for forcing a job promotion? -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/REST-API-for-promoting-builds-tp4687670.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: What exactly is 'response time'?
Hi David, 160ms for a ping seems rather high. Are the master/slave in different continents? VM to VM (hosted on different co-located physical machine) I am getting sub millisecond. rtt min/avg/max/mdev = 0.172/0.434/0.844/0.278 ms /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich Sent: 17 January 2014 14:37 To: jenkinsci-users@googlegroups.com Subject: RE: What exactly is 'response time'? Hi Pinging the slave from the master's command line consistently gives a response time of 160ms, as opposed to 12s. BR David From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly Sent: 17 January 2014 14:32 To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Subject: Re: What exactly is 'response time'? Its the time the last ping packet took to route through the remoting layer. 12s does sound a bit bad... the ping may have hit the node when busy archiving artifacts or during a GC pause... or are some of your slaves VMs? On 17 January 2014 14:12, David Aldrich david.aldr...@emea.nec.commailto:david.aldr...@emea.nec.com wrote: Hi The 'Manage nodes' page of our Jenkins installation shows widely different response time for our slaves, ranging from 31ms to 12s. The figure at the top of the column is 17min. Our master and most slaves run Linux. All run on an internal network. What exactly does 'response time' indicate in this context? Is 12s something to worry about? What does the top figure (17mins) indicate? Thanks in advance. 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.commailto:jenkinsci-users%2bunsubscr...@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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. Click herehttps://www.mailcontrol.com/sr/17WGJKyatI3GX2PQPOmvUndZP90azNGYHx!pR6KkiTXWRIPfFQdwYFcJOQNTrtToqA0QORD0PH8KIUtpuCToCg== to report this email as spam. -- 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.commailto: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.
Managing maven credentials on a shared build server
Hi, Are there any known best practices for managing credentials for maven on a shared build server? Only way I see it is to have store them in a workspace in custom setting xml, but for that users should be able to upload the file from somewhere. And only option is to get it from version control system. Which is not really working, maven credentials should be separated for snapshots and releases repositories. E.g different persons make builds and other prepare releases. Obviosly it's not applicable if credentials are stored in the same repository. Rephrasing it: is there a way to separate maven credentials per job while manage it somewhere on jenkins? There is a plugin credential-store that provides a nice interface for managing password. But again, this is for global definitions. --Roman ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. -- 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: Generating parallel flow with Build Flow Plugin
Hi,
Thanks for your response.
My problem is that I'm trying to build it dynamically depending on the
parameters. I can receive a list of servers to deploy to so I want to run
the job to deploy to each server in parallel. That list of servers can be
different every time, as it's passed manually with an extended choice
parameter, triggered manually.
Any ideas of how I can achieve that?
Thanks and regards
Rodrigo
On Friday, 17 January 2014 09:05:47 UTC, TomDV wrote:
On 16 Jan 2014, at 19:15, Rodrigo García Peláez
rodrigoga...@gmail.comjavascript:
wrote:
Any ideas?
When I run sequentially the GENERIC_DEPLOYMENT job quickly I get the job
to run twice in parallel. The quite period is 0 for this job. But when I do
it from the Build Flow job below it runs them sequentially
Thanks
Rodrigo
Hi,
In order to make your jobs run parallel you need to split them into
different blocks.
E.g.:
parallel (
{
build( “GENERIC_DEPLOYMENT )
},
{
build( “BACKEND_BUILD_TAG:params[BACKEND_BUILD_TAG] )
},
{
build( “BACKEND_SERVER:it) )
}
)
Regards,
Tom De Vylder
--
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: A way to get rid of useless local workspace?
Thank you so much for your explanation! It seems now easy to define a new slave, trigger svn update on it with SCM poll, and execute the Ant script from that location. Don't need even my Ant remote task anymore with jenkins slave agent... On Thursday, January 16, 2014 10:05:12 PM UTC+1, LesMikesell wrote: My builds are all done on slaves and even though the master controls the SCM polling, it does not check out any source locally on the master. However, with usual setup, the slave checks out a copy of the target the job is configure to poll before executing anything in the job.So I don't understand how you avoid that - or why you want to avoid it and make your own ant script do the slave checkout. And I think whatever it is you are doing is making the master do the checkout instead of the slave. On Thu, Jan 16, 2014 at 8:18 AM, kgiloo gilles...@gmail.com javascript: wrote: Sorry, i did not get your point... What do you mean exactly? On Thursday, January 16, 2014 5:31:05 AM UTC+1, LesMikesell wrote: On Wed, Jan 15, 2014 at 2:42 AM, kgiloo gilles...@gmail.com wrote: probably my description lacked precision: I should have titled A way to get rid of useless checkout of repository into my local workspace. I do not use any special slave configuration to trigger my builds on slaves, it is all driven by Ant. In other words, checkout of repository is also performed by Ant on slave. I need the poll SCM to kick off the build process, for nothing else, i.e checkout of repository in workspace has no sense on my master. Why do it that way? Why not include the ant script in the checkout and let jenkins do it in the right place for you? -- Les Mikesell lesmi...@gmail.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: jenkins warnings plugin pclint linux
I would suggest that you pipe the output of the pclint command through a small script that removes the Z: from the filenames. (Or you can use a custom parser that basically does the same as the pclint parser and remove the Z: prefix there) Ulli Am 15.01.2014 um 15:51 schrieb Stijn stijn.deroovanma...@gmail.com: Hi, I'm using pclint together with jenkins warnings plugin on linux. However, pclint is a windows executable executed by wine. Therefore, the output of pclint is something like Z:\media\Data\workspace\pr_7315\app\common\logging\src\logger.c(91): Note 956: Non const, non volatile static or external variable 'log_parse_succeeded' Z: doesn't exist on a linux system, so Z: should be the \ path instead. The warnings plugin gives following error: 01 Copying the source file 'Z:/media/Data/workspace/pr_7315/app/drivers/io/src/io_rm_7358.c' from the workspace to the build folder '/var/lib/jenkins/jobs/pr_7315/builds/2014-01-15_14-50-21/workspace-files/aa97a26a.tmp' on the Jenkins master failed. 02 Is the file 'Z:/media/Data/workspace/pr_7315/app/drivers/io/src/io_rm_7358.c' a valid filename? 03 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]/Z:/media/Data/workspace/pr_7315/app/drivers/io/src/io_rm_7358.c' 04 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace/Z:/media/Data/workspace/pr_7315/app/drivers/io/src/io_rm_7358.c' 05 java.io.FileNotFoundException: Z:/media/Data/workspace/pr_7315/app/drivers/io/src/io_rm_7358.c (No such file or directory) 06 at java.io.FileInputStream.open(Native Method) 07 at java.io.FileInputStream.init(FileInputStream.java:137) 08 at hudson.FilePath$37.invoke(FilePath.java:1814) 09 at hudson.FilePath$37.invoke(FilePath.java:1809) 10 at hudson.FilePath.act(FilePath.java:914) 11 at hudson.FilePath.act(FilePath.java:887) 12 at hudson.FilePath.copyTo(FilePath.java:1809) 13 at hudson.plugins.analysis.core.HealthAwareRecorder.copyFilesWithAnnotationsToBuildFolder(HealthAwareRecorder.java:398) 14 at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:334) 15 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) 16 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 17 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 18 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) 19 at hudson.model.Build$BuildExecution.post2(Build.java:183) 20 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 21 at hudson.model.Run.execute(Run.java:1703) 22 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 23 at hudson.model.ResourceController.execute(ResourceController.java:88) 24 at hudson.model.Executor.run(Executor.java:231) Any idea how to solve this? KR, Stijn. -- 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. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: jenkins warnings plugin pclint linux
On Wednesday, January 15, 2014 9:51:25 AM UTC-5, Stijn wrote: Hi, I'm using pclint together with jenkins warnings plugin on linux. However, pclint is a windows executable executed by wine. Therefore, the output of pclint is something like Z:\media\Data\workspace\pr_7315\app\common\logging\src\logger.c(91): Note 956: Non const, non volatile static or external variable 'log_parse_succeeded' Z: doesn't exist on a linux system, so Z: should be the \ path instead. It's pretty perverse to run a Windows lint on Wine. Why not just use a native lint? If you must use a Windows executable under Wine, the included winepath utility can help you convert paths. -- 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.
Jenkins global env vars stuck for some slave jobs
Hi all,
We've been trying to use Jenkins global env vars to define the svn URL to use
for some of our builds. While this seemed to work when we tested it earlier,
now that we're trying to set the env var back from a release branch to the
trunk, the value of the env var seems stuck for some build jobs.
Our Machintosh full build has the old idea of the env var while our Windows
full build sees the new, correct env var value. Both of these jobs are run on
build slaves, not the Jenkins server. We're using Jenkins ver. 1.482.
Here's more details:
This is the env var is set in Configure System - Global properties -
Environment variables
name: FULL_BUILD_TRUNK_TO_USE
value: trunk
I've hacked our problematic Mac build job script to output what it thinks is
the value of this env var, then purposely error to stop the job. I've also
tried defining test env vars from the global one in the job itself and via the
env inject plugin as a test.
For the injected env var test, I've defined the following:
Build Environment - Inject environment variables to the build process -
Properties Content
INJECTED_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
For the build job env var test, I've defined the following:
Build Environment - Set environment variables
BUILD_ENV_VAR_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
Here's the hacked test build job script:
--snip--
#!/bin/sh
echo This is a hack to see what this build job thinks the build env var is set
to.
echo FULL_BUILD_TRUNK_TO_USE = ${FULL_BUILD_TRUNK_TO_USE}
echo INJECTED_TRUNK_TO_USE = ${INJECTED_TRUNK_TO_USE}
echo BUILD_ENV_VAR_TRUNK_TO_USE = ${BUILD_ENV_VAR_TRUNK_TO_USE}
exit 1
--snip--
In all cases, the above script code outputs the old branch value of
FULL_BUILD_TRUNK_TO_USE, not the new trunk value set in the global config:
--snip--
[EnvInject] - Executing scripts and injecting environment variables after the
SCM step.
[EnvInject] - Injecting as environment variables the properties content
INJECTED_TRUNK_TO_USE=branches/RB-2.3.1
[EnvInject] - Variables injected successfully.
[ClientMacFull] $ /bin/sh
/var/folders/uu/uu50uc60HNO7gmdeMNxMEE+++TI/-Tmp-/hudson2189251323725654867.sh
This is a hack to see what this build job thinks the build env var is set to.
FULL_BUILD_TRUNK_TO_USE = branches/RB-2.3.1
INJECTED_TRUNK_TO_USE = branches/RB-2.3.1
BUILD_ENV_VAR_TRUNK_TO_USE = branches/RB-2.3.1
--snip--
What's odd is that the Windows build does not have the same problem. However
one difference with that build is that the global env var is used directly in
the svn URL settings of that job, whereas the Mac build manually calls svn
directly from the script using the env var itself to build the URL. So the Mac
build script directly accesses the env var in the script and the Windows build
does not.
Any ideas as to what's wrong and how I can get this to work?
Thanks in advance for any suggestions.
Best,
Allen Cronce
--
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: Send over ftp only changed scm files
Hi, Can you share what you did with me, I look for the same think you describe in your post, send just changed files in svn! Thank you in advance :) On Tuesday, June 12, 2012 8:46:40 PM UTC+1, Eduardo Rodrigues wrote: Rob, Your answer make me think in oder possibilities.Thank you Roy 2012/6/12 Mandeville, Rob rmand...@litle.com javascript: That's an odd mode, I don't think Jenkins would support this. I'm guessing that the problem is that svn isn't running on the machine you want the files on. I'm in a unix shop, so I can handle this with a command called rsync. The rsync algorithm automagically figures out what changed and only transfers that. If that's not an option, make a job based on svn that gets a list of files younger than a certain time (such as the last time it was run), archive those files, and use the FTP publisher plugin. Of course, this is all off the top of my head, so don't bet the company on this without doing some serious testing. I've found from hard experience that pushing out deltas rather than replacing the whole tree is dangerous. Sure, it can handle changes to individual files, but what about new files, files that have been deleted from the source tree, or (my un-favorite) renamed files? --Rob -Original Message- From: jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] On Behalf Of Roy Sent: Tuesday, June 12, 2012 2:31 PM To: Jenkins Users Subject: Re: Send over ftp only changed scm files I have jenkins installed in a server and create a job that every commit in svn I want to send changed files over ftp, Maybe what i need is some plugin that copy svn changed files to a temp dir after that I can send this files over ftp. Now can you understand? Thank you Roy On Jun 12, 3:16 pm, Brian J. Murrell br...@interlinx.bc.ca wrote: On 12-06-12 02:10 PM, Roy wrote: There are some way to do that? I'm trying to do find some plugin or solution since yesterday. Can someone help me? I don't know about anyone else but I don't think I really understand what it is you want. b. signature.asc 1KViewDownload 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. -- [image: DigitalBox.cc] *Eduardo Rodrigues Gomes(Roy)* *+55 11 8434-9021* *+55 11 2385-0560* eduardo.rodrig...@digitalbox.cc javascript: http://www.digitalbox.cc -- 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: Managing maven credentials on a shared build server
There is actually a layered set of credential stores... if you use the folders plugin (which as of version 4.0 is free as in Open Frickin Source) then you can tie credentials to within a specific folder. imod has been working on trying to integrate credentials into the maven settings.xml provider... but after we made him a committer over at Maven we've been keeping him busy with his OSS time ;-) On 17 January 2014 15:20, Naumenko, Roman roman.naume...@rbccm.com wrote: Hi, Are there any known best practices for managing credentials for maven on a shared build server? Only way I see it is to have store them in a workspace in custom setting xml, but for that users should be able to upload the file from somewhere. And only option is to get it from version control system. Which is not really working, maven credentials should be separated for snapshots and releases repositories. E.g different persons make builds and other prepare releases. Obviosly it's not applicable if credentials are stored in the same repository. Rephrasing it: is there a way to separate maven credentials per job while manage it somewhere on jenkins? There is a plugin credential-store that provides a nice interface for managing password. But again, this is for global definitions. --Roman ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. -- 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: How to get last stable build number through groovy script ?
Thank you!! I was looking for Post build plugin information only. I am curious know why is that different from groovy plugin? Also there a document available to find out these information of groovy post build plugin and groovy plugin? Thanks, Maneesh On Friday, January 17, 2014 2:25:07 AM UTC-8, Daniel Beck wrote: For Freestyle jobs at least, it's manager.build.parent.lastStableBuild.number and manager.build.parent.lastFailedBuild.number. Note that this only works like this in Groovy Postbuild Plugin, which has no relation to Groovy Plugin. On 17.01.2014, at 10:56, Maneesh M P manees...@gmail.com javascript: wrote: I am able to get the current build number currentBuildNumber = manager.build.number How to get the lastStableBuild, lastFaledBuildNumber ? Thanks, M -- 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 javascript:. 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: Jenkins global env vars stuck for some slave jobs
Try restarting your slaves. There was an issue with EnvInject where global
variable changes wouldn't propagate to the slave unless the slave was fully
disconnected and reconnected.
On Friday, January 17, 2014 8:19:34 AM UTC-8, Allen Cronce wrote:
Hi all,
We've been trying to use Jenkins global env vars to define the svn URL to
use for some of our builds. While this seemed to work when we tested it
earlier, now that we're trying to set the env var back from a release
branch to the trunk, the value of the env var seems stuck for some build
jobs.
Our Machintosh full build has the old idea of the env var while our
Windows full build sees the new, correct env var value. Both of these jobs
are run on build slaves, not the Jenkins server. We're using Jenkins ver.
1.482.
Here's more details:
This is the env var is set in Configure System - Global properties -
Environment variables
name: FULL_BUILD_TRUNK_TO_USE
value: trunk
I've hacked our problematic Mac build job script to output what it thinks
is the value of this env var, then purposely error to stop the job. I've
also tried defining test env vars from the global one in the job itself and
via the env inject plugin as a test.
For the injected env var test, I've defined the following:
Build Environment - Inject environment variables to the build process
- Properties Content
INJECTED_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
For the build job env var test, I've defined the following:
Build Environment - Set environment variables
BUILD_ENV_VAR_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
Here's the hacked test build job script:
--snip--
#!/bin/sh
echo This is a hack to see what this build job thinks the build env var
is set to.
echo FULL_BUILD_TRUNK_TO_USE = ${FULL_BUILD_TRUNK_TO_USE}
echo INJECTED_TRUNK_TO_USE = ${INJECTED_TRUNK_TO_USE}
echo BUILD_ENV_VAR_TRUNK_TO_USE = ${BUILD_ENV_VAR_TRUNK_TO_USE}
exit 1
--snip--
In all cases, the above script code outputs the old branch value
of FULL_BUILD_TRUNK_TO_USE, not the new trunk value set in the global
config:
--snip--
[EnvInject] - Executing scripts and injecting environment variables after
the SCM step.
[EnvInject] - Injecting as environment variables the properties content
INJECTED_TRUNK_TO_USE=branches/RB-2.3.1
[EnvInject] - Variables injected successfully.
[ClientMacFull] $ /bin/sh
/var/folders/uu/uu50uc60HNO7gmdeMNxMEE+++TI/-Tmp-/hudson2189251323725654867.sh
This is a hack to see what this build job thinks the build env var is set
to.
FULL_BUILD_TRUNK_TO_USE = branches/RB-2.3.1
INJECTED_TRUNK_TO_USE = branches/RB-2.3.1
BUILD_ENV_VAR_TRUNK_TO_USE = branches/RB-2.3.1
--snip--
What's odd is that the Windows build does not have the same problem.
However one difference with that build is that the global env var is used
directly in the svn URL settings of that job, whereas the Mac build
manually calls svn directly from the script using the env var itself to
build the URL. So the Mac build script directly accesses the env var in the
script and the Windows build does not.
Any ideas as to what's wrong and how I can get this to work?
Thanks in advance for any suggestions.
Best,
Allen Cronce
--
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: Jenkins global env vars stuck for some slave jobs
Thanks. I just tried that (before seeing your email). It worked. The build
slave now has the correct env var value.
I guess that we can reboot as a work around. We don't change back and forth
between the trunk and branches that often.
But is there a more permanent solution? Maybe the problem you mentioned has
been fixed in an update?
On Friday, January 17, 2014 9:47:52 AM UTC-8, Jason Swager wrote:
Try restarting your slaves. There was an issue with EnvInject where
global variable changes wouldn't propagate to the slave unless the slave
was fully disconnected and reconnected.
On Friday, January 17, 2014 8:19:34 AM UTC-8, Allen Cronce wrote:
Hi all,
We've been trying to use Jenkins global env vars to define the svn URL to
use for some of our builds. While this seemed to work when we tested it
earlier, now that we're trying to set the env var back from a release
branch to the trunk, the value of the env var seems stuck for some build
jobs.
Our Machintosh full build has the old idea of the env var while our
Windows full build sees the new, correct env var value. Both of these jobs
are run on build slaves, not the Jenkins server. We're using Jenkins ver.
1.482.
Here's more details:
This is the env var is set in Configure System - Global properties -
Environment variables
name: FULL_BUILD_TRUNK_TO_USE
value: trunk
I've hacked our problematic Mac build job script to output what it thinks
is the value of this env var, then purposely error to stop the job. I've
also tried defining test env vars from the global one in the job itself and
via the env inject plugin as a test.
For the injected env var test, I've defined the following:
Build Environment - Inject environment variables to the build process
- Properties Content
INJECTED_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
For the build job env var test, I've defined the following:
Build Environment - Set environment variables
BUILD_ENV_VAR_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
Here's the hacked test build job script:
--snip--
#!/bin/sh
echo This is a hack to see what this build job thinks the build env var
is set to.
echo FULL_BUILD_TRUNK_TO_USE = ${FULL_BUILD_TRUNK_TO_USE}
echo INJECTED_TRUNK_TO_USE = ${INJECTED_TRUNK_TO_USE}
echo BUILD_ENV_VAR_TRUNK_TO_USE = ${BUILD_ENV_VAR_TRUNK_TO_USE}
exit 1
--snip--
In all cases, the above script code outputs the old branch value
of FULL_BUILD_TRUNK_TO_USE, not the new trunk value set in the global
config:
--snip--
[EnvInject] - Executing scripts and injecting environment variables after
the SCM step.
[EnvInject] - Injecting as environment variables the properties content
INJECTED_TRUNK_TO_USE=branches/RB-2.3.1
[EnvInject] - Variables injected successfully.
[ClientMacFull] $ /bin/sh
/var/folders/uu/uu50uc60HNO7gmdeMNxMEE+++TI/-Tmp-/hudson2189251323725654867.sh
This is a hack to see what this build job thinks the build env var is set
to.
FULL_BUILD_TRUNK_TO_USE = branches/RB-2.3.1
INJECTED_TRUNK_TO_USE = branches/RB-2.3.1
BUILD_ENV_VAR_TRUNK_TO_USE = branches/RB-2.3.1
--snip--
What's odd is that the Windows build does not have the same problem.
However one difference with that build is that the global env var is used
directly in the svn URL settings of that job, whereas the Mac build
manually calls svn directly from the script using the env var itself to
build the URL. So the Mac build script directly accesses the env var in the
script and the Windows build does not.
Any ideas as to what's wrong and how I can get this to work?
Thanks in advance for any suggestions.
Best,
Allen Cronce
--
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: Logger to feature mapping
Thanks a lot Daniel. I'll give that a try. Just for academic purpose, if
indeed I want to know the logger to feature mapping, where would I look?
Thanks
Balaji
On Thu, Jan 16, 2014 at 5:58 PM, Daniel Beck m...@beckweb.net wrote:
Logging wouldn't help for these, as these actions don't seem to get logged.
But check out the Audit Trail Plugin, which records the most important
user actions. To record enabling/disabling project via the buttons for it
(and not just users submitting the job config page), and add 'enable' and
'disable' to the regular expression of what it logs in the Advanced
configuration.
Unfortunately, Audit Trail only records e.g. that a user submitted a
config form ('/job/jobname/configSubmit by danielbeck') and not _what_ was
changed. This is where the Job Config History Plugin helps. It logs all
changes to job configurations in detail, and displays them as diffs of the
job config XML.
On 17.01.2014, at 01:19, Balaji Parthasarathy bpart...@gmail.com wrote:
Hi,
In my Jenkins instance, if I want to know things like
1. Who disabled a job and when?
2. When was it re-enabled? And who?
3. If a job config was changed, who changed it and what was changed?
I need to enable logging per feature. This URL
https://wiki.jenkins-ci.org/display/JENKINS/Logger+Configuration says
Refer to Hudson source code or the mailing list archive for what logger
corresponds to what feature. Can someone give quick pointers to logger
names for the above use cases? BTW, was this enhancement request
implemented -
http://jenkins-ci.361315.n4.nabble.com/Issue-4068-New-Provide-a-list-of-available-loggers-with-a-short-description-tt409405.html#none
I searched the mailing lists and general google search but did not get
any hits.
Thanks
Balaji
--
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: Jenkins global env vars stuck for some slave jobs
I believe that
JENKINS-14623https://issues.jenkins-ci.org/browse/JENKINS-14623 covers
this issue indirectly.
On Friday, January 17, 2014 9:54:59 AM UTC-8, Allen Cronce wrote:
Thanks. I just tried that (before seeing your email). It worked. The build
slave now has the correct env var value.
I guess that we can reboot as a work around. We don't change back and
forth between the trunk and branches that often.
But is there a more permanent solution? Maybe the problem you mentioned
has been fixed in an update?
On Friday, January 17, 2014 9:47:52 AM UTC-8, Jason Swager wrote:
Try restarting your slaves. There was an issue with EnvInject where
global variable changes wouldn't propagate to the slave unless the slave
was fully disconnected and reconnected.
On Friday, January 17, 2014 8:19:34 AM UTC-8, Allen Cronce wrote:
Hi all,
We've been trying to use Jenkins global env vars to define the svn URL
to use for some of our builds. While this seemed to work when we tested it
earlier, now that we're trying to set the env var back from a release
branch to the trunk, the value of the env var seems stuck for some build
jobs.
Our Machintosh full build has the old idea of the env var while our
Windows full build sees the new, correct env var value. Both of these jobs
are run on build slaves, not the Jenkins server. We're using Jenkins ver.
1.482.
Here's more details:
This is the env var is set in Configure System - Global properties -
Environment variables
name: FULL_BUILD_TRUNK_TO_USE
value: trunk
I've hacked our problematic Mac build job script to output what it
thinks is the value of this env var, then purposely error to stop the job.
I've also tried defining test env vars from the global one in the job
itself and via the env inject plugin as a test.
For the injected env var test, I've defined the following:
Build Environment - Inject environment variables to the build process
- Properties Content
INJECTED_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
For the build job env var test, I've defined the following:
Build Environment - Set environment variables
BUILD_ENV_VAR_TRUNK_TO_USE=$FULL_BUILD_TRUNK_TO_USE
Here's the hacked test build job script:
--snip--
#!/bin/sh
echo This is a hack to see what this build job thinks the build env var
is set to.
echo FULL_BUILD_TRUNK_TO_USE = ${FULL_BUILD_TRUNK_TO_USE}
echo INJECTED_TRUNK_TO_USE = ${INJECTED_TRUNK_TO_USE}
echo BUILD_ENV_VAR_TRUNK_TO_USE = ${BUILD_ENV_VAR_TRUNK_TO_USE}
exit 1
--snip--
In all cases, the above script code outputs the old branch value
of FULL_BUILD_TRUNK_TO_USE, not the new trunk value set in the global
config:
--snip--
[EnvInject] - Executing scripts and injecting environment variables
after the SCM step.
[EnvInject] - Injecting as environment variables the properties content
INJECTED_TRUNK_TO_USE=branches/RB-2.3.1
[EnvInject] - Variables injected successfully.
[ClientMacFull] $ /bin/sh
/var/folders/uu/uu50uc60HNO7gmdeMNxMEE+++TI/-Tmp-/hudson2189251323725654867.sh
This is a hack to see what this build job thinks the build env var is
set to.
FULL_BUILD_TRUNK_TO_USE = branches/RB-2.3.1
INJECTED_TRUNK_TO_USE = branches/RB-2.3.1
BUILD_ENV_VAR_TRUNK_TO_USE = branches/RB-2.3.1
--snip--
What's odd is that the Windows build does not have the same problem.
However one difference with that build is that the global env var is used
directly in the svn URL settings of that job, whereas the Mac build
manually calls svn directly from the script using the env var itself to
build the URL. So the Mac build script directly accesses the env var in the
script and the Windows build does not.
Any ideas as to what's wrong and how I can get this to work?
Thanks in advance for any suggestions.
Best,
Allen Cronce
--
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: LTS 1.532.2 release date
On 17.01.2014, at 15:39, Guillaume Boucherie guillaume.bouche...@gmail.com wrote: Version 1.532.1 has some really annoying bug. If the bug is more annoying than your process requirements are rigid, you can always upgrade to the recently created release candidate. http://jenkins-ci.org/stable-rc -- 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: How to get last stable build number through groovy script ?
On 17.01.2014, at 18:29, Maneesh M P maneesh.po...@gmail.com wrote: I am curious know why is that different from groovy plugin? Also there a document available to find out these information of groovy post build plugin and groovy plugin? Well, both have Wiki pages that describe what each individually does. Groovy plugin * provides a global tool configuration for managing Groovy versions, similar to what Ant and Maven plugins have. * provides a build step that runs standalone Groovy scripts (essentially launches the 'groovy' program) using the configured Groovy versions. * provides a build step (system Groovy) that runs a Groovy script within Jenkins which is only available for Admins/users with 'run scripts' permission. Groovy Postbuild Plugin * provides build badges and build summary actions that can be used from scripts * provides a publisher (post-build step) for running Groovy scripts within Jenkins - a helper object 'manager' makes access to the current build, log pattern matching, and the included build badges and summary action particularly easy - has an ineffective security option, so that anyone able to configure any job can run arbitrary code in Jenkins (JENKINS-15212) -- 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: Logger to feature mapping
Forwarding Daniel's reply to the mailing list in case it helps someone else in the future. Sorry if I should not have done that. Balaji On Fri, Jan 17, 2014 at 10:50 AM, Daniel Beck m...@beckweb.net wrote: The source code, I'm afraid (but you'll learn how to script and extend Jenkins in the process, so it could be worth the effort). Start with http://javadoc.jenkins-ci.org (Javadoc of core) and look for something that looks like it could be relevant -- hudson.model and jenkins.model are good choices to start looking. Then check the source code ( https://github.com/jenkinsci/jenkins/tree/master/core/src/main/java/) whether there are related log statements. http://sorcerer.jenkins-ci.org/ might be a useful alternative to the above combination, but it's stuck at version 1.513. If you want to know about a particular plugin: Most plugins are quite small, so the source should be easy enough to navigate. For commercial Cloudbees plugins, there is http://jenkins-enterprise-javadocs.apps.cloudbees.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: A way to get rid of useless local workspace?
It is pretty much the point of the slave agent and the way jenkins works to do all of the remote work for you. I wasn't sure if you did not understand that or if you had some special requirement to run your own remote ant script. If you want some things to be copied back to the master, add a post-build action to 'archive the artifacts' and specify the files you want. -- Les Mikesell lesmikes...@gmail.com On Fri, Jan 17, 2014 at 9:35 AM, kgiloo gilles.ka...@gmail.com wrote: Thank you so much for your explanation! It seems now easy to define a new slave, trigger svn update on it with SCM poll, and execute the Ant script from that location. Don't need even my Ant remote task anymore with jenkins slave agent... On Thursday, January 16, 2014 10:05:12 PM UTC+1, LesMikesell wrote: My builds are all done on slaves and even though the master controls the SCM polling, it does not check out any source locally on the master. However, with usual setup, the slave checks out a copy of the target the job is configure to poll before executing anything in the job.So I don't understand how you avoid that - or why you want to avoid it and make your own ant script do the slave checkout. And I think whatever it is you are doing is making the master do the checkout instead of the slave. On Thu, Jan 16, 2014 at 8:18 AM, kgiloo gilles...@gmail.com wrote: Sorry, i did not get your point... What do you mean exactly? On Thursday, January 16, 2014 5:31:05 AM UTC+1, LesMikesell wrote: On Wed, Jan 15, 2014 at 2:42 AM, kgiloo gilles...@gmail.com wrote: probably my description lacked precision: I should have titled A way to get rid of useless checkout of repository into my local workspace. I do not use any special slave configuration to trigger my builds on slaves, it is all driven by Ant. In other words, checkout of repository is also performed by Ant on slave. I need the poll SCM to kick off the build process, for nothing else, i.e checkout of repository in workspace has no sense on my master. Why do it that way? Why not include the ant script in the checkout and let jenkins do it in the right place for you? -- Les Mikesell lesmi...@gmail.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.
Re: how to change email address in all job configuration [Email Ext plugin]
I see this method in the code
* Get the list of configured email theTriggers for this project.
* @return
*/
public ListEmailTrigger getConfiguredTriggers() {
if (configuredTriggers == null) {
configuredTriggers = new ArrayListEmailTrigger();
}
But I am not sure how will i iterate through the configured triggers using
groovy :( can anyone help ?
Thanks,
Maneesh
On Friday, January 17, 2014 2:57:26 AM UTC-8, slide wrote:
You'd have yo get the configured triggers and iterate over them as well.
On Jan 16, 2014 6:16 PM, Maneesh M P manees...@gmail.com javascript:
wrote:
I was able to use the below script to iterate through email address, but
the problem is even this doesn't display addresses in the trigger
import hudson.plugins.emailext.*
import hudson.model.*
import hudson.maven.*
import hudson.maven.reporters.*
import hudson.tasks.*
// For each project
for(item in Hudson.instance.items) {
println(JOB : +item.name);
// Find current recipients defined in project
if(!(item instanceof ExternalJob)) {
if(item instanceof MavenModuleSet) {
println(MAVEN MODULE SET);
// Search for Maven Mailer Reporter
println(Reporters);
for(reporter in item.reporters) {
if(reporter instanceof MavenMailer) {
println( reporter : +reporter+ : +reporter.recipients);
}
}
} else
if(item instanceof FreeStyleProject) {
println(FREESTYLE PROJECT);
}
println(Publishers);
for(publisher in item.publishersList) {
// Search for default Mailer Publisher (doesn't exist for Maven
projects)
if(publisher instanceof Mailer) {
println( publisher : +publisher+ : +publisher.recipients);
} else
// Or for Extended Email Publisher
if(publisher instanceof ExtendedEmailPublisher) {
println( publisher : +publisher+ : +publisher.recipientList);
}
}
} else {
println(External Jobs cannot have MailNotificationsRecipients)
}
println(\n===\n);
}
Thanks,
Maneesh
On Thursday, January 16, 2014 5:11:50 PM UTC-8, slide wrote:
The easiest way is to use the script console. You need to iterate
through your projects, get the publisher list, find the email-ext publisher
and then modify the properties you need to for the recipient.
On Jan 16, 2014 4:29 PM, Maneesh M P manees...@gmail.com wrote:
Configure slicing plugin does not display the address specified inside
email triggers
Thanks,
Maneesh
On Thursday, January 16, 2014 3:15:58 PM UTC-8, Daniel Beck wrote:
Configuration Slicing plugin *might* work.
On 17.01.2014, at 00:09, Maneesh M P manees...@gmail.com wrote:
I have more than 300+ jobs configured in my jenkins and I am using
email ext plugin to configure the mail trigger. currently i am in a
situation where I have to change one recipient mail address to something
else
Is there an easy way to do it?
Thanks,
M
--
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-use...@googlegroups.com javascript:.
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: LTS 1.532.2 release date
On Fri, Jan 17, 2014 at 12:43 PM, Daniel Beck m...@beckweb.net wrote: On 17.01.2014, at 15:39, Guillaume Boucherie guillaume.bouche...@gmail.com wrote: Version 1.532.1 has some really annoying bug. If the bug is more annoying than your process requirements are rigid, you can always upgrade to the recently created release candidate. http://jenkins-ci.org/stable-rc Is there a changelog for that? -- Les Mikesell lesmikes...@gmail.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: LTS 1.532.2 release date
On 18.01.2014, at 00:32, Les Mikesell lesmikes...@gmail.com wrote: Is there a changelog for that? Not a regular one yet, but there's the list of resolved issues [1] and the list of changes since 1.532.1 in Git [2]. 1: https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+10172+AND+labels+%3D+%221.532.2-fixed%22 2: https://github.com/jenkinsci/jenkins/compare/jenkins-1.532.1...stable -- 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.
