[JIRA] [envinject-plugin] (JENKINS-29811) File used for injection is first looked up in directory containing workspace
Title: Message Title Wilco Greven commented on JENKINS-29811 Re: File used for injection is first looked up in directory containing workspace This is a duplicate of JENKINS-23666. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven commented on JENKINS-22679 Regression, Promoted builds plugin not expanding job parameters on immediate promote after build. Yep, it's waiting there for almost half a year now. It's pretty frustrating that it still hasn't been merged. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven updated JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Change By: Wilco Greven (13/Feb/15 8:25 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven commented on JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK What bothers me is that the behaviour of the job is changed unexpectedly. When I configure a job to use a specific JVM, I expect that it will always use that JVM. This is especially important for test jobs. Logging it would already be a big improvement. BTW, I do think the fact that JAVA_HOME is set empty is an actual bug. If Jenkins falls back to the system JDK, JAVA_HOME should be set accordingly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven updated JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Change By: Wilco Greven (13/Feb/15 8:29 AM) Description: InoticedthatwhenthereisnoinstalleravailableforaJDK,theJAVA_HOMEenvironmentvariablewillbeemptyintheenvironmentofabuild.ThiswillhappenforexamplewhenthereisnoinstallerconfiguredforaJDK.Inthatcaseitsnothardtofindthecause.ButforthecaseIdescribebelowitsmuchhardertofindoutwhyJAVA_HOMEisempty.ThereforeIthink abuild logging should failorJAVA_HOMEshouldnot be set improved whenaspecificJDKisconfiguredforthatbuildandnoinstallerisavailableforthatJDK. FurthermoreJAVA_HOMEshouldbesettomatchthedefaultJVM. Herearethestepstoreproduce:-ConfiguretwoJDKs,namedJDK1andJDK2(becauseifyouhaveonlyoneJDKyoucantselectoneinajob)-AddanExtract*.zip/*.tar.gzinstallertoJDK1andsetthelabelforthisinstallertojdk1,soitwontbeavailableforinstallationonnodestowhichthislabelisnotassigned-CreateafreestylejobandselectJDK1asJDK-RunthejobandcheckthatJAVA_HOMEisempty This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven created JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Feb/15 6:16 PM Description: I noticed that when there is no installer available for a JDK, the JAVA_HOME environment variable will be empty in the environment of a build. This will happen for example when there is no installer configured for a JDK. In that case it's not hard to find the cause. But for the case I describe below it's much harder to find out why JAVA_HOME is empty. Therefore I think a build should fail or JAVA_HOME should not be set when a specific JDK is configured for that build and no installer is available for that JDK. Here are the steps to reproduce: Configure two JDK's, named JDK1 and JDK2 (because if you have only one JDK you can't select one in a job) Add an 'Extract .zip/.tar.gz' installer to JDK1 and set the label for this installer to 'jdk1', so it won't be available for installation on nodes to which this label is not assigned Create a freestyle job and select JDK1 as JDK Run the job and check that JAVA_HOME is empty Environment: Jenkins 1.580.1 Project: Jenkins Priority: Minor Reporter: Wilco Greven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24872) Job fails when using a blocking parameterized remote trigger with a job name containing a token
Wilco Greven commented on JENKINS-24872 Job fails when using a blocking parameterized remote trigger with a job name containing a token See pull request https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24872) Job fails when using a blocking parameterized remote trigger with a job name containing a token
Wilco Greven created JENKINS-24872 Job fails when using a blocking parameterized remote trigger with a job name containing a token Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger Created: 26/Sep/14 12:48 PM Description: We have a Jenkins job with a parameterized-remote-trigger build step. The trigger is configured to block until the remote triggered projects finish their builds. The remote job name contains a token. What we see is that the remote job is triggered succesfully. But polling the status of the remote job fails, because in the URL that is used for polling the token is not substituted. Environment: jenkins 1.565.2 parameterized-remote-trigger 2.1.3 Project: Jenkins Priority: Major Reporter: Wilco Greven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project
Wilco Greven closed JENKINS-22196 as Fixed Validation error when choosing a valid project as manual downstream project Fixed in build-pipeline 1.4.3. Change By: Wilco Greven (08/Aug/14 7:30 AM) Status: Open Closed Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven closed JENKINS-17961 as Fixed URLTrigger does not poll when URL starts with environment variable Change By: Wilco Greven (08/Aug/14 7:32 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Wilco Greven updated JENKINS-23666 Inject environment variables build step uses the wrong property file Change By: Wilco Greven (04/Jul/14 11:55 AM) Description: Wehaveajobthatusesaninjectenvironmentvariablesbuildsteptoinjectenvironmentvariablesfromapropertyfiletarget/build.properties.Thispropertyfilewasverifiedtoexistintheworkspace.Atfirstthisworkedfine.Thenbyaccidentsomeonecreatedafile/target/build.propertiesintherootofthefilesystem.Whathappenednextisthattheinjectenvironmentvariablesbuildstepwouldusethisnewfileinsteadofthefileinthejobsworkspace. Thecauseofthisbehaviouristhatthepluginfirsttriestoresolvethepathasarelativepathagainstthecurrentworkingdirectory(ofthejenkinsinstance).Inourcasethecurrentworkingdirectorywastherootdirectory,whichexplainswhyitused/target/build.properties.Onlywhenthisfiledoesntexistitwilllookupthepropertyfilerelativetotheworkspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Wilco Greven updated JENKINS-23666 Inject environment variables build step uses the wrong property file Change By: Wilco Greven (04/Jul/14 11:56 AM) Description: Wehaveajobthatusesaninjectenvironmentvariablesbuildsteptoinjectenvironmentvariablesfromapropertyfiletarget/build.properties.Thispropertyfilewasverifiedtoexistintheworkspace.Atfirstthisworkedfine.Thenbyaccidentsomeonecreatedafile/target/build.propertiesintherootofthefilesystem.Whathappenednextisthattheinjectenvironmentvariablesbuildstepwouldusethisnewfileinsteadofthefileinthejobsworkspace.Thecauseofthisbehaviouristhatthepluginfirsttriestoresolvethepathasarelativepathagainstthecurrentworkingdirectory(ofthejenkinsinstance).Inourcasethecurrentworkingdirectorywastherootdirectory,whichexplainswhyitused/target/build.properties.Onlywhenthisfiledoesntexistitwilllookupthepropertyfilerelativetotheworkspace. Myexpectationwasthatrelativepathswouldonlybelookedupintheworkspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
commented on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion that triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion that triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will automatically run job2. But job2 will be run with param1=${param1} which is not correct.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
edited a comment on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will now automatically start job2. But job2 will be run with param1=${param1} which is not correct.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
edited a comment on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will automatically run job2. But job2 will be run with param1=${param1} which is not correct.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
edited a comment on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. Reverting to 2.16 fixes the problem. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will now automatically start job2. But job2 will be run with param1=${param1} which is not correct.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Wilco Greven created JENKINS-23666 Inject environment variables build step uses the wrong property file Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 03/Jul/14 10:51 AM Project: Jenkins Priority: Major Reporter: Wilco Greven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Wilco Greven
updated JENKINS-23666
Inject environment variables build step uses the wrong property file
Change By:
Wilco Greven
(03/Jul/14 10:53 AM)
Environment:
{noformat}Naam↓Waardeawt.toolkit sun.awt.X11.XToolkitcatalina.base /opt/tomcat6catalina.home /opt/tomcat6catalina.useNaming truecom.sun.management.jmxremote com.sun.management.jmxremote.authenticate falsecom.sun.management.jmxremote.port 9003com.sun.management.jmxremote.ssl falsecommon.loader ${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jarfile.encoding UTF-8file.encoding.pkg sun.iofile.separator /guice.disable.misplaced.annotation.check truehttp.nonProxyHosts *.rsghttp.proxyHost ibraccsqd01.nl.rsghttp.proxyPort 8080hudson.slaves.WorkspaceList _java.awt.graphicsenv sun.awt.X11GraphicsEnvironmentjava.awt.headless truejava.awt.printerjob sun.print.PSPrinterJobjava.class.path /opt/tomcat6/bin/bootstrap.jarjava.class.version 51.0java.endorsed.dirs /opt/tomcat6/endorsedjava.ext.dirs /usr/java/jdk1.7.0_51/jre/lib/ext:/usr/java/packages/lib/extjava.home /usr/java/jdk1.7.0_51/jrejava.io.tmpdir /opt/tomcat6/tempjava.library.path /usr/lib/oracle/11.2/client/lib:/usr/java/packages/lib/i386:/lib:/usr/libjava.naming.factory.initial org.apache.naming.java.javaURLContextFactoryjava.naming.factory.url.pkgs org.apache.namingjava.rmi.server.hostname java.rmi.server.randomIDs truejava.runtime.name Java(TM)SERuntimeEnvironmentjava.runtime.version 1.7.0_51-b13java.security.egd file:///dev/urandomjava.specification.name JavaPlatformAPISpecificationjava.specification.vendor OracleCorporationjava.specification.version 1.7java.util.logging.config.file /opt/tomcat6/conf/logging.propertiesjava.util.logging.manager org.apache.juli.ClassLoaderLogManagerjava.vendor OracleCorporationjava.vendor.url http://java.oracle.com/java.vendor.url.bug http://bugreport.sun.com/bugreport/java.version 1.7.0_51java.vm.info mixedmodejava.vm.name JavaHotSpot(TM)ServerVMjava.vm.specification.name JavaVirtualMachineSpecificationjava.vm.specification.vendor OracleCorporationjava.vm.specification.version 1.7java.vm.vendor OracleCorporationjava.vm.version 24.51-b03jna.platform.library.path /usr/lib:/libline.separator mail.smtp.sendpartial truemail.smtps.sendpartial trueos.arch i386os.name Linuxos.version 2.6.18-308.el5PAEpackage.access sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.,sun.beans.package.definition sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.path.separator :securerandom.source file:/dev/./urandomserver.loader shared.loader sun.arch.data.model 32sun.boot.class.path /usr/java/jdk1.7.0_51/jre/lib/resources.jar:/usr/java/jdk1.7.0_51/jre/lib/rt.jar:/usr/java/jdk1.7.0_51/jre/lib/sunrsasign.jar:/usr/java/jdk1.7.0_51/jre/lib/jsse.jar:/usr/java/jdk1.7.0_51/jre/lib/jce.jar:/usr/java/jdk1.7.0_51/jre/lib/charsets.jar:/usr/java/jdk1.7.0_51/jre/lib/jfr.jar:/usr/java/jdk1.7.0_51/jre/classessun.boot.library.path /usr/java/jdk1.7.0_51/jre/lib/i386sun.cpu.endian littlesun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManagersun.io.unicode.encoding UnicodeLittlesun.java.command org.apache.catalina.startup.Bootstrapstartsun.java.launcher SUN_STANDARDsun.jnu.encoding UTF-8sun.management.compiler HotSpotTieredCompilerssun.os.patch.level unknownsvnkit.http.methods Digest,Basic,NTLM,Negotiatesvnkit.ssh2.persistent falsetomcat.util.buf.StringCache.byte.enabled trueuser.country USuser.dir /user.home /rootuser.language enuser.name rootuser.timezone Europe/AmsterdamOmgevingsvariabelenNaam↓Waarde_ /opt/jdk/bin/javaJENKINS_HOME /data/jenkins-workLANG en_US.UTF-8LD_LIBRARY_PATH /usr/lib/oracle/11.2/client/libNLSPATH /usr/dt/lib/nls/msg/%L/%N.catPATH /sbin:/usr/sbin:/bin:/usr/binPWD /SHLVL 2TERM xtermTNS_ADMIN /usr/lib/oracle/11.2/client/network/adminXFILESEARCHPATH /usr/dt/app-defaults/%L/DtInvoegtoepassingenNaam↓VersieIngeschakeldPinnedactive-directory 1.37 true falseanalysis-core 1.56 true falseant 1.2 true trueantisamy-markup-formatter 1.1 true trueartifact-promotion 0.2.6 true falseasync-http-client 1.7.8 true falseawseb-deployment-plugin 0.0.3 true falsebuild-flow-plugin 0.12 true falsebuild-name-setter 1.3 true falsebuild-pipeline-plugin 1.4.2 true
[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Wilco Greven
updated JENKINS-23666
Inject environment variables build step uses the wrong property file
Change By:
Wilco Greven
(03/Jul/14 11:06 AM)
Environment:
{noformat}Naam↓Waardeawt.toolkit sun.awt.X11.XToolkitcatalina.base /opt/tomcat6catalina.home /opt/tomcat6catalina.useNaming truecom.sun.management.jmxremote com.sun.management.jmxremote.authenticate falsecom.sun.management.jmxremote.port 9003com.sun.management.jmxremote.ssl falsecommon.loader ${catalina.base}/lib
linux
,
${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jarfile.encoding UTF-8file.encoding.pkg sun.iofile.separator /guice.disable.misplaced.annotation.check truehttp.nonProxyHosts *.rsghttp.proxyHost ibraccsqd01.nl.rsghttp.proxyPort 8080hudson.slaves.WorkspaceList _java.awt.graphicsenv sun.awt.X11GraphicsEnvironmentjava.awt.headless truejava.awt.printerjob sun.print.PSPrinterJobjava.class.path /opt/tomcat6/bin/bootstrap.jarjava.class.version 51.0java.endorsed.dirs /opt/tomcat6/endorsedjava.ext.dirs /usr/java/jdk1.7.0_51/jre/lib/ext:/usr/java/packages/lib/extjava.home /usr/java/jdk1.7.0_51/jrejava.io.tmpdir /opt/tomcat6/tempjava.library.path /usr/lib/oracle/11.2/client/lib:/usr/java/packages/lib/i386:/lib:/usr/libjava.naming.factory.initial org.apache.naming.java.javaURLContextFactoryjava.naming.factory.url.pkgs org.apache.namingjava.rmi.server.hostname java.rmi.server.randomIDs truejava.runtime.name Java(TM)SERuntimeEnvironmentjava.runtime.version
jdk
1.7.0_51
-b13java.security.egd file:///dev/urandomjava.specification.name JavaPlatformAPISpecificationjava.specification.vendor OracleCorporationjava.specification.version 1.7java.util.logging.config.file /opt/tomcat6/conf/logging.propertiesjava.util.logging.manager org.apache.juli.ClassLoaderLogManagerjava.vendor OracleCorporationjava.vendor.url http://java.oracle.com/java.vendor.url.bug http://bugreport.sun.com/bugreport/java.version 1.7.0_51java.vm.info mixedmodejava.vm.name JavaHotSpot(TM)ServerVMjava.vm.specification.name JavaVirtualMachineSpecificationjava.vm.specification.vendor OracleCorporationjava.vm.specification.version 1.7java.vm.vendor OracleCorporationjava.vm.version 24.51-b03jna.platform.library.path /usr/lib:/libline.separator mail.smtp.sendpartial truemail.smtps.sendpartial trueos.arch i386os.name Linuxos.version 2.6.18-308.el5PAEpackage.access sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.,sun.beans.package.definition sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.path.separator :securerandom.source file:/dev/./urandomserver.loader shared.loader sun.arch.data.model 32sun.boot.class.path /usr/java/jdk1.7.0_51/jre/lib/resources.jar:/usr/java/jdk1.7.0_51/jre/lib/rt.jar:/usr/java/jdk1.7.0_51/jre/lib/sunrsasign.jar:/usr/java/jdk1.7.0_51/jre/lib/jsse.jar:/usr/java/jdk1.7.0_51/jre/lib/jce.jar:/usr/java/jdk1.7.0_51/jre/lib/charsets.jar:/usr/java/jdk1.7.0_51/jre/lib/jfr.jar:/usr/java/jdk1.7.0_51/jre/classessun.boot.library.path /usr/java/jdk1.7.0_51/jre/lib/i386sun.cpu.endian littlesun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManagersun.io.unicode.encoding UnicodeLittlesun.java.command org.apache.catalina.startup.Bootstrapstartsun.java.launcher SUN_STANDARDsun.jnu.encoding UTF-8sun.management.compiler HotSpotTieredCompilerssun.os.patch.level unknownsvnkit.http.methods Digest,Basic,NTLM,Negotiatesvnkit.ssh2.persistent falsetomcat.util.buf.StringCache.byte.enabled trueuser.country USuser.dir /user.home /rootuser.language enuser.name rootuser.timezone Europe/AmsterdamOmgevingsvariabelenNaam↓Waarde_ /opt/jdk/bin/javaJENKINS_HOME /data/
jenkins
-workLANG en_US.UTF-8LD_LIBRARY_PATH /usr/lib/oracle/11.2/client/libNLSPATH /usr/dt/lib/nls/msg/%L/%N.catPATH /sbin:/usr/sbin:/bin:/usr/binPWD /SHLVL 2TERM xtermTNS_ADMIN /usr/lib/oracle/11.2/client/network/adminXFILESEARCHPATH /usr/dt/app-defaults/%L/DtInvoegtoepassingenNaam↓VersieIngeschakeldPinnedactive-directory
1.
37 true falseanalysis-core 1
554
.
56 true falseant
1
.2 true trueantisamy-markup-formatter 1.1 true trueartifact-promotion 0.2.6 true falseasync-http-client 1.7.8 true falseawseb-deployment-plugin 0.0.3 true falsebuild-flow-plugin 0.12 true falsebuild-name-setter 1.3 true
[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Wilco Greven updated JENKINS-23666 Inject environment variables build step uses the wrong property file Change By: Wilco Greven (03/Jul/14 11:47 AM) Description: Wehaveajobthatusesaninjectenvironmentvariablesbuildsteptoinjectenvironmentvariablesfromapropertyfiletarget/build.properties.Thispropertyfilewasverifiedtoexistintheworkspace. Atfirstthisworkedfine. By Thenby accidentsomeonecreatedafile/target/build.propertiesintherootofthefilesystem. Whenthisfileexistsitwillbeusedby Whathappenednextisthat theinjectenvironmentvariablesbuildstep wouldusethisnewfile insteadofthefileinthe jobs workspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project
Wilco Greven commented on JENKINS-22196 Validation error when choosing a valid project as manual downstream project Hello Thomas, A folder is indeed a Cloudbees Folder Plugin folder. Wilco This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project
Wilco Greven commented on JENKINS-22196 Validation error when choosing a valid project as manual downstream project Hello Thomas, The description is not very clear, now that I read it again, sorry for that. But the issue should be easy to reproduce using the following steps: 1. Create a new folder. 2. Create a new project in the folder. In the next steps we will add a manual trigger that triggers this project. 3. Create a new Maven project in the folder. 4. In the Maven project created in step 3 add a 'Build other projects (manual step)' post-build action to trigger the project created in step 2. You should see that validation of the project name fails and it suggests that the project is in the parent folder. It is essential that the project created in step 3 is a Maven project. The versions I used are Jenkins 1.532.2 and build-pipeline-plugin 1.4.2. Wilco This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project
Wilco Greven created JENKINS-22196 Validation error when choosing a valid project as manual downstream project Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 14/Mar/14 2:13 PM Description: When you add a manual trigger to a Maven project validation of the project name fails. Jenkins will suggest that the project is in the parent folder. For example when I enter 'some-project' as project name, it will suggest '../some-project'. Project: Jenkins Priority: Minor Reporter: Wilco Greven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Wilco Greven
commented on JENKINS-13348
EnvInject overriding WORKSPACE variable
I don't think all plugins have already been rebuild with the new EnvInject version.
What we did is creating a job which periodically runs the following Groovy system script:
hudson.EnvVars.masterEnvVars.remove('WORKSPACE')
It's not nice, but it minimizes the damage caused by this bug.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy] (JENKINS-18112) Token macro expansion for the system groovy build step classpath
Wilco Greven created JENKINS-18112 Token macro expansion for the system groovy build step classpath Issue Type: Improvement Assignee: vjuranek Components: groovy Created: 28/May/13 12:48 PM Description: The classpath setting for the system groovy build step does currently not support token macro expansion. What I would like to do is put a jar on the classpath which is in the workspace of a job or somewhere under JENKINS_HOME. This can't be done with the version 1.13. of the plugin. Environment: Red Hat Enterprise Linux Server release 5.3 (Tikanga) java version 1.6.0_11 Java(TM) SE Runtime Environment (build 1.6.0_11-b03) Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode) Jenkins ver. 1.509.1 Project: Jenkins Priority: Major Reporter: Wilco Greven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Wilco Greven commented on JENKINS-13348 EnvInject overriding WORKSPACE variable I can reproduce the issue using Natalia's steps, but not consistently. To check if WORKSPACE has been modified you can check the value of hudson.EnvVars.masterEnvVars using the script console. Could it be that the cause is in EnvVarsResolver.gatherEnvVarsNode? It looks like EnvVars.masterEnvVars is updated directly in that method when the code runs on master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven created JENKINS-17961 URLTrigger does not poll when URL starts with environment variable Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 15/May/13 12:57 PM Description: If I define an environment variable NEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsg and use it in the following url to poll: $NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library no polling happens. See the following log: prePolling started on May 15, 2013 2:51:04 PM Polling for the job playground_schommelschommel-2-release-_update_shared_library_versie Looking nodes where the poll can be run. Looking for a node to the restricted label master. Restrict on master label. Polling on master. Polling on master. Polling complete. Took 1 ms. No changes./pre The following workaround works. Define an environment variable NEXUS_HOST=l1-ibrprdmvn01.nl.rsg and use it in the url: http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library prePolling started on May 15, 2013 2:57:04 PM Polling for the job playground_schommelschommel-2-release-_update_shared_library_versie Looking nodes where the poll can be run. Looking for a node to the restricted label master. Restrict on master label. Polling on master. Polling on master. Invoking the url: http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library Inspecting the content Polling complete. Took 92 ms. No changes./pre Environment: Red Hat Enterprise Linux Server release 5.3 (Tikanga) java version 1.6.0_11 Java(TM) SE Runtime Environment (build 1.6.0_11-b03) Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode) Jenkins ver. 1.509.1 Project: Jenkins Priority: Minor Reporter: Wilco Greven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven updated JENKINS-17961 URLTrigger does not poll when URL starts with environment variable Change By: Wilco Greven (15/May/13 12:58 PM) Description: IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog: pre code PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges./ pre code Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 12:59 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:
code
{blockquote}
PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.
/code
{blockquote}
Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 12:59 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{
blockquote
quote
}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{
blockquote
quote
}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:00 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{
quote
code
}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{
quote
code
}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryprePollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges./pre
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:01 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{code}
PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.
{code}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library
pre
{code}
PollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges.
/pre
{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:02 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsganduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{code}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{code}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-library
Seethelog:
{code}PollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges.{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Wilco Greven
updated JENKINS-17961
URLTrigger does not poll when URL starts with environment variable
Change By:
Wilco Greven
(15/May/13 1:20 PM)
Description:
IfIdefineanenvironmentvariableNEXUS_BASE_URL=http://l1-ibrprdmvn01.nl.rsg
underJenkinsglobalproperties
anduseitinthefollowingurltopoll:$NEXUS_BASE_URL/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarynopollinghappens.Seethefollowinglog:{code}PollingstartedonMay15,20132:51:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Pollingcomplete.Took1ms.Nochanges.{code}Thefollowingworkaroundworks.DefineanenvironmentvariableNEXUS_HOST=l1-ibrprdmvn01.nl.rsganduseitintheurl:http://$NEXUS_HOST/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-librarySeethelog:{code}PollingstartedonMay15,20132:57:04PMPollingforthejobplayground_-_schommel_-_schommel-2-release_-_update_shared_library_versieLookingnodeswherethepollcanberun.Lookingforanodetotherestrictedlabelmaster.Restrictonmasterlabel.Pollingonmaster.Pollingonmaster.Invokingtheurl:http://l1-ibrprdmvn01.nl.rsg/service/local/lucene/search?repositoryId=releasesg=nl.ibridge.jenkins-playgrounda=shared-libraryInspectingthecontentPollingcomplete.Took92ms.Nochanges.{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
