How to manipulate PATH for jenkins outside of jenkins
Hi, I need to run jobs where the PATH is set by the server itself (e.g. by .bashrc), so it can be manipulated by chef/puppet/... At this point, I can't figure out how to do this, since jenkins runs the shell scripts inside a job as non-interactive, non-login shells. Part of the jobs are running bundle install and bundle exec compass compile, which requires the PATH to be set properly. What is the best way to do this, keeping in mind server install and manipulation is through provisioning tools (no manual steps)? I have researched the BASH_ENV, it doesn't seem usable. I have tried using a /etc/profile.d/path.sh file and sourcing /etc/profile as a first step in the build process, that works, but seems to be very funky. -- 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/27cec6b5-e8fc-419f-b624-3ab23fa99e9a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to manipulate PATH for jenkins outside of jenkins
Also important. I use phing. Which means that sourcing a file won't help, since that is done in an Exectask, which is isolated from the other tasks. I can't source a file first and then run another task expecting the env variables to be manipulated. On Monday, 4 May 2015 09:59:39 UTC+2, Dieter Blomme wrote: Hi, I need to run jobs where the PATH is set by the server itself (e.g. by .bashrc), so it can be manipulated by chef/puppet/... At this point, I can't figure out how to do this, since jenkins runs the shell scripts inside a job as non-interactive, non-login shells. Part of the jobs are running bundle install and bundle exec compass compile, which requires the PATH to be set properly. What is the best way to do this, keeping in mind server install and manipulation is through provisioning tools (no manual steps)? I have researched the BASH_ENV, it doesn't seem usable. I have tried using a /etc/profile.d/path.sh file and sourcing /etc/profile as a first step in the build process, that works, but seems to be very funky. -- 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/ad95b404-ee0c-4cfd-acda-b0312e24d211%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[ Help ] Save Restore Running Job state
Hi, I ran Reload Configuration from Disk on my jenkins server after modifying a config.xml file. However, on reload I found all running jobs are marked as finished abruptly. Is there a way to restore / save-and-reload the running jobs in such a scenario ? -Milan -- 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/a983ff69-a68f-4273-a5b1-cd7d28ec0f37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ Help ] Save Restore Running Job state
This should not happen. If this is a recent Jenkins version (no older than six weeks or so), please file a bug. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue On 04.05.2015, at 10:04, Milan Satpathy satpathy.mila...@gmail.com wrote: Hi, I ran Reload Configuration from Disk on my jenkins server after modifying a config.xml file. However, on reload I found all running jobs are marked as finished abruptly. Is there a way to restore / save-and-reload the running jobs in such a scenario ? -Milan -- 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/a983ff69-a68f-4273-a5b1-cd7d28ec0f37%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/9F076FEB-8065-415D-BE86-E8E14895548D%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Git Publisher: EnvVar in tag name
I am trying to use Git Publisher to create a git tag, but I cannot get it to use an Environment variable in the tag name: Is it even possible to supply an Environment Variable as part of a Git tag name? git tag -l v$VERSION # timeout=10 git tag -a -f -m Jenkins Git plugin tagging with v$VERSION v$VERSION # timeout=10 Pushing tag v$VERSION to repo origin git --version # timeout=10 git -c core.askpass=true push ssh://g...@git.company.com/packages/myLib.git v$VERSION ERROR: Failed to push tag v$VERSION to origin hudson.plugins.git.GitException: Command git -c core.askpass=true push ssh://g...@git.company.com/packages/myLib.git v$VERSION returned status code 1: stdout: stderr: remote: invalid characters in ref or filename: refs/tags/v$VERSION remote: error: hook declined to update refs/tags/v$VERSION To ssh://g...@git.company.com/packages/myLib.git ! [remote rejected] v$VERSION - v$VERSION (hook declined) error: failed to push some refs to 'ssh://g...@git.company.com/packages/myLib.git' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1663) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:325) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to Development-openSUSE-x86_64(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:753) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy87.execute(Unknown Source) at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:306) at hudson.plugins.git.GitPublisher$1.endBuild(GitPublisher.java:147) at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:407) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1766) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) -- 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/cd8ae789-fd97-4feb-afa2-4135ce4ec89e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins master and slave workspace directory
Hi,
I'm testing Jenkins on Master-Slave configuration, but I didn't configure
slave workspace directory. I set FS root on the slave, but Jenkins added
workspace word to the path.
Example:
FSRoot: D:\JK
output: Building remotely on jenkins-win-fin in workspace d:\JK\*workspace*
\Main-Win-FIN
This path is too long for my project, so I would like to use shorter path.
Thanks in advanced.
Viktor Józsa
2013. április 26., péntek 10:29:33 UTC+2 időpontban Adam PAPAI a következőt
írta:
Why don't you use the $WORKSPACE variable? It always points to the
directory where your source code is - or in other words where your job is
located.
Aswini Rajasekaran javascript:
April 26, 2013 10:27 AM
Hi Adam,
I am running tests on both master and slaves and am specifying the test
location directory in user-extensions.js file in selenium. As the
workspaces are different in master and slave, I can't run the same job in
both master and slave depending on the load on master. If I can't make this
to run on any node, then I have to end up tying it to one node which
completely nullifies the parallel execution concept.
Regards,
Aswini
On Friday, 26 April 2013 09:22:58 UTC+1, Adam PAPAI wrote: --
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.
Adam PAPAI javascript:
April 26, 2013 10:22 AM
What is the reason why do you want it to be the same?
Anyway on the master you shouldn't run tests. Only on the slaves.
The reason is:
on the master under the jenkinsrootjobs/jobname there are the meta
infos, build history, config.xml and so on, so the realy workspace is
under the jobname/workspace
On the slaves, Jenkins does not store meta info, build history, configs,
so that's why its located under: jenkinsroot/jobs/workspace/jobname
--
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.
Aswini Rajasekaran javascript:
April 25, 2013 2:04 PM
Hi all,
I have a small question, this might sound silly but I am not able to find
the answer for this.
In my jenkins master node, the workspace directory is defined as
jenkinsroot/jobs/*jobname/workspace* - this is configured as
${ITEM_ROOTDIR}/workspace in jenkins master.
whereas in slave, the workspace directory gets stored like this
jenkinsroot/jobs/*workspace/jobname*
I want both the workspace directory, in master and slave to be consistent.
Is there anything that I can do to make this happen?
Thanks in advance.
Regards,
Aswini
--
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.
--
Adam PAPAI
E-mail: wo...@wooh.hu javascript:
Phone: +3630 3355735
Web: http://www.wooh.hu
--
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/c1f1d444-12cb-4724-861a-e0ca6b009631%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jenkins docker image stucks on start-up
I'm trying to use the official Jenkins docker image https://registry.hub.docker.com/_/jenkins/but it seems to stuck after/while setting agent port during start-up (see below output). http://localhost:8080 is not reachable.. mark@MARK-PC ~ $ docker run -p 8080:8080 jenkins Unable to find image 'jenkins:latest' locally latest: Pulling from jenkins 511136ea3c5a: Pull complete ] 32 B/32 BB 848d84b4b2ab: Pull complete ] 50.97 MB/50.97 MBB 71d9d77ae89e: Pull complete ] 32 B/32 BB 34664741b33f: Pull complete ] 32 B/32 BB bd8bd16075a0: Pull complete ] 197.7 MB/197.7 MBB c15d04694341: Pull complete ] 15.33 MB/15.33 MBB 5e97c669e8ad: Pull complete ] 32 B/32 BB b872be1ed4e2: Pull complete ] 4.396 kB/4.396 kBB dc840aab2066: Pull complete ] 32 B/32 BB adc3c45c3240: Pull complete ]180 B/180 BB 2d759671b8eb: Pull complete ]347 B/347 BB f89db0b7f3f4: Pull complete ] 32 B/32 BB 0f90d7a31266: Pull complete ] 62.53 MB/62.53 MBB 436ac75860fa: Pull complete ] 32 B/32 BB 918ffc77f2ce: Pull complete ]351 B/351 BB a3f93642995b: Pull complete ] 32 B/32 BB 1b8eb55d3cb2: Pull complete ] 32 B/32 BB 5d31e1363108: Pull complete ] 32 B/32 BB 0b2e95c97d30: Pull complete ]749 B/749 BB 8b8c22b711b0: Pull complete ] 32 B/32 BB 1520f72eb8b6: Already exists ===]522 B/522 BB jenkins:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security. Digest: sha256: a8383bdcd35d15b4a88e25e193ffb05f5304df3e8d9f4d81a90f03eb454e7f49 Status: Downloaded newer image for jenkins:latest /usr/share/jenkins/ref/init.groovy.d/tcp-slave-agent-port.groovy /usr/share/jenkins/ref/init.groovy.d/tcp-slave-agent-port.groovy - init. groovy.d/tcp-slave-agent-port.groovy copy init.groovy.d/tcp-slave-agent-port.groovy to JENKINS_HOME Running from: /usr/share/jenkins/jenkins.war webroot: EnvVars.masterEnvVars.get(JENKINS_HOME) May 04, 2015 9:37:11 AM winstone.Logger logInternal INFO: Beginning extraction from war file May 04, 2015 9:37:12 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: jetty-winstone-2.8 May 04, 2015 9:37:13 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars. get(JENKINS_HOME) May 04, 2015 9:37:14 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: Started SelectChannelConnector@0.0.0.0:8080 May 04, 2015 9:37:14 AM winstone.Logger logInternal INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled May 04, 2015 9:37:14 AM jenkins.InitReactorRunner$1 onAttained INFO: Started initialization May 04, 2015 9:37:21 AM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins May 04, 2015 9:37:21 AM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins May 04, 2015 9:37:21 AM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins May 04, 2015 9:37:21 AM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions May 04, 2015 9:37:21 AM jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs May 04, 2015 9:37:21 AM jenkins.util.groovy.GroovyHookScript execute INFO: Executing /var/jenkins_home/init.groovy.d/tcp-slave-agent-port.groovy May 04, 2015 9:37:23 AM org.jenkinsci.main.modules.sshd.SSHD start INFO: Started SSHD at port 54711 May 04, 2015 9:37:23 AM hudson.model.AsyncPeriodicWork$1 run INFO: Started Download metadata May 04, 2015 9:37:23 AM jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization May 04, 2015 9:37:23 AM hudson.WebAppMain$3 run INFO: Jenkins is fully up and running May 04, 2015 9:37:27 AM hudson.model.UpdateSite updateData INFO: Obtained the latest update center data file for UpdateSource default May 04, 2015 9:37:27 AM hudson.model.DownloadService$Downloadable load INFO: Obtained the updated data file for hudson.tasks.Maven.MavenInstaller May 04, 2015
Re: Jenkins docker image stucks on start-up
I would guess the problem is due to using boot2docker, i.e. the port won't be exposed on localhost, but on a separate network interface. See the documentation: https://docs.docker.com/installation/windows/#container-port-redirection Regards, Chris On 04/05/15 11:43, Marco K. wrote: I'm trying to use the official Jenkins docker image https://registry.hub.docker.com/_/jenkins/but it seems to stuck after/while setting agent port during start-up (see below output). http://localhost:8080 is not reachable.. | |mark@MARK-PC ~ |$ docker run -p 8080:8080jenkins Unableto find image 'jenkins:latest'locally latest:Pullingfromjenkins 511136ea3c5a:Pullcomplete ]32B/32BB 848d84b4b2ab:Pullcomplete ]50.97MB/50.97MBB 71d9d77ae89e:Pullcomplete ]32B/32BB 34664741b33f:Pullcomplete ]32B/32BB bd8bd16075a0:Pullcomplete ]197.7MB/197.7MBB c15d04694341:Pullcomplete ]15.33MB/15.33MBB 5e97c669e8ad:Pullcomplete ]32B/32BB b872be1ed4e2:Pullcomplete ]4.396kB/4.396kBB dc840aab2066:Pullcomplete ]32B/32BB adc3c45c3240:Pullcomplete ]180B/180BB 2d759671b8eb:Pullcomplete ]347B/347BB f89db0b7f3f4:Pullcomplete ]32B/32BB 0f90d7a31266:Pullcomplete ]62.53MB/62.53MBB 436ac75860fa:Pullcomplete ]32B/32BB 918ffc77f2ce:Pullcomplete ]351B/351BB a3f93642995b:Pullcomplete ]32B/32BB 1b8eb55d3cb2:Pullcomplete ]32B/32BB 5d31e1363108:Pullcomplete ]32B/32BB 0b2e95c97d30:Pullcomplete ]749B/749BB 8b8c22b711b0:Pullcomplete ]32B/32BB 1520f72eb8b6:Alreadyexists ===]522B/522BB jenkins:latest:Theimage you are pulling has been verified.Important:image verification isa tech preview feature andshould notbe relied on to provide security. Digest:sha256:a8383bdcd35d15b4a88e25e193ffb05f5304df3e8d9f4d81a90f03eb454e7f49 Status:Downloadednewer image forjenkins:latest /usr/share/jenkins/ref/init.groovy.d/tcp-slave-agent-port.groovy /usr/share/jenkins/ref/init.groovy.d/tcp-slave-agent-port.groovy -init.groovy.d/tcp-slave-agent-port.groovy copy init.groovy.d/tcp-slave-agent-port.groovy to JENKINS_HOME Runningfrom:/usr/share/jenkins/jenkins.war webroot:EnvVars.masterEnvVars.get(JENKINS_HOME) May04,20159:37:11AM winstone.LoggerlogInternal INFO:Beginningextraction fromwar file May04,20159:37:12AM org.eclipse.jetty.util.log.JavaUtilLoginfo INFO:jetty-winstone-2.8 May04,20159:37:13AM org.eclipse.jetty.util.log.JavaUtilLoginfo INFO:NO JSP Supportfor,did notfind org.apache.jasper.servlet.JspServlet Jenkinshome directory:/var/jenkins_home found at:EnvVars.masterEnvVars.get(JENKINS_HOME) May04,20159:37:14AM org.eclipse.jetty.util.log.JavaUtilLoginfo INFO:StartedSelectChannelConnector@0.0.0.0:8080 May04,20159:37:14AM winstone.LoggerlogInternal INFO:WinstoneServletEnginev2.0running:controlPort=disabled May04,20159:37:14AM jenkins.InitReactorRunner$1onAttained INFO:Startedinitialization May04,20159:37:21AM jenkins.InitReactorRunner$1onAttained INFO:Listedall plugins May04,20159:37:21AM jenkins.InitReactorRunner$1onAttained INFO:Preparedall plugins May04,20159:37:21AM jenkins.InitReactorRunner$1onAttained INFO:Startedall plugins May04,20159:37:21AM jenkins.InitReactorRunner$1onAttained INFO:Augmentedall extensions May04,20159:37:21AM jenkins.InitReactorRunner$1onAttained INFO:Loadedall jobs May04,20159:37:21AM jenkins.util.groovy.GroovyHookScriptexecute INFO:Executing/var/jenkins_home/init.groovy.d/tcp-slave-agent-port.groovy May04,20159:37:23AM org.jenkinsci.main.modules.sshd.SSHD start INFO:StartedSSHD at port 54711 May04,20159:37:23AM hudson.model.AsyncPeriodicWork$1run INFO:StartedDownloadmetadata May04,20159:37:23AM jenkins.InitReactorRunner$1onAttained INFO:Completedinitialization May04,20159:37:23AM hudson.WebAppMain$3run INFO:Jenkinsisfully up andrunning May04,20159:37:27AM hudson.model.UpdateSiteupdateData INFO:Obtainedthe latest update center data file forUpdateSourcedefault May04,20159:37:27AM hudson.model.DownloadService$Downloadableload INFO:Obtainedthe updated data file forhudson.tasks.Maven.MavenInstaller May04,20159:37:28AM hudson.model.DownloadService$Downloadableload
Re: Why is a release candidate plugin update available from the stable update site?
IIRC only plugins that have a alpha or beta version are filtered out of the stable update center and shown in the experimental update center. RC versions are not considered experimental. On Thursday, 30 April 2015 18:47:24 UTC+1, Ullrich Hafner wrote: I don’t think that plugins are yet part of the LTS releases. So you see all plugin updates in both channels. Am 30.04.2015 um 11:46 schrieb Benjamin benjamin...@gmail.com javascript:: Hi, I configured the Update Site to use the stable update site ( http://updates.jenkins-ci.org/stable/update-center.json): https://lh3.googleusercontent.com/-N-vicoPWtgg/VUH4rQxLhhI/SjA/cwtKv1m2DAw/s1600/2015-04-30%2B11_40_44-Clipboard.png I just discovered that a *Docker plugin* update is available from 0.8 to *0.9.0-rc1* https://lh3.googleusercontent.com/-38fp0iMwctw/VUH5GIa1lXI/SjI/FcQJBnStkUY/s1600/2015-04-30%2B11_41_22-Update%2BCenter%2B%5BJenkins%5D.png I would not expect a release candidate to appear for the *stable *update site. Is this intended behavior? If not, how could I help to get this issue? How is the update-center.json content generated/curated? Best regards Benjamin -- 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/131c716d-1a83-45ed-929e-4ff707aed92d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/131c716d-1a83-45ed-929e-4ff707aed92d%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/1d4e5156-f186-407f-9747-a313a16a07f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins docker image stucks on start-up
Thank you very much, Chris. I'm able to reach Jenkins at http://192.168.59.103:8080 which is the default IP for boot2docker users according to the link. Kind regards, Marco Am Montag, 4. Mai 2015 12:35:02 UTC+2 schrieb Christopher Orr: I would guess the problem is due to using boot2docker, i.e. the port won't be exposed on localhost, but on a separate network interface. See the documentation: https://docs.docker.com/installation/windows/#container-port-redirection Regards, Chris -- 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/649c4858-a261-4a86-871c-7a22a225ffc6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins 1.607 - Environment Variables Stuck
Hi Henk, Setting the variable within the Jenkins job works properly (both SET and SETX), but the problem is that when we modify the windows variables (a la button clicking on Windows), restart the slave, the master (restarting the Jenkins client/master and/or rebooting), the environment variables modified on the Jenkins Slave (Windows) are not updated within Jenkins. It's like Jenkins, on first run, snapshots the environment variables and never loads them from the OS again.\ Thanks, VJ On Wednesday, April 29, 2015 at 4:28:36 AM UTC-7, Henk van Voorthuijsen wrote: Varun, Have you tried setting the variable with SETX instead of SET ? Henk -- 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/b3c6acec-ca58-49ff-869b-150aadec9b61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Anyone have the direct link to the unmigrate instructions?
I am one of those that upgraded to a new version that changes the way builds are stored on the drive only to find that some of the plugins would not work so I was forced to downgrade. As expected, I ran into the incompatibility issue and now I am looking for the unmigrate instructions that are mentioned in other posts. My problem is I can't find them... Can someone point me to the exact link that shows the instructions? https://issues.jenkins-ci.org/browse/JENKINS-24380 is what I was looking at initially... I just can't find the actual instructions / script. I hope I am just missing something obvious. Thanks for the 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/96df00cb-3e39-4fa0-8879-3cf9a6c05d32%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Need help on puppet integration with Jenkins
Hi all, I need to deploy my code in weblogic server. I have written any script to build artifact . When I'm trying to deploy the artifact I'm getting error . So I was suggested to use puppet . I have downloaded puppet plugin and deployment notification plugin as first step . Could any of you please explain me how puppet will work ? And how i should use these plugins? Will they automatically deploy artifact or some code has to be written. If so where should I place the code ? And what code is to be written . I need an example to deploy an artifact in a sever . Thanks in advance . -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5c1c140f-03d0-436b-b3fb-15c1531bc726%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Got no such job when trigger a build with jenkins-cli 1.525 as an administrator permission after enable LDAP and role strategy security
Is this issue solved I have the same problem: https://lh3.googleusercontent.com/-Lxgl0MhQDL0/VUfJyxCP7pI/gMM/CdAbs5cnIwY/s1600/bug1.PNG https://lh3.googleusercontent.com/-0P1EXcyngjA/VUfJ2fWSBgI/gMU/VYOQJALbgfs/s1600/bug2.PNG On Thursday, September 5, 2013 at 9:58:22 PM UTC-5, viola lu wrote: I have setup a jenkins server and enable LDAP and role strategy security. I can build jobs in UI as administrator account. But if i trigger builds via jenkins-cli , it failed, and reported an error no such job . icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ version --username ** --password ** 1.525 icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ list-jobs --username ** --password ** Setup_Jenkins test testSlave1 Upload_Artifacts_and_Result icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ build test --username ** --password ** *No such job 'test'* Is this a bug? -- 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/7c9d3c0f-483a-4b8a-9eb1-bb865bf891d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Got no such job when trigger a build with jenkins-cli 1.525 as an administrator permission after enable LDAP and role strategy security
Looks like this is the known issue https://issues.jenkins-ci.org/browse/JENKINS-12543 which is also where a workaround is provided in the comments. On 04.05.2015, at 21:34, David Dominguez davdo...@gmail.com wrote: Is this issue solved I have the same problem: On Thursday, September 5, 2013 at 9:58:22 PM UTC-5, viola lu wrote: I have setup a jenkins server and enable LDAP and role strategy security. I can build jobs in UI as administrator account. But if i trigger builds via jenkins-cli , it failed, and reported an error no such job . icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ version --username ** --password ** 1.525 icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ list-jobs --username ** --password ** Setup_Jenkins test testSlave1 Upload_Artifacts_and_Result icap@icap-build-linux-5:/icap/jazz_build/build/Core_Sonar/ant_build/lib$ java -jar jenkins-cli.jar -s http://9.111.211.30:8080/ build test --username ** --password ** No such job 'test' Is this a bug? -- 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/7c9d3c0f-483a-4b8a-9eb1-bb865bf891d9%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/A5BBF758-30DF-4F51-8909-1D2055FA8018%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
JIRA Plugin not adding comment on downstream builds
I have been trying to use the JIRA Plugin https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin to integrate Jenkins and JIRA. From what I've read, the JIRA plugin should be able to use fingerprint information to update the JIRA ticket when a downstream build runs that uses that artifact. ex: a fix is made to projectA and the build updates the relevant JIRA ticket. After projectA is built, projectB (which depends on projectA) builds, and that should also update the JIRA ticket. However, I am only getting an update on the JIRA ticket from the build of projectA and not from the both (the projectB build is the one I really care about). I double checked the fingerprint of the artifact in Jenkins and it does recognize the relationship between the two builds, and I made sure both jobs were configured with the Update relevant JIRA issues post build action. I'm not sure if I have mis-understood the description of the plugin and this isn't possible, or if I just simply have something mis-configured. After searching around online, I couldn't find any similar issues with the plugin, so I'm coming here to see if anyone uses that plugin in this way, and if so if there is any special configuration that needs to be done to get it to work that I may have missed. -- 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/68c5ff88-6a82-47af-8581-6490a2f61e19%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
