Jenkins Selenium Grid plugin generates huge logfile
Hello,
from eclipse, my tests are running very well and there are no problems at
all.
But if I run my tests from Jenkins, the selenium plugin increases the
selenium.log for about 700mb each run.
It seems that there is any binary stuff appended to the log... look here:
INFO: REQUEST : {platform=ANY,
firefox_profile=UEsDBBQACAgIADRGRUI2ZXh0ZW5zaW9uc1xmaXJlYnVnQHNvZnR3YXJl
LmpvZWhld2l0dC5jb21cYm9vdHN0cmFwLmpzvVdbb9pIFH5H4j+c5aWmBdM+bLtNFa1awjaskoaG
oq5UVWiwB5itPcPOjHNplP++53jGxgZaULQbHsB4zv3ynTO9pzDmHBIRcWl4aG8szJUGy3VqQM0h
M2zB4Wmv2Wg2ej14+n9+oNfLlfSVNJZJa0hpRH+gH8Exvk9XSnI8CKOEGcPNm/Jc1M+FRA/mLKqS
ZHWSzIqETnOVZwIp0N250HyWLSBVcZZwA3bJLKQZHs4wSIrFPAZ8g+Zpm62AyRgy6d8rCWaZ2Vhd
yzAX+otAZZo8AX7F9S1Ifu0lF7KuhV2iZaGjLDWxmA6XXPNm44pp+GN4OXg3eT89vziZnA3G6MiX
ZgPw09LcqExH/KjX87b3YvpecH3KEgxC+LdpdX5MPJ9ZjWHaR+V+u0trV101M1xf7ZfseYhYHKwh
t+ZAnkWUiD0keZj3WZqoiCX7lKVCiq7m/2T4fw9pEaAD3VhpPj87xE6vvZsn+DDaPVTGKo39PV7b
2Wx8zXuirMmgyrfQvOdbo/fXqH9xPqEmQr601X5zCJPXtGZ5PFR5p5Q1WF4reDsakuJ5JiMrsGsF
wU2SBCumWWo6oDkzSrabjbtm475GmcnDaT1G7KSkfKBJl3yBuMMRbpccKhGDlK1WQi6MoyQEwFPs
+jJ8QoULbkdaWRWp5BRxKOF6HfVWO/yYIeIMCxgM+iKUZnjJzQYP5aCiI+eeXA43dCFw4ctgOh33
L4ejT1P8Mx2PBv3pFJ5BqxeGZYJbHZBZkrjvQjgKDg2342xmrLAZhSdo+Rpsdap6f8rhdLiW3mYr
o/o2RizONERLrVKKKwVZM5IRglQWYZgTvNKce/H8meOrDIaUSewJHSIIlzWz4vE5k2LOjT1DtMjt
cYkNfUWMmF2uzdjdCbs7vmZ8WRIxn7MssUC0OAckZsIRjdbMFIoTR0dvzQ6TOlAEulD1IBmRUt9E
3rYPl0HQjkVN0105uK15TrLyRlAInQm7BZ+HQwKa7AymLmLJbyxuN5gzH8I/HJu3vmjUbWs8HQKE
VYCOoCAUiD7ATKtrRHec3xLnvQnXTcRllnKsNiyuSg9dp9Svg/IsaEl2JRb0eORllYG9XgpcEIK1
oHDJzLnSfJDwlCo0aLcd5bYvFAhsevU5t6sqA9V/wDgE7RKJau5SoGTeErSkeLc6ZQQ2VqA8IJir...
and so on for about 9.000.000 lines.
I tried to set the selenium logger to WARNING but it doesn't change
anything.
Someone knows about this issue?
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: jenkins clustering
Hello Sami, 2013/2/5 Sami Tikka sjti...@gmail.com Oh you really meant you want your slaves to HA! sort of :) I'm just speculating on the possibility to have slaves not abort the build if communication with master is interrupted (e.g. master crashes) and build console logs be later retrieved as soon as master is back online. Usually people just have so many slaves it doesn't matter if some go down. we have this kind of redundancy too :) But in case of master failure, even if running on slaves machines perfectly fit, jobs would be abrouptly stopped just because master - slave channel is interrupted. Thanks again for your support. A presto, -m -- Sami Matteo Centonza mat...@metatype.it kirjoitti 4.2.2013 kello 16.37: Hello Sami, Rob, thanks for your replies. We are currently using redhat cluster to provide failover capabilities to jenkins master. Haven't tried Cloudbees Jenkins Enterprise either but from what' i've read, i assume failover capabilities are restricted to master failover, so functionally equivalent to what we have already achieved. I can't find any reference on slave resiliency in the event of a master failure, but i'll be really glad to be corrected from someone more knowledgeable than me on the enterprise product :) A presto, -m 2013/2/4 Mandeville, Rob rmandevi...@litle.com If you’re willing to pony up some money, you should talk to Cloudbees regarding their Enterprise version ( http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-overview.cb). I haven’t tried it (yet), but it comes with several plugins you can’t get otherwise, and one of them is a High Availability plugin. This specifically allows you to fail over to a second Jenkins master on the fly if the master dies. ** ** --Rob ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Matteo *Sent:* Tuesday, January 22, 2013 2:24 PM *To:* jenkinsci-users@googlegroups.com *Subject:* jenkins clustering ** ** Hello, ** ** first i'd like to thank developers for this great project. ** ** I'm sorry if already asked but i'm new on this list and searching the web has produced no results. ** ** We have a jenkins installation with 1 master and 5 slaves connected through ssh. ** ** We are mostly a java shop and jenkins is central to our infrastructure since we build and deploy releases to servers from it. ** ** For this reason slave resiliency in the face of master failure is paramount to us. ** ** My question: Is there a way, in a master/slave configuration, to have slave builds running to completion even in case of master failure (ideally refetching console logs once the master is back up :))? ** ** In our current setup, we get a proxy error on master UI and builds are aborted. ** ** Thanks in advance for any hint, ** ** -m 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. 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. -- 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.
loss of build data with multi-config (matrix) jobs on jenkins 1.480.2
Hi All, I've recently experienced some build loss with Jenkins: https://issues.jenkins-ci.org/browse/JENKINS-16638 Particularly frustrating as some of the lost builds were of an intermittent failure we've spent a week or two trying to track down... To try and figure out what's going on, what logging can I configure such that whenever a file gets deleted on the master in the build history, a line gets logged? I've scoured the existing jenkins.log file and there's nothing in there to indicate any problems... Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- 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: Build Flow Plugin: Ensuring jobs operate on the same Git revision
if you configure the build-flow itself to be triggered by SCM you may pass GIT_COMMIT to triggered jobs, never tried this. I expected you could also retrieve this commit revision from SCMRevisionState action, but git-plugin don't use this API (sic) 2013/2/4 Johannes Schirrmeister johannes.schirrmeis...@prezi.com Hi everyone, The Build Flow Plugin seems like a great way to orchestrate our build pipelines. I would like to ask if there is any best practice on how to ensure that all jobs in one pipeline checkout the same revisions of a Git repository. I believe the Git plugin initially sets the GIT_COMMIT environment variable and this value would have to be injected into the environments for all builds before they are run. I'd greatly appreciate your feedback, thank you! Johannes -- 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/Slave connection via TelNet
Hi ! Similar problem with version 1.500 of Jenkins (403 instead of 404) : Failing to obtain http://URL_JENKINS/computer/SLAVE/slave-agent.jnlp java.io.IOException: Failed to load http://URL_JENKINS/computer/SLAVE/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:236) at hudson.remoting.Launcher.run(Launcher.java:198) at hudson.remoting.Launcher.main(Launcher.java:171) Waiting 10 seconds before retry Failing to obtain http://URL_JENKINS/computer/SLAVE/slave-agent.jnlp java.io.IOException: Failed to load http://URL_JENKINS/computer/SLAVE/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:236) at hudson.remoting.Launcher.run(Launcher.java:198) at hudson.remoting.Launcher.main(Launcher.java:171) Waiting 10 seconds before retry I launch the slave using this command line : java -jar slave.jar -auth myuser:mypassword -jnlpUrl http://URL_JENKINS/computer/SLAVE/slave-agent.jnlp @Sami : The -auth option is printed when you run : java -jar slave.jar -optionthatdoesnotexist I can connect to Jenkins using this login/password. Any ideas ? Thanks in advance. Michaël Pailloncy 2013/2/3 Sami Tikka sjti...@gmail.com Which Jenkins version are you using? Recent Jenkins versions allowed unauthenticated access to the slave-agent.jnlp URL, which makes starting JNLP slaves a bit more difficult. I'm pretty sure the slave startup does not use -auth option to provide a username and password. Where did you pick that up? You can use a browser to authenticate and download the slave-agent.jnlp and save file on the slave local disk. Then start the slave and profile a file://localhost/path/to/slave-agent.jnlp as URL on the slave command line. -- Sami Mehdi Hayani Soujaa hayani.mehdi...@gmail.com kirjoitti 1.2.2013 kello 11.38: Hii, From the Jenkins-The Definitive Guide book we've tried to add the slave based on the command line strategy. So, as mentioned in the book, we used the following command: java -jar slave.jar -jnlpUrl _http://**.**.**.**:/cip/computer/NewNode/slave-agent.jnlp -auth user:password But, the problem is that each time we execute this command, we get this error: Failing to obtain http:// **.**.**.***:/cip/computer/NewNode/slave-agent.jnlp java.io.IOException: Failed to load _http://**.**.**.***:/cip/computer/NewNode/slave-agent.jnlp: 404 Not Found at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:238) at hudson.remoting.Launcher.run(Launcher.java:200) at hudson.remoting.Launcher.main(Launcher.java:173) Waiting 10 seconds before retry It seems that it can't find the slave agent file, But if we copy the URL in a browser manually, the file is downloaded. Any idea about this issue ?? Regards Mehdi -- 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. -- 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: m2release plugin release:rollback
I've missed the Use custom workspace option under the maven advanced configuration - I can use this to set up a remedy job for the real job, which operates on the workspace of the real job. On Tue, Feb 5, 2013 at 8:25 AM, Ilko Iliev ilkomil...@gmail.com wrote: Thanks for the info. Wipe out the workspace will leave the versions as changed during the prepare stage. IMHO this feature will be very helpful to revert to a stable stage w/out too much extra magic. It's true that the tag must be removed manually, if it has been created, but in our case this could be done direct from the IDE. On opposite, the build infrastructure is not in our (developers) full control and it is not so trivial to execute rollback from the shell because of the file permissions. On 04.02.2013, at 18:39, Eric Pyle eric.p...@cd-adapco.com wrote: I've seen release:rollback implemented as a Batch Task in a Maven build job. This was at my previous employer so I don't have access to the job anymore to give the details, but I think it is pretty straightforward. This way you can keep the rollback function together with the regular build job with no funny business about the SCM. It's true that if Maven has created tags, they won't be automatically deleted, but you can do that manually if needed. You may want to run maven release -DdryRun=true first to make sure there are no Maven errors before running the real build. DryRun won't commit any changes to source control. Regards, Eric On 2/4/2013 12:28 PM, teilo wrote: Hi, It’s not supported (which is why the RFE is still open) and comments in the wiki are not monitored by the plugin maintainer. Wipe out workspace is probably the best form or release:rollback J maven won’t delete the tag if it created it anyway - so depending on what failed you may well need to do something by hand anyway. Regards, /James On Monday, 4 February 2013 16:58:34 UTC, Ilko wrote: Hi, I came accross the request for release:rollback on failed release[1], however it is still marked as opened. From the wiki of the plugin[2] I can't figure out, if this feature is implemented or not and the RFE is one and half year old. Can someone give me an info? Or is there some other way to perform release:rollback after failed release? My very ugly solution was to set the SCM to None, run Pre-Build step with -B release:rollback goal and then dummy clean Build step, but as you can see this can only work with test jobs, because all config must be cleared :-( TIA [1] https://issues.jenkins-ci.org/browse/JENKINS-8263 [2] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin -- 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. -- 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: don't keep this build forever button does nothing
Hi Sami, Not talking about deleting builds here, but toggling keep build forever. It appears for some builds, this toggle can't take place but there's no indication why that might be, and the build stays kept even though I don't want it to be. How would I go about debugging this? cheers, Chris On 03/02/2013 23:13, Sami Tikka wrote: Jenkins only deletes builds when it runs the job. If you need the disk space vacated immediately, you can script it like described here: http://jenkins.361315.n4.nabble.com/Is-there-a-way-to-make-quot-discard-old-builds-quot-happen-right-now-td3879634.html -- Sami Chris Withersch...@simplistix.co.uk kirjoitti 20.1.2013 kello 0.43: Hi All, I'd like to delete this build: http://jenkins.simplistix.co.uk/job/testfixtures-tox/83/ ...however clicking the don't keep this build forever button does nothing. What am I doing wrong? Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- 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: arcvhiving takes forever - just me?
Fingerprints? https://issues.jenkins-ci.org/browse/JENKINS-13154 That made a significant difference to me. Other than that google for bandwidth delay product and ssh plugin (check the last comment in https://issues.jenkins-ci.org/browse/JENKINS-3922) /James On Monday, 4 February 2013 21:17:26 UTC, Maven User wrote: Hi all - Super quick question - maybe this is a known issue When archiving a large artifact, jenkins seems to take forever (in some cases, taking a 1 min build up to 30 min). What's weird is when I ssh up to that same slave and scp over that same artifact to the same final location, it takes less than 10 seconds. Suggestions? -- 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 Selenium Grid plugin generates huge logfile
I'll take a look into it,
Richard
On 2013-02-05, at 03:10, psiuk.da...@gmail.com wrote:
Hello,
from eclipse, my tests are running very well and there are no problems at all.
But if I run my tests from Jenkins, the selenium plugin increases the
selenium.log for about 700mb each run.
It seems that there is any binary stuff appended to the log... look here:
INFO: REQUEST : {platform=ANY,
firefox_profile=UEsDBBQACAgIADRGRUI2ZXh0ZW5zaW9uc1xmaXJlYnVnQHNvZnR3YXJl
LmpvZWhld2l0dC5jb21cYm9vdHN0cmFwLmpzvVdbb9pIFH5H4j+c5aWmBdM+bLtNFa1awjaskoaG
oq5UVWiwB5itPcPOjHNplP++53jGxgZaULQbHsB4zv3ynTO9pzDmHBIRcWl4aG8szJUGy3VqQM0h
M2zB4Wmv2Wg2ej14+n9+oNfLlfSVNJZJa0hpRH+gH8Exvk9XSnI8CKOEGcPNm/Jc1M+FRA/mLKqS
ZHWSzIqETnOVZwIp0N250HyWLSBVcZZwA3bJLKQZHs4wSIrFPAZ8g+Zpm62AyRgy6d8rCWaZ2Vhd
yzAX+otAZZo8AX7F9S1Ifu0lF7KuhV2iZaGjLDWxmA6XXPNm44pp+GN4OXg3eT89vziZnA3G6MiX
ZgPw09LcqExH/KjX87b3YvpecH3KEgxC+LdpdX5MPJ9ZjWHaR+V+u0trV101M1xf7ZfseYhYHKwh
t+ZAnkWUiD0keZj3WZqoiCX7lKVCiq7m/2T4fw9pEaAD3VhpPj87xE6vvZsn+DDaPVTGKo39PV7b
2Wx8zXuirMmgyrfQvOdbo/fXqH9xPqEmQr601X5zCJPXtGZ5PFR5p5Q1WF4reDsakuJ5JiMrsGsF
wU2SBCumWWo6oDkzSrabjbtm475GmcnDaT1G7KSkfKBJl3yBuMMRbpccKhGDlK1WQi6MoyQEwFPs
+jJ8QoULbkdaWRWp5BRxKOF6HfVWO/yYIeIMCxgM+iKUZnjJzQYP5aCiI+eeXA43dCFw4ctgOh33
L4ejT1P8Mx2PBv3pFJ5BqxeGZYJbHZBZkrjvQjgKDg2342xmrLAZhSdo+Rpsdap6f8rhdLiW3mYr
o/o2RizONERLrVKKKwVZM5IRglQWYZgTvNKce/H8meOrDIaUSewJHSIIlzWz4vE5k2LOjT1DtMjt
cYkNfUWMmF2uzdjdCbs7vmZ8WRIxn7MssUC0OAckZsIRjdbMFIoTR0dvzQ6TOlAEulD1IBmRUt9E
3rYPl0HQjkVN0105uK15TrLyRlAInQm7BZ+HQwKa7AymLmLJbyxuN5gzH8I/HJu3vmjUbWs8HQKE
VYCOoCAUiD7ATKtrRHec3xLnvQnXTcRllnKsNiyuSg9dp9Svg/IsaEl2JRb0eORllYG9XgpcEIK1
oHDJzLnSfJDwlCo0aLcd5bYvFAhsevU5t6sqA9V/wDgE7RKJau5SoGTeErSkeLc6ZQQ2VqA8IJir...
and so on for about 9.000.000 lines.
I tried to set the selenium logger to WARNING but it doesn't change anything.
Someone knows about this issue?
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-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: Getting all Job Information from different Server
Hi Andreas, thanks for your answer, that is what i expected. But if there is no such plugin, i guess i will go like you described it, and will do a little script work for my overview information. Maybe in the future, if there are more tasks which have to be solved i will finally have to create a plugin to do some configuration stuff for example. Again, thanks for your help. -- 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.
module marked as didn't run and tests not marking build as unstable
Hi, Building an m2 single-module project on Jenkins 1.485 and we are seeing two (possibly related) problems. Firstly, occasionally we are seeing the build have it's module marked as (didn't run) when from the console it is clear that it did. Secondly, we are seeing test failures and the build is still marked as successful not unstable. What is odd about this, is that jenkins still knows that the job is unstable because it doesn't trigger downstream projects. Anyone else seeing this or know what the problem might be? -- 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: Build Flow Plugin: Ensuring jobs operate on the same Git revision
Hi Nicolas, Thanks for getting back to me. My build flow is indeed triggered by SCM so I could come up with this workaround for now: Using the build flow DSL, I first retrieve the GIT_COMMIT value and then pass it as a parameter for all following builds. revision = build.properties[environment][GIT_COMMIT] build(pipeline-start, GIT_COMMIT: revision) [...] What makes this a little messy is the extra build step git checkout $GIT_COMMIT I have to add for every job. Do you or anyone else on this list see a chance to communicate the GIT_COMMIT value to the Git plugin directly? (Somehow overwriting the GIT_COMMIT environment variable so the plugin would checkout that revision before the build is executed...?) On Tue, Feb 5, 2013 at 11:04 AM, nicolas de loof nicolas.del...@gmail.comwrote: if you configure the build-flow itself to be triggered by SCM you may pass GIT_COMMIT to triggered jobs, never tried this. I expected you could also retrieve this commit revision from SCMRevisionState action, but git-plugin don't use this API (sic) 2013/2/4 Johannes Schirrmeister johannes.schirrmeis...@prezi.com Hi everyone, The Build Flow Plugin seems like a great way to orchestrate our build pipelines. I would like to ask if there is any best practice on how to ensure that all jobs in one pipeline checkout the same revisions of a Git repository. I believe the Git plugin initially sets the GIT_COMMIT environment variable and this value would have to be injected into the environments for all builds before they are run. I'd greatly appreciate your feedback, thank you! Johannes -- 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. -- 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.
Perform a single svn checkout in a multi-configuration project
Hello, I am configuring a Jenkins server and I dont know, if possible, how to configure correctly svn checkout. I have a multiexecutable project. Building steps are: Checkout entire repository Build per project Test per project. So, I configured a multi-configuration project with an user-axis named project for iterating. However, instead of a single entire svn checkout, Jenkins performs a checkout in workspace, it creates a project directory, it creates a directory for each project and, inside each project directory, checkout again entire directory. I can't perform checkout iteratively because are interrelated projects, I need the code of two or three projects at the same time before I could build any of them. Is there any way to perform an unique checkout to workspace? Thank you 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.
Re: Build Flow Plugin: Ensuring jobs operate on the same Git revision
afaik you can configure the git-plugin to checkout a commit passed as paramter, setting it as branch 2013/2/5 Johannes Schirrmeister johannes.schirrmeis...@prezi.com Hi Nicolas, Thanks for getting back to me. My build flow is indeed triggered by SCM so I could come up with this workaround for now: Using the build flow DSL, I first retrieve the GIT_COMMIT value and then pass it as a parameter for all following builds. revision = build.properties[environment][GIT_COMMIT] build(pipeline-start, GIT_COMMIT: revision) [...] What makes this a little messy is the extra build step git checkout $GIT_COMMIT I have to add for every job. Do you or anyone else on this list see a chance to communicate the GIT_COMMIT value to the Git plugin directly? (Somehow overwriting the GIT_COMMIT environment variable so the plugin would checkout that revision before the build is executed...?) On Tue, Feb 5, 2013 at 11:04 AM, nicolas de loof nicolas.del...@gmail.com wrote: if you configure the build-flow itself to be triggered by SCM you may pass GIT_COMMIT to triggered jobs, never tried this. I expected you could also retrieve this commit revision from SCMRevisionState action, but git-plugin don't use this API (sic) 2013/2/4 Johannes Schirrmeister johannes.schirrmeis...@prezi.com Hi everyone, The Build Flow Plugin seems like a great way to orchestrate our build pipelines. I would like to ask if there is any best practice on how to ensure that all jobs in one pipeline checkout the same revisions of a Git repository. I believe the Git plugin initially sets the GIT_COMMIT environment variable and this value would have to be injected into the environments for all builds before they are run. I'd greatly appreciate your feedback, thank you! Johannes -- 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. -- 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: Build Flow Modularization
so, you are running a meta-flow plugin !
there is no short term plan for the build-flow plugin to offer this level
of flexibility. I plan to make the DSL source an extension point, so user
can either write the groovy DSL (as they do today) or use a graphical
designer (with limited capabilities, but probably simpler for
non-developers). This may be used by you to dynamically provide the DSL.
Anyway, this only is a long term plan, mostly depending on my spare time...
2013/2/1 Foxgang teve...@gmail.com
We are using the Jenkins Build Flow plugin to orchestrate our builds.
Currently, we have worked out a semi-hacky way to dynamically generate a
DSL string based on available jobs and parameters, which we then invoke by
emulating what the plugin does behind the scenes. This woks just fine, but
it's extremely long and complex. Moreover, we want to be able to run this
'DSL generator' from multiple build flow jobs, so we can have
different development branches run by different flows.
In short, we need a way to pull our DSL out into a script file, or better
yet, into the scriptler plugin, then call it from the build flow job. This
will make the jobs much easier to handle, and will
reduce maintenance points. Is there a roadmap for this sort of thing?
Also, one of the big pains of the plugin is that the contents of the text
field in the job are manually concatenated into the flow closure (flow
{+dsl+}) behind the scenes, preventing users from defining functions,
imports, or much of anything. This is part of the reason that our dynamic
build flow generation is so verbose and hacky; everything is being placed
in the flow closure, so anything too robust produces groovy syntax errors.
--
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: Perform a single svn checkout in a multi-configuration project
On Tue, Feb 5, 2013 at 6:33 AM, Fernando Cerezal krypto...@gmail.com wrote: I am configuring a Jenkins server and I dont know, if possible, how to configure correctly svn checkout. I have a multiexecutable project. Building steps are: Checkout entire repository Build per project Test per project. So, I configured a multi-configuration project with an user-axis named project for iterating. However, instead of a single entire svn checkout, Jenkins performs a checkout in workspace, it creates a project directory, it creates a directory for each project and, inside each project directory, checkout again entire directory. I can't perform checkout iteratively because are interrelated projects, I need the code of two or three projects at the same time before I could build any of them. Is there any way to perform an unique checkout to workspace? Multi-configuration jobs are generally used to build in parallel across a different set of platforms or environments. If your job is just one set of serialized steps why can't you just use a job with several build steps or your own build script that does them all - perhaps using svn externals to get all the code components? Or organize things so the artifacts from one build are available to the next. -- 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: Jenkins/Slave connection via TelNet
On 05/02/2013 16:00, Mehdi Hayani Soujaa wrote: Hi, Since we're using LDAP authentication to access jenkins server, i taught that using -auth and specify some LDAP credentials would solve the problem, But this did not work So what we've done, is that we've created a new role with the Connect right on the Slave and assigned to the Anonymous user Doesn't this expose you to exactly the security hole that forced this change in the first place? Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- 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: hudson migration
gorazd, i ended up just creating new jobs from scratch and running jenkins along side hudson to build the history up. this allowed me to cleanup some unused jobs and stage jenkins in an operational environment for production deployment. regards, -- Sent from my mobile device Stefan Schwoegler ste...@cryp7.net On Feb 5, 2013, at 1:01, gi...@ptica.net gi...@ptica.net wrote: Hello, I have preaty much the same problem as you described in http://jenkins.361315.n4.nabble.com/hudson-migration-all-jobs-are-gone-td4640310.html I have 80+ jobs to migrate. Did you find any solution to your problem? Thanks, Gorazd Kos, Slovenia -- 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.
Detect command failure?
Hi, I am running jenkins on Linux. Yesterday, because of a memory issue, phpunit was not able to run the hole tests suite. However the build was still successful. I understand that if phpunit fails it does not return any errors or failures. Now I am wondering if there is a way to make Jenkins detect this kind of issues. 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
How does Jenkins checkout sources from svn to the slaves?
Hi Team, Does any one know how Jenkins checkout source code from SVN repository to slaves? I'm posting this question because we are facing a case which has demonstrated the opposite of our assumption: - *svn co https://..* does not work if we launch it directly in the slave simply because SSL is disabled - But if we execute a job that builds on that slave, checkout works successfully and sources are downloaded to the slave So, i would be very grateful if someone could explain me what is happening ? and how Jenkins proceed concerning source checkout ? Regards Mehdi -- 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: Detect command failure?
If your call to phpunit is expected to create a file, you could check that file is created and then use exit 1 to cause the build script to exit with the failure. Mark Waite From: Adam Tong adam.to...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Tuesday, February 5, 2013 9:17 AM Subject: Detect command failure? Hi, I am running jenkins on Linux. Yesterday, because of a memory issue, phpunit was not able to run the hole tests suite. However the build was still successful. I understand that if phpunit fails it does not return any errors or failures. Now I am wondering if there is a way to make Jenkins detect this kind of issues. 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-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: arcvhiving takes forever - just me?
I tried setting the window but I have no idea what the number relates to. Should it be 4 thousand, 400 thousand, 400 billion? On Tuesday, February 5, 2013 5:39:17 AM UTC-5, teilo wrote: Fingerprints? https://issues.jenkins-ci.org/browse/JENKINS-13154 That made a significant difference to me. Other than that google for bandwidth delay product and ssh plugin (check the last comment in https://issues.jenkins-ci.org/browse/JENKINS-3922) /James On Monday, 4 February 2013 21:17:26 UTC, Maven User wrote: Hi all - Super quick question - maybe this is a known issue When archiving a large artifact, jenkins seems to take forever (in some cases, taking a 1 min build up to 30 min). What's weird is when I ssh up to that same slave and scp over that same artifact to the same final location, it takes less than 10 seconds. Suggestions? -- 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.
Beta Build Environment
I work for an agile development group, so we like to test everything, including our build environment. I have been challenged to figure out how my team can create a second build environment to test enhancements on. This would also involve creating a beta copy of our Jenkins instance. We need to be able to test changes to (in order of importance) job configurations, slave configurations, and (possibly) plugin configurations. Is there any way to do this? Has anyone ever tried? Thanks in advance, --Rob Mandeville 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Detect command failure?
Hi, Where should I do this check exactly? Is there a way to do that in build.xml? Thank you On Tue, Feb 5, 2013 at 12:03 PM, Mark Waite markwa...@yahoo.com wrote: If your call to phpunit is expected to create a file, you could check that file is created and then use exit 1 to cause the build script to exit with the failure. Mark Waite From: Adam Tong adam.to...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Tuesday, February 5, 2013 9:17 AM Subject: Detect command failure? Hi, I am running jenkins on Linux. Yesterday, because of a memory issue, phpunit was not able to run the hole tests suite. However the build was still successful. I understand that if phpunit fails it does not return any errors or failures. Now I am wondering if there is a way to make Jenkins detect this kind of issues. 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-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. -- 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: arcvhiving takes forever - just me?
Regardless of the setting NOTHING makes the archiving go faster :-/ -- 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 user/group?
Hi, Some of my jobs need to access directories outside of the workspace. In my Hudson environment, I changed it to run as another user but that causes substantial issues at upgrade time. I'd like to avoid that with Jenkins. - Jenkins is running on an Ubuntu server. - The jobs run as user 'jenkins', group 'nogroup' sudo -u jenkins groups nogroup Note there are files in the /var/lib/jenkins that belong to 'adm' group. I don't know which userid the Jenkins updates use. It seems to me there are a few choices: 1) chgrp the external directories to the nogroup group. This should give jenkins userid access to the directories via the group permissions 2) chmod the external directories to 777. Go wide open 3) add jenkins userid to the same group that the external directories belong to. 4) create a new group and add the jenkins userid and all the external directories to the new group. The jenkins userid will still belong to the nogroup group and so the updates should work correctly. 5) or some other technique What is your recommendation? PS just tried #3, but still go permission denied sudo usermod -a -G cm6 jenkins sudo -u jenkins groups nogroup cm6 ls: cannot access /home/cm6/Applications/blah.xml: Permission denied John -- 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 does Jenkins checkout sources from svn to the slaves?
subversion plugin uses svnkit, not native svn client 2013/2/5 Mehdi Hayani Soujaa hayani.mehdi...@gmail.com Hi Team, Does any one know how Jenkins checkout source code from SVN repository to slaves? I'm posting this question because we are facing a case which has demonstrated the opposite of our assumption: - *svn co https://..* does not work if we launch it directly in the slave simply because SSL is disabled - But if we execute a job that builds on that slave, checkout works successfully and sources are downloaded to the slave So, i would be very grateful if someone could explain me what is happening ? and how Jenkins proceed concerning source checkout ? Regards Mehdi -- 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 user/group?
If you did that 'ls' command in the same shell where you did the 'sudo' commands, it did not work because group membership is applied to your session at login time. You would need to logout and login again for your session to belong to the new groups(s). When you run 'sudo -u jenkins' that creates a new session that *is* in the new groups, but your existing session is not. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Feb 5 2013 14:50:32 Hi, Some of my jobs need to access directories outside of the workspace. In my Hudson environment, I changed it to run as another user but that causes substantial issues at upgrade time. I'd like to avoid that with Jenkins. - Jenkins is running on an Ubuntu server. - The jobs run as user 'jenkins', group 'nogroup' sudo -u jenkins groups nogroup Note there are files in the /var/lib/jenkins that belong to 'adm' group. I don't know which userid the Jenkins updates use. It seems to me there are a few choices: 1) chgrp the external directories to the nogroup group. This should give jenkins userid access to the directories via the group permissions 2) chmod the external directories to 777. Go wide open 3) add jenkins userid to the same group that the external directories belong to. 4) create a new group and add the jenkins userid and all the external directories to the new group. The jenkins userid will still belong to the nogroup group and so the updates should work correctly. 5) or some other technique What is your recommendation? PS just tried #3, but still go permission denied sudo usermod -a -G cm6 jenkins sudo -u jenkins groups nogroup cm6 ls: cannot access /home/cm6/Applications/blah.xml: Permission denied John -- 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 user/group?
Thank you Kevin, that worked. The ls command was in the jenkins job. I restarted jenkins: sudo service jenkins restart and then re-ran the job. Works like charm! Thanks again. John On Tue, Feb 5, 2013 at 12:06 PM, KEVIN FLEMING (BLOOMBERG/ 731 LEXIN) kpflem...@bloomberg.net wrote: If you did that 'ls' command in the same shell where you did the 'sudo' commands, it did not work because group membership is applied to your session at login time. You would need to logout and login again for your session to belong to the new groups(s). When you run 'sudo -u jenkins' that creates a new session that *is* in the new groups, but your existing session is not. -- *From:*jenkinsci-users@googlegroups.com*To:* jenkinsci-users@googlegroups.com*Date:* 2/05 14:50 -- Hi, Some of my jobs need to access directories outside of the workspace. In my Hudson environment, I changed it to run as another user but that causes substantial issues at upgrade time. I'd like to avoid that with Jenkins. - Jenkins is running on an Ubuntu server. - The jobs run as user 'jenkins', group 'nogroup' sudo -u jenkins groups nogroup Note there are files in the /var/lib/jenkins that belong to 'adm' group. I don't know which userid the Jenkins updates use. It seems to me there are a few choices: 1) chgrp the external directories to the nogroup group. This should give jenkins userid access to the directories via the group permissions 2) chmod the external directories to 777. Go wide open 3) add jenkins userid to the same group that the external directories belong to. 4) create a new group and add the jenkins userid and all the external directories to the new group. The jenkins userid will still belong to the nogroup group and so the updates should work correctly. 5) or some other technique What is your recommendation? PS just tried #3, but still go permission denied sudo usermod -a -G cm6 jenkins sudo -u jenkins groups nogroup cm6 ls: cannot access /home/cm6/Applications/blah.xml: Permission denied John -- 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. -- 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 does Jenkins work with Source Control ??
I'm not understanding the process that Jenkins uses for interacting with the source control system. Oh, I understand that there are various plugins for various source control systems with various capabilities, but I'm not understanding what the flow is. Questions: 1. When is the source control system called to pull a workspace? 2. Can I control the parameters to the pull command? 3. Is it expected that every build is done to a fresh workspace? 4. Or is it that, after the workspace is setup, future builds will be incremental? 5. How and when does Jenkins do its polling of the source control system? 6. If the build does an update of some source (for instance, the build version#), how should the update be pushed back into the source control system? I hope that gives an idea of what I'm looking for. Is there any documentation or examples of setting up jobs in Jenkins to work with a source control system? -- 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: $HOSTNAME in email-ext plugins
That's a reasonable workaround; we might do that if we have to. We name our
nodes differently than the machine name though (e.g. computer1-unix-rhel6
for the machine named computer1 running RedHat 6). So there's no way to
get the machine name? Should this be reported as a bug?
On Monday, February 4, 2013 2:01:41 PM UTC-6, slide wrote:
I'd recommend using the NODE_NAME variable instead. It works cross
platform.
On Mon, Feb 4, 2013 at 1:00 PM, Foxgang tev...@gmail.com javascript:wrote:
We would like Jenkins to include the machine name of the slave it used
when it sends an email. On windows slaves, this is solved by using ${ENV,
var=COMPUTERNAME}. This uses the Token Macro expansion plugin to grab the
%COMPUTERNAME% environment variable.
However, this doesn't seem to work with $HOSTNAME (the Unix equivalent).
Strangely, it does work for other Unix variables, like $HOME. Additionally,
when I put 'echo $HOSTNAME' in an 'execute shell' build step, it also
works. Is there some reason that this particular variable doesn't expand?
Is there an alternate method I could use?
--
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.
--
Website: http://earl-of-code.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: $HOSTNAME in email-ext plugins
I don't think it's a bug, if the variable isn't available, there is nothing
email-ext can do to get it really.
Sent from my Windows Phone
--
From: Foxgang
Sent: 2/5/2013 16:22
To: jenkinsci-users@googlegroups.com
Subject: Re: $HOSTNAME in email-ext plugins
That's a reasonable workaround; we might do that if we have to. We name our
nodes differently than the machine name though (e.g. computer1-unix-rhel6
for the machine named computer1 running RedHat 6). So there's no way to
get the machine name? Should this be reported as a bug?
On Monday, February 4, 2013 2:01:41 PM UTC-6, slide wrote:
I'd recommend using the NODE_NAME variable instead. It works cross
platform.
On Mon, Feb 4, 2013 at 1:00 PM, Foxgang tev...@gmail.com javascript:wrote:
We would like Jenkins to include the machine name of the slave it used
when it sends an email. On windows slaves, this is solved by using ${ENV,
var=COMPUTERNAME}. This uses the Token Macro expansion plugin to grab the
%COMPUTERNAME% environment variable.
However, this doesn't seem to work with $HOSTNAME (the Unix equivalent).
Strangely, it does work for other Unix variables, like $HOME. Additionally,
when I put 'echo $HOSTNAME' in an 'execute shell' build step, it also
works. Is there some reason that this particular variable doesn't expand?
Is there an alternate method I could use?
--
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.
--
Website: http://earl-of-code.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.
Jenkins 1.498 - Builds disappearing
We've just noticed that for any new jobs that have been setup under 1.498, the builds are disappearing a few minutes after they have been run. We don't have the jobs flagged as Discard builds, and I can still see the builds in the JENKINSHOME\jobs\job_name\builds folder, so the data is there. They just don't appear through the UI. Has anyone else noticed this? --- Daniel Becroft -- 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.
Copy Artifact plugin doesn't traverse entire upstream path
If I have the following setup: jobA - jobB - jobC - jobD As part of jobD's work, I need to copy an artifact from jobA. However, the copy artifact plugin doesn't seem to know about jobA, and I get the following error: Started by upstream project test-copy-B http://jenkins.supercorp.local:8080/job/test-copy-B/ build number 1 http://jenkins.supercorp.local:8080/job/test-copy-B/1 originally caused by: Started by upstream project test-copy-A http://jenkins.supercorp.local:8080/job/test-copy-A/ build number 1 http://jenkins.supercorp.local:8080/job/test-copy-A/1 originally caused by: Started by user anonymous http://jenkins.supercorp.local:8080/user/null Building remotely on SCBBUILD01.supercorp.local http://jenkins.supercorp.local:8080/computer/SCBBUILD01.supercorp.local in workspace D:\jenkins\workspace\test-copy-C Unable to find a build for artifact copy from: test-copy-A Build step 'Copy artifacts from another project' marked build as failure Finished: FAILURE Any ideas? --- Daniel Becroft -- 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 1.498 - Builds disappearing
Further information: Restarting Jenkins makes the builds display again, but that's not an ideal solution. There is still an underlying issue with the jobs somewhere. --- Daniel Becroft On Wed, Feb 6, 2013 at 3:05 PM, Daniel Becroft djcbecr...@gmail.com wrote: We've just noticed that for any new jobs that have been setup under 1.498, the builds are disappearing a few minutes after they have been run. We don't have the jobs flagged as Discard builds, and I can still see the builds in the JENKINSHOME\jobs\job_name\builds folder, so the data is there. They just don't appear through the UI. Has anyone else noticed this? --- Daniel Becroft -- 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 1.498 - Builds disappearing
I am also facing the similar issue, Poll SCM @daily also not working for this jobs... But for Nigghtly Builds we dont have any issue. thanks bala On Wed, Feb 6, 2013 at 10:48 AM, Daniel Becroft djcbecr...@gmail.comwrote: Further information: Restarting Jenkins makes the builds display again, but that's not an ideal solution. There is still an underlying issue with the jobs somewhere. --- Daniel Becroft On Wed, Feb 6, 2013 at 3:05 PM, Daniel Becroft djcbecr...@gmail.comwrote: We've just noticed that for any new jobs that have been setup under 1.498, the builds are disappearing a few minutes after they have been run. We don't have the jobs flagged as Discard builds, and I can still see the builds in the JENKINSHOME\jobs\job_name\builds folder, so the data is there. They just don't appear through the UI. Has anyone else noticed this? --- Daniel Becroft -- 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. -- Bala.ch -- 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 ensure a job executes on all slaves.
Hi all, We have just upgraded some 3rd party libraries we use. I would like a Jenkins job to pull them from subversion onto all our windows build slaves. I have them grouped under a label. thanks kenneth -- 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.
