Run tests on another machine
Hii, I have a build running on jenkins and I'm using maven. I wonder how I could run my screen test on a different machine that is the jenkins, the bamboo that is setting up a possible agent. I need this configuration because the machine that is the jenkins is a CentOS without graphics, and my screen tests need to be on a windows machine with a browser. Could someone help me or have some material for this? thank -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3a3f37aa-920f-4c48-b1e3-2e1e296c6b65%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Run tests on another machine
Usually that would mean that the PATH on your Windows machine does not include the maven bin directory. On Tue, Apr 28, 2015 at 7:25 AM Erick Macedo erickfmac...@gmail.com wrote: First, thank you for personal help. I'm trying to configure it with the plugin Send files or execute commands over SSH In Exec command, I am entering something like: cd test / project-1 mvn install But this error happens on linux SSH: Connecting from host [web.buy] SSH: Connecting with configuration [Test Server] ... SSH: EXEC: STDOUT / STDERR from command [cd test / project-1 mvn clean install] ... bash: --command = mvn clean install: command not found My Maven is configured correctly. Could someone help me with this? Em terça-feira, 28 de abril de 2015 08:37:30 UTC-3, Erick Macedo escreveu: Hii, I have a build running on jenkins and I'm using maven. I wonder how I could run my screen test on a different machine that is the jenkins, the bamboo that is setting up a possible agent. I need this configuration because the machine that is the jenkins is a CentOS without graphics, and my screen tests need to be on a windows machine with a browser. Could someone help me or have some material for this? thank -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d2f173cf-43d7-40cd-a16e-d19a6c8c9dd6%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/d2f173cf-43d7-40cd-a16e-d19a6c8c9dd6%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG3cMeXYfg8PfsC_nFk9Cwapbpchhn6wzEmNF7LoMKDFA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Run tests on another machine
Mark, this test I am running on another linux machine, but when work will move to a Windowns. Maven is configured correctly, if I go in and finish typing mvn -va version is displayed correctly. On the tips of staff I understand that, to have a Slaves I would have to have another server installed jenkins, right? To work with Jenkins (Master and Slave) And in my case I just wanted to run the test on another server and get the return Em terça-feira, 28 de abril de 2015 08:37:30 UTC-3, Erick Macedo escreveu: Hii, I have a build running on jenkins and I'm using maven. I wonder how I could run my screen test on a different machine that is the jenkins, the bamboo that is setting up a possible agent. I need this configuration because the machine that is the jenkins is a CentOS without graphics, and my screen tests need to be on a windows machine with a browser. Could someone help me or have some material for this? thank -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6ee41dbe-85ce-4b41-8058-63f86050%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Run tests on another machine
There is more information in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds In order to run screen tests, Jenkins or a Jenkins slave needs access to the GUI. The easiest way (that I know of) is to start the Jenkins slave as a JNLP agent. On Tuesday, April 28, 2015 at 1:37:30 PM UTC+2, Erick Macedo wrote: Hii, I have a build running on jenkins and I'm using maven. I wonder how I could run my screen test on a different machine that is the jenkins, the bamboo that is setting up a possible agent. I need this configuration because the machine that is the jenkins is a CentOS without graphics, and my screen tests need to be on a windows machine with a browser. Could someone help me or have some material for this? thank -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5283a170-7ed4-404d-9b3e-dea0d0959807%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Run tests on another machine
Hi, Am 28.04.2015 um 15:54 schrieb Fred G: In order to run screen tests, Jenkins or a Jenkins slave needs access to the GUI. The easiest way (that I know of) is to start the Jenkins slave as a JNLP agent. It is also possible to install it as a service, however you have to go into the service configuration and explicitly enable GUI access. Simon -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/553F93C2.1080300%40hogyros.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: HTTPS Subversion 1.7 and Jenkins - issuer not trusted
Adam Retter adam.retter@... writes: Hi Jan, Thanks for your reply I have finally solved this, unfortunately it was not as simple as I hoped (probably due to the fact our platform is on Windows Server). The point you raised below, gave me a good hint - Run a simply svn command like list/info/whatever from a shell/command box and accept the cert if prompted so. So looking at the build output, I could tell that the 'buildnumber' Maven plugin was directly calling svn, so this was outside of Jenkins awareness really. I then realised that Jenkins was running as the 'SYSTEM' user and so that svn command was being executed by the SYSTEM user. Obviously the SYSTEM user needed to accept the server certificate and provide authentication, which it didnt had. I located where svn keeps its auth details for the SYSTEM user on Windows 2008 Server - C:\Windows\System32\config\systemprofile\AppData\Roaming\Subversion\auth and I copied in appropriate authentication files to the svn.simple and and svn.ssl.server folders from another account where I knew the build worked. It did now accept the SSL cert but refused to authenticate. So no luck doing that. I then tried a different approach. I re- installed Jenkins making sure that it would run under a custom user account called - s-subversion and configured the Windows service appropriately to use that account. When I tried to build the project I had the same issue again, but I could now open a command prompt running as the 's-jenkins' user and execute 'svn up' in the job's workspace, svn then prompted me to accept the server certificate and enter a username and password. After that running the build again in Jenkins now works perfectly. I have added the detail above to try and assist future Windows server users. Thanks Hi, I had figured out a solution for this. Just login to the Windows Server with any user credentials. Open Command Prompt, set USERNAME=SYSTEMNAME$ (Whatever USERNAME is used as per the Jenkins) set USERDOMAIN=DOMAIN (Whatever DOMAINNAME is used as per the Jenkins) set USERPROFILE=C:\Windows\System32\config\systemprofile (same as the one taken by Jenkins) Then run svn command, so it will check for the username and profile folder and come up with asking for svn credentials and it will get saved as encrypted in the folders under C:\Windows\System32\config\systemprofile\AppData\Roaming\Subversion\auth Thanks, Sreekumar R -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/loom.20150428T133356-809%40post.gmane.org. For more options, visit https://groups.google.com/d/optout.
Re: Run tests on another machine
With Jenkins it is easiest to add a slave on the target platform, then restrict the job to that slave. For greater flexibility, you can assign a label to the slave and restrict the job by label. For even more flexibility, there are plugins that will automatically assign labels by platform or by installed tool. Mark Waite On Tue, Apr 28, 2015, 5:37 AM Erick Macedo erickfmac...@gmail.com wrote: Hii, I have a build running on jenkins and I'm using maven. I wonder how I could run my screen test on a different machine that is the jenkins, the bamboo that is setting up a possible agent. I need this configuration because the machine that is the jenkins is a CentOS without graphics, and my screen tests need to be on a windows machine with a browser. Could someone help me or have some material for this? thank -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3a3f37aa-920f-4c48-b1e3-2e1e296c6b65%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/3a3f37aa-920f-4c48-b1e3-2e1e296c6b65%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG%3DmXPVB8YyBXk_MSWJ907XbFL8chmgHmPAUbD-WSP2gQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: HTTPS Subversion 1.7 and Jenkins - issuer not trusted
Adam Retter adam.retter@... writes: Hi Jan, Thanks for your reply I have finally solved this, unfortunately it was not as simple as I hoped (probably due to the fact our platform is on Windows Server). The point you raised below, gave me a good hint - Run a simply svn command like list/info/whatever from a shell/command box and accept the cert if prompted so. So looking at the build output, I could tell that the 'buildnumber' Maven plugin was directly calling svn, so this was outside of Jenkins awareness really. I then realised that Jenkins was running as the 'SYSTEM' user and so that svn command was being executed by the SYSTEM user. Obviously the SYSTEM user needed to accept the server certificate and provide authentication, which it didnt had. I located where svn keeps its auth details for the SYSTEM user on Windows 2008 Server - C:\Windows\System32\config\systemprofile\AppData\Roaming\Subversion\auth and I copied in appropriate authentication files to the svn.simple and and svn.ssl.server folders from another account where I knew the build worked. It did now accept the SSL cert but refused to authenticate. So no luck doing that. I then tried a different approach. I re- installed Jenkins making sure that it would run under a custom user account called - s-subversion and configured the Windows service appropriately to use that account. When I tried to build the project I had the same issue again, but I could now open a command prompt running as the 's-jenkins' user and execute 'svn up' in the job's workspace, svn then prompted me to accept the server certificate and enter a username and password. After that running the build again in Jenkins now works perfectly. I have added the detail above to try and assist future Windows server users. Thanks Hi, I had figured out a solution for this. Just login to the Windows Server with any user credentials. Open Command Prompt, set USERNAME=SYSTEMNAME$ (Whatever USERNAME is used as per the Jenkins) set USERDOMAIN=DOMAIN (Whatever DOMAINNAME is used as per the Jenkins) set USERPROFILE=C:\Windows\System32\config\systemprofile (same as the one taken by Jenkins) Then run svn command, so it will check for the username and profile folder and come up with asking for svn credentials and it will get saved as encrypted in the folders under C:\Windows\System32\config\systemprofile\AppData\Roaming\Subversion\auth Thanks, Sreekumar R -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/loom.20150428T133457-847%40post.gmane.org. For more options, visit https://groups.google.com/d/optout.
How to perform distributed tests on available Jenkins nodes?
For every nightly SW build, I want it to be tested on available testing systems. I created Jenkins slaves for these system, and listen to the completion of Jenkins build. I am trying to use Node label Parameter plugin to trigger test on particular system, ideally Jenkins can find whichever an idle system and start test on it. The results are, tests on the default Node can be always started, automatically or manually, but I can never start the test on Possible Node. What's the right way to achieve what I planned. I have my job configuration image attached. Any idea is greatly appreciated. Thanks Victoria -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1a44a41a-b170-4d31-97d5-66becf8e7c5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to perform distributed tests on available Jenkins nodes?
I use the elastic axis plugin to define a multi configuration job which runs a single job on all available slaves. The platform labeler plugin makes platform selection easier with the elastic axis plugin. Mark Waite On Tue, Apr 28, 2015, 9:23 AM Victoria Wei Lei weile...@gmail.com wrote: For every nightly SW build, I want it to be tested on available testing systems. I created Jenkins slaves for these system, and listen to the completion of Jenkins build. I am trying to use Node label Parameter plugin to trigger test on particular system, ideally Jenkins can find whichever an idle system and start test on it. The results are, tests on the default Node can be always started, automatically or manually, but I can never start the test on Possible Node. What's the right way to achieve what I planned. I have my job configuration image attached. Any idea is greatly appreciated. Thanks Victoria -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1a44a41a-b170-4d31-97d5-66becf8e7c5d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/1a44a41a-b170-4d31-97d5-66becf8e7c5d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF9HRe%3Ds%2BkZi6H_CkZ9-jGi6ROdnq9jz%2Bhjnnf-GebVvw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: How to perform distributed tests on available Jenkins nodes?
Nice, I will try it. Thank you so much, Mark. Victoria On Tue, Apr 28, 2015 at 11:10 AM, Mark Waite mark.earl.wa...@gmail.com wrote: I use the elastic axis plugin to define a multi configuration job which runs a single job on all available slaves. The platform labeler plugin makes platform selection easier with the elastic axis plugin. Mark Waite On Tue, Apr 28, 2015, 9:23 AM Victoria Wei Lei weile...@gmail.com wrote: For every nightly SW build, I want it to be tested on available testing systems. I created Jenkins slaves for these system, and listen to the completion of Jenkins build. I am trying to use Node label Parameter plugin to trigger test on particular system, ideally Jenkins can find whichever an idle system and start test on it. The results are, tests on the default Node can be always started, automatically or manually, but I can never start the test on Possible Node. What's the right way to achieve what I planned. I have my job configuration image attached. Any idea is greatly appreciated. Thanks Victoria -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1a44a41a-b170-4d31-97d5-66becf8e7c5d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/1a44a41a-b170-4d31-97d5-66becf8e7c5d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/3_GV1FKIVAs/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF9HRe%3Ds%2BkZi6H_CkZ9-jGi6ROdnq9jz%2Bhjnnf-GebVvw%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF9HRe%3Ds%2BkZi6H_CkZ9-jGi6ROdnq9jz%2Bhjnnf-GebVvw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAFHFZs_F2zOiijudDqxrkKrDx-jRRk7wzNTP2ZztGbnrY6rQnQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Getting Last promoted build number
I was trying the get the last successful build that was promoted (promotion plugin) into a specific environment out of Jenkins, but not sure how. Gain, not looking for Build Number, but for the build# that was promoted. Ran into some success using the xml/api, but this quickly ended as it doesn't seem i have a way of extracting the most recent in the build. http://JENKINS/job/APPLICATION/promotion/process/QA_ENVIRONMENT/api/xml?depth=1xpath=/*/build[2]/target/number was promising, but can't set the most recent buld number. The xml format seems to change and would have to not do xpath read all and then sort by date somehow. Not good to do. The end result is to put the # on a wiki page that has tons of other information, so linking/iframes not really a good thing, would like to just get the result from a GET and display it on a page. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b1db073-6905-43d0-b1c3-7f33b709139f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Bug Publish over SSH
I can not understand this behavior. In Exec command: cd test / build-38 / project ls echo $ M2 mvn -v This command does the following: 1 - cd test / build-38 / project (in this directory on the remote server) 2 - ls (list the remote server content) 3 - echo $ M2 (Prints $ M2 LOCAL server, where the jenkins is the created) 4 - mvn -v (bash: mvn: command not found, here is also strange because mvn -v works both on the local server, and the remote) Em terça-feira, 28 de abril de 2015 16:25:21 UTC-3, Erick Macedo escreveu: Hi, I'm using the plugin Publish over SSH to run a remote command maven on a linux machine with properly configured maven. However when running mvn command is generated an error bash: mvn: command not found. The plugin is properly connecting the remote machine, as for testing in the Exec command I include the command ifconfig and the same printed data from the remote machine. However, when performing the command echo $ M2_HOME or echo $ PATH in the Exec command he printed the local machine where the information jenkins is the created, not the remote machine. Something very strange. Someone could help me? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/24f4e71d-fba0-468d-8047-44d6f4c48225%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Bug Publish over SSH
It works as the user that you are connecting as? Is there anything in the .bashrc that would set the path to mvn? Perhaps the Publish Over SSH doesn't run in such a way that the .bashrc file is loaded? Check into these things. On Tue, Apr 28, 2015 at 1:19 PM Erick Macedo erickfmac...@gmail.com wrote: I can not understand this behavior. In Exec command: cd test / build-38 / project ls echo $ M2 mvn -v This command does the following: 1 - cd test / build-38 / project (in this directory on the remote server) 2 - ls (list the remote server content) 3 - echo $ M2 (Prints $ M2 LOCAL server, where the jenkins is the created) 4 - mvn -v (bash: mvn: command not found, here is also strange because mvn -v works both on the local server, and the remote) Em terça-feira, 28 de abril de 2015 16:25:21 UTC-3, Erick Macedo escreveu: Hi, I'm using the plugin Publish over SSH to run a remote command maven on a linux machine with properly configured maven. However when running mvn command is generated an error bash: mvn: command not found. The plugin is properly connecting the remote machine, as for testing in the Exec command I include the command ifconfig and the same printed data from the remote machine. However, when performing the command echo $ M2_HOME or echo $ PATH in the Exec command he printed the local machine where the information jenkins is the created, not the remote machine. Something very strange. Someone could help me? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/24f4e71d-fba0-468d-8047-44d6f4c48225%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/24f4e71d-fba0-468d-8047-44d6f4c48225%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVd2--GmN5YBMqPOf6%3DLUnG3JUz%2BASpV0WuRC%3DhL376rMQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins 1.607 - Environment Variables Stuck
Hi Jennifer, I'll test out the restarting master node in on Thursday and post the results... but I feel that Simon and I are having the same issue here. Thanks for the quick replies! VJ On Tuesday, April 28, 2015 at 2:56:23 AM UTC-7, Jennifer Hofmeister wrote: Hi VJ, Hi Simon, Just to sum it up… whatever process runs as a service will only load new env values when restarted. The JNLP and JNLP command line options are spawned from the Jenkins master service, so you’ll want to restart that one after changing your envs so it can pick up new values and pass them on. It’s all about to which Windows service your node goes back to. (ok, you said you already tried this… but just to double-check.) For me (Windows master and slaves), this was always a safe way to fix env problems, but if you’re concrete sure it’s no service configuration thing and still have troubles, maybe try out the “Environment variables” tickbox in the node configuration. You can have global values overwritten by whatever you specify, and these variables are then passed on to every process in the build. Best, Jennifer -Original Message- From: jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] On Behalf Of Simon Richter Sent: Montag, 27. April 2015 22:44 To: jenkins...@googlegroups.com javascript: Subject: Re: Jenkins 1.607 - Environment Variables Stuck Hi, On 27.04.2015 14:57, Jennifer Hofmeister wrote: Does the slave run as a service? If not, it will probably just read the Jenkins service’s old PATH in case that one was not restarted after manipulation. I have the same issue, I can even reboot the slave and the environment stays the same (all variables, not just PATH). It appears that new variables are taken over once when the slave starts, but then remain at their first value when changed later on. Simon -- 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:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/553E9F81.7010603%40hogyros.de. For more options, visit https://groups.google.com/d/optout. From: Varun Jain [mailto:vjai...@gmail.com javascript:] Sent: Montag, 27. April 2015 20:17 To: jenkins...@googlegroups.com javascript: Cc: Jennifer Hofmeister Subject: Re: Jenkins 1.607 - Environment Variables Stuck Hi Jennifer, I've tried it as the service, the JNLP, and the java command line. All of which yielded the same results. I also did try restarting the service. Thanks, VJ On Monday, April 27, 2015 at 5:57:23 AM UTC-7, Jennifer Hofmeister wrote: Hi Varun, Does the slave run as a service? If not, it will probably just read the Jenkins service’s old PATH in case that one was not restarted after manipulation. Best, Jennifer From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Varun Jain Sent: Samstag, 25. April 2015 00:41 To: jenkins...@googlegroups.com Subject: Jenkins 1.607 - Environment Variables Stuck Hey everyone. I'm facing an issue where the environment variables seem stuck and un-updating when running tasks via Jenkins on Windows Slaves. Here are the steps I do to reproduce, and resolve the problem 1. Create new Node and set JUST the home directory 2. Run job with just echo %PATH% 3. Modify PATH, restart Jenkins Slave 4. Echo PATH via command line, outputs as the correct NEW Path 5. Run job with jenkins. OLD path is output Resolution: Delete and recreate slave Thanks, VJ -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3153e714-ee64-490c-b65e-c31812e76864%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/52130dfb-3257-4029-9592-84e5e9b754a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Jenkins 1.607 - Environment Variables Stuck
Hi VJ, Hi Simon, Just to sum it up… whatever process runs as a service will only load new env values when restarted. The JNLP and JNLP command line options are spawned from the Jenkins master service, so you’ll want to restart that one after changing your envs so it can pick up new values and pass them on. It’s all about to which Windows service your node goes back to. (ok, you said you already tried this… but just to double-check.) For me (Windows master and slaves), this was always a safe way to fix env problems, but if you’re concrete sure it’s no service configuration thing and still have troubles, maybe try out the “Environment variables” tickbox in the node configuration. You can have global values overwritten by whatever you specify, and these variables are then passed on to every process in the build. Best, Jennifer -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Simon Richter Sent: Montag, 27. April 2015 22:44 To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins 1.607 - Environment Variables Stuck Hi, On 27.04.2015 14:57, Jennifer Hofmeister wrote: Does the slave run as a service? If not, it will probably just read the Jenkins service’s old PATH in case that one was not restarted after manipulation. I have the same issue, I can even reboot the slave and the environment stays the same (all variables, not just PATH). It appears that new variables are taken over once when the slave starts, but then remain at their first value when changed later on. Simon -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/553E9F81.7010603%40hogyros.de. For more options, visit https://groups.google.com/d/optout. From: Varun Jain [mailto:vjain8...@gmail.com] Sent: Montag, 27. April 2015 20:17 To: jenkinsci-users@googlegroups.com Cc: Jennifer Hofmeister Subject: Re: Jenkins 1.607 - Environment Variables Stuck Hi Jennifer, I've tried it as the service, the JNLP, and the java command line. All of which yielded the same results. I also did try restarting the service. Thanks, VJ On Monday, April 27, 2015 at 5:57:23 AM UTC-7, Jennifer Hofmeister wrote: Hi Varun, Does the slave run as a service? If not, it will probably just read the Jenkins service’s old PATH in case that one was not restarted after manipulation. Best, Jennifer From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Varun Jain Sent: Samstag, 25. April 2015 00:41 To: jenkins...@googlegroups.com Subject: Jenkins 1.607 - Environment Variables Stuck Hey everyone. I'm facing an issue where the environment variables seem stuck and un-updating when running tasks via Jenkins on Windows Slaves. Here are the steps I do to reproduce, and resolve the problem 1. Create new Node and set JUST the home directory 2. Run job with just echo %PATH% 3. Modify PATH, restart Jenkins Slave 4. Echo PATH via command line, outputs as the correct NEW Path 5. Run job with jenkins. OLD path is output Resolution: Delete and recreate slave Thanks, VJ -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3153e714-ee64-490c-b65e-c31812e76864%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAA587D532C45541B62417404F1D22030E81ED58%40you-exch1.younicos.local. For more options, visit https://groups.google.com/d/optout.
Bug Publish over SSH
Hi, I'm using the plugin Publish over SSH to run a remote command maven on a linux machine with properly configured maven. However when running mvn command is generated an error bash: mvn: command not found. The plugin is properly connecting the remote machine, as for testing in the Exec command I include the command ifconfig and the same printed data from the remote machine. However, when performing the command echo $ M2_HOME or echo $ PATH in the Exec command he printed the local machine where the information jenkins is the created, not the remote machine. Something very strange. Someone could help me? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/05c8eac6-eeca-488a-a9ce-3e4a31dae3c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
1.611 not offered for update
According to the Jenkins changelog http://jenkins-ci.org/changelog, Jenkins 1.611 has been out for a few days now. However, my Jenkins is only offering me an upgrade to 1.610 (I'm currently on 1.609). Going to http://jenkins/pluginManager/advanced and hitting Check Now makes no difference. Does someone need to do something additional to make the release visible? Thanks -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6836E1DC2DDC174C9D64B7860E5AF5FC9EE03B9B%40EXCHMBX01.fed.cclrc.ac.uk. For more options, visit https://groups.google.com/d/optout.
Re: Run tests on another machine
Hi, Am 28.04.2015 um 16:30 schrieb Mark Waite: Usually that would mean that the PATH on your Windows machine does not include the maven bin directory. There is a bit of a problem right now with the master overwriting the environment of slaves with an old snapshot of the environment variables. In case Maven was installed after the slave connected to the master for the first time, this might be the problem (and deleting the node in the master and recreating it fixes it). Simon -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/553FA1FC.4020604%40hogyros.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: Jenkins 1.607 - Environment Variables Stuck
Hi Jennifer, Just to sum it up… whatever process runs as a service will only load new env values when restarted. That is expected behaviour, yes. The JNLP and JNLP command line options are spawned from the Jenkins master service, so you’ll want to restart that one after changing your envs so it can pick up new values and pass them on. So if the default environment on the slave changes, I need to restart the slave first for it to pick it up (expected), and then subsequently restart the master to make it re-fetch the environment from the slave, which is then written back during execution? I've had success getting new environment variables accepted by deleting the node from the master config an recreating them with the same settings. When the slave then reconnects, the new environment is accepted (but also sticky). I think I have also restarted the master at one point and didn't get an updated environment. I use a Linux master and Windows slaves BTW. Simon -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/553FA3CE.9030609%40hogyros.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: Run tests on another machine
Hi , again thanks for the help. When you talk master and slave, the Master is a server installed Jenkins and the Slave any other server (even without the installed jenkins)? More to the point, Maven has been configured on another server before the connection then I do not believe that this is the problem, perhaps a limitation of the plugin? thank you Em terça-feira, 28 de abril de 2015 08:37:30 UTC-3, Erick Macedo escreveu: Hii, I have a build running on jenkins and I'm using maven. I wonder how I could run my screen test on a different machine that is the jenkins, the bamboo that is setting up a possible agent. I need this configuration because the machine that is the jenkins is a CentOS without graphics, and my screen tests need to be on a windows machine with a browser. Could someone help me or have some material for this? thank -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3efd53eb-c7af-4f80-a9d5-e5c9e15a5abe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
