[JIRA] [coverity-plugin] (JENKINS-24606) Coverity plugin does not use --https-port even though configured to use SSL
Kohsuke Kawaguchi updated JENKINS-24606 Coverity plugin does not use --https-port even though configured to use SSL Change By: Kohsuke Kawaguchi (28/Feb/15 3:55 AM) Attachment: coverity_jenkins.tgz 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] [coverity-plugin] (JENKINS-24606) Coverity plugin does not use --https-port even though configured to use SSL
Kohsuke Kawaguchi reopened JENKINS-24606 Coverity plugin does not use --https-port even though configured to use SSL Change By: Kohsuke Kawaguchi (28/Feb/15 3:55 AM) Resolution: Fixed Status: Closed Reopened 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] [coverity-plugin] (JENKINS-24606) Coverity plugin does not use --https-port even though configured to use SSL
Kohsuke Kawaguchi closed JENKINS-24606 as Fixed Coverity plugin does not use --https-port even though configured to use SSL Removed the attachment as per the request by the plugin maintainer. Change By: Kohsuke Kawaguchi (28/Feb/15 3:56 AM) Status: Reopened Closed 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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions
ikedam
updated JENKINS-27171
Conditions are evaluated for each actions
Change By:
ikedam
(28/Feb/15 4:30 AM)
Description:
Followingcase:{noformat}FlexiblePublishConditionalActionRun?:StringmatchString1:${Test1}String2:expectedActionsomeaction1someaction2
{noformat}
Inthiscase,stringmatchingisevaluatedeachforsomeaction1andsomeaction2.Theconditionshouldbeevaluatedonlyonefortheconfigurationas:*Itcanbeaproblemifthereisaconditionwithside-effects.*Userscanexpecttheconditionwillbeevaluatedonlyonceastheyconfiguredthatonlyonceintheconfigurationpage.*Userscanconfigurelikethisiftheyreallywanttheconditionevaluatedforeachtime:{noformat}FlexiblePublishConditionalActionRun?:StringmatchString1:${Test1}String2:expectedActionsomeaction1ConditionalActionRun?:StringmatchString1:${Test1}String2:expectedActionsomeaction2{noformat}
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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions
ikedam commented on JENKINS-27171 Conditions are evaluated for each actions Anyway, conditions are evaluated every time in prebuild, post-build, aggregations... 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] [pegdown-formatter-plugin] (JENKINS-27049) PegDown formatter causes deprecation message in jenkins log
Mark Waite closed JENKINS-27049 as Not A Defect PegDown formatter causes deprecation message in jenkins log Change By: Mark Waite (28/Feb/15 4:02 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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions
ikedam started work on JENKINS-27171 Conditions are evaluated for each actions Change By: ikedam (28/Feb/15 4:25 AM) Status: Open InProgress 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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions
ikedam
created JENKINS-27171
Conditions are evaluated for each actions
Issue Type:
Bug
Assignee:
ikedam
Components:
flexible-publish-plugin
Created:
28/Feb/15 4:25 AM
Description:
Following case:
Flexible Publish
Conditional Action
Run?: String match
String1: ${Test1}
String2: expected
Action
some action 1
some action 2
In this case, string matching is evaluated each for some action 1 and some action 2.
The condition should be evaluated only one for the configuration as:
* It can be a problem if there is a condition with side-effects.
* Users can expect the condition will be evaluated only once as they configured that only once in the configuration page.
* Users can configure like this if they really want the condition evaluated for each time:
Flexible Publish
Conditional Action
Run?: String match
String1: ${Test1}
String2: expected
Action
some action 1
Conditional Action
Run?: String match
String1: ${Test1}
String2: expected
Action
some action 2
Environment:
flexible-publish-0.14.1
Project:
Jenkins
Priority:
Minor
Reporter:
ikedam
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] [nodejs-plugin] (JENKINS-27170) Provide Node npm bin/ folder to PATH not working for npm install
feng yu
updated JENKINS-27170
Provide Node npm bin/ folder to PATH not working for npm install
Change By:
feng yu
(28/Feb/15 1:32 AM)
Description:
IfollowedtheplugindocthatcheckedProvideNodenpmbin/foldertoPATH,butitnotworksfornpminstall.Youcanseemyscreenshots.
But
Theexecuteshellcommandcanworksverywell,but
theconsolelogshowsnode:commandnotfound
:
,maybenotexportthe$PATH?
$/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npminstall-gkarmakarma-clikarma-jasminekarma-junit-reporterkarma-phantomjs-launcherkarma-spec-reportergulpgulp-concatgulp-sassgulp-minify-cssgulp-renamenpmWARNenginekarma-cli@0.0.4:wanted:{node:~0.8||~0.10}(current:{node:0.12.0,npm:2.5.1})npmWARNenginekarma@0.12.31:wanted:{node:~0.8||~0.10}(current:{node:0.12.0,npm:2.5.1})/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/karma-/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma-cli/bin/karmanpmWARNoptionaldepfailed,continuingfsevents@0.3.5phantomjs@1.9.15install/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma-phantomjs-launcher/node_modules/phantomjsnodeinstall.jssh:node:Commandnotfoundws@0.4.32install/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws(node-gyprebuild2builderror.log)||(exit0)/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/gulp-/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/gulp/bin/gulp.jsnode-sass@2.0.1install/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/gulp-sass/node_modules/node-sassnodescripts/install.jssh:node:CommandnotfoundnpmERR!Linux3.16.0-31-genericnpmERR!argv/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/node/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npminstall-gkarmakarma-clikarma-jasminekarma-junit-reporterkarma-phantomjs-launcherkarma-spec-reportergulpgulp-concatgulp-sassgulp-minify-cssgulp-renamenpmERR!nodev0.12.0npmERR!npmv2.5.1npmERR!codeELIFECYCLEnpmERR!phantomjs@1.9.15install:`nodeinstall.js`npmERR!Exitstatus127npmERR!npmERR!Failedatthephantomjs@1.9.15installscriptnodeinstall.js.npmERR!Thisismostlikelyaproblemwiththephantomjspackage,npmERR!notwithnpmitself.npmERR!Telltheauthorthatthisfailsonyoursystem:npmERR!nodeinstall.jsnpmERR!Youcangettheirinfovia:npmERR!npmownerlsphantomjsnpmERR!Thereislikelyadditionalloggingoutputabove.npmERR!Linux3.16.0-31-genericnpmERR!argv/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/node/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npminstall-gkarmakarma-clikarma-jasminekarma-junit-reporterkarma-phantomjs-launcherkarma-spec-reportergulpgulp-concatgulp-sassgulp-minify-cssgulp-renamenpmERR!nodev0.12.0npmERR!npmv2.5.1npmERR!Uncaught,unspecifiederrorevent.npmERR!npmERR!Ifyouneedhelp,youmayreportthiserrorat:npmERR!http://github.com/npm/npm/issuesnpmERR!Pleaseincludethefollowingfilewithanysupportrequest:npmERR!/npm-debug.log
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] [svnmerge-plugin] (JENKINS-27155) Can't find the Enable Subversion Merge Tracking option in the configuration
Hugues Chabot assigned JENKINS-27155 to Hugues Chabot Cant find the Enable Subversion Merge Tracking option in the configuration Change By: Hugues Chabot (27/Feb/15 1:52 PM) Assignee: KohsukeKawaguchi HuguesChabot 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] [customtools-plugin] (JENKINS-27157) Overriding Tool location(s) has no effect
Markus Eisenmann
commented on JENKINS-27157
Overriding Tool location(s) has no effect
Hi!
Yes, I've run the (test-) job on the master!
To understand my use-case:
Currently, we are using a variable like "JOBS_WORKS_ROOT", which is defined for the master and each slave (specific). This variable defines the root-directory which contains (at least) all wokspaces. The (main-) tools are located under ${JOBS_WORKS_ROOT}\shared\tools\tool-name and each job - regardless whether it runs on the master or an a slave - can use use these "relative" setup of tools.
My idea was, to configure "${JOBS_WORKS_ROOT}\shared\tools\tool-name" as home location to get the same behaviour (but with automatic download and installation).
Up to now, I've not tested, whether the location-override has an effect on slaves
As work-around I've already determined, that a (hard) directoy-link does redirect the installation to get a similar behaviour.
Best regards from Salzburg,
Markus
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] [delivery-pipeline-plugin] (JENKINS-26282) Two manual triggers triggers same downstream job
Jeff Fiser commented on JENKINS-26282 Two manual triggers triggers same downstream job Upgraded to 0.8.9 and still having this issue. We see this when using a single parent job with 2 manual triggers and Rundeck job call. The Rundeck job executes and clicking on the one of the manual downstream triggers works ok. When I click on the second manual trigger I get the error. Here's the trace from the log: Feb 27, 2015 4:23:39 PM se.diabol.jenkins.pipeline.DeliveryPipelineView triggerManual WARNING: Could not trigger manual build oxygen/messagebus/messagebus_charlotte_prod_puppet_run(swat_l2-release_mgmt-sys_mgmt) for upstream oxygen/messagebus/messagebus_tucson_simulation_puppet_run id: 4. Did you mean to specify messagebus/messagebus_charlotte_prod_puppet_run(swat_l2-release_mgmt-sys_mgmt)? se.diabol.jenkins.pipeline.trigger.TriggerException: Trigger not found for manual build oxygen/messagebus/messagebus_charlotte_prod_puppet_run(swat_l2-release_mgmt-sys_mgmt) for upstream oxygen/messagebus/messagebus_tucson_simulation_puppet_run id: 4 at se.diabol.jenkins.pipeline.DeliveryPipelineView.triggerManual(DeliveryPipelineView.java:264) at se.diabol.jenkins.pipeline.PipelineApi.doManualStep(PipelineApi.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Paul Sokolovsky commented on JENKINS-27093 Spurious gits scm poll change detection As I mentioned, this is pretty busy production system, but I checked with its stakeholders, they've done with release builds for now. So yes, we appreciate your looking into this and can do more testing like deploying test stuff. 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] [workflow-plugin] (JENKINS-26619) DescribableHelper does not handle GitSCMExtension
Jesse Glick started work on JENKINS-26619 DescribableHelper does not handle GitSCMExtension Change By: Jesse Glick (27/Feb/15 4:58 PM) Status: Open InProgress 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Jesse Glick reopened JENKINS-26693 Build token root can not start Workflow plugin jobs Change By: Jesse Glick (27/Feb/15 5:00 PM) Resolution: Fixed Status: Resolved Reopened Assignee: JesseGlick NicolasDeLoof 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Jesse Glick started work on JENKINS-26693 Build token root can not start Workflow plugin jobs Change By: Jesse Glick (27/Feb/15 5:00 PM) Status: Open InProgress 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] [delivery-pipeline-plugin] (JENKINS-26282) Two manual triggers triggers same downstream job
Jeff Fiser reopened JENKINS-26282 Two manual triggers triggers same downstream job Upgraded to 0.8.9 and still having this issue. We see this when using a single parent job with 2 manual triggers and Rundeck job call. The Rundeck job executes and clicking on the one of the manual downstream triggers works ok. When I click on the second manual trigger I get the error. Here's the trace from the log: Feb 27, 2015 4:23:39 PM se.diabol.jenkins.pipeline.DeliveryPipelineView triggerManual WARNING: Could not trigger manual build oxygen/messagebus/messagebus_charlotte_prod_puppet_run(swat_l2-release_mgmt-sys_mgmt) for upstream oxygen/messagebus/messagebus_tucson_simulation_puppet_run id: 4. Did you mean to specify messagebus/messagebus_charlotte_prod_puppet_run(swat_l2-release_mgmt-sys_mgmt)? se.diabol.jenkins.pipeline.trigger.TriggerException: Trigger not found for manual build oxygen/messagebus/messagebus_charlotte_prod_puppet_run(swat_l2-release_mgmt-sys_mgmt) for upstream oxygen/messagebus/messagebus_tucson_simulation_puppet_run id: 4 at se.diabol.jenkins.pipeline.DeliveryPipelineView.triggerManual(DeliveryPipelineView.java:264) at se.diabol.jenkins.pipeline.PipelineApi.doManualStep(PipelineApi.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [remoting] (JENKINS-5643) Allow Hudson to checkout source code from master and transfer data to slave
Neon Ngo commented on JENKINS-5643 Allow Hudson to checkout source code from master and transfer data to slave We are also in the need for this feature, otherwise in our master / slave setup, we have to setup SCM access for all our slave machines vs just doing it once on the master machine. 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] [docker-build-publish-plugin] (JENKINS-27164) docker-build-publish-plugin broken compatibility with token-macro-plugin
Justin Good
created JENKINS-27164
docker-build-publish-plugin broken compatibility with token-macro-plugin
Issue Type:
Bug
Assignee:
Michael Neale
Components:
docker-build-publish-plugin, token-macro-plugin
Created:
27/Feb/15 5:04 PM
Description:
A change was introduced in the docker-build-publish-plugin to enable multiple tags. Tags are delimited by a comma (,).
The Token macro plugin allows you to adjust values to your requirements, using the comma as an operator. In our environment, we have previously used a subset of the Git revision to tag our Docker images. The Token macro used is as follows:
${GIT_REVISION,length=6}
When building using the docker-build-publish plugin, the following error is returned:
[docker-build] $ docker build -t example/delivery:${GIT_REVISION .
time="2015-02-27T16:53:52Z" level="fatal" msg="Illegal tag name (${GIT_REVISION): only [A-Za-z0-9_.-] are allowed, minimum 2, maximum 30 in length"
Can the docker-build-publish plugin be fixed to restore compatibility?
Environment:
Jenkins version 1.599
docker-build-publish-plugin 0.10
token-macro-plugin 1.10
Project:
Jenkins
Labels:
plugin
docker
macro
Priority:
Major
Reporter:
Justin Good
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] [docker-build-publish-plugin] (JENKINS-27164) docker-build-publish-plugin broken compatibility with token-macro-plugin
Justin Good updated JENKINS-27164 docker-build-publish-plugin broken compatibility with token-macro-plugin Change By: Justin Good (27/Feb/15 5:08 PM) Environment: Jenkins version 1.599docker-build-publish-plugin0.10token-macro-plugin1.10 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] [git-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Kanstantsin Shautsou commented on JENKINS-27093 Spurious gits scm poll change detection The most funny thing that right now i have infinite polling for 2.2.12 on production system. It see changes constantly and the only thing i found: periodically failed slave and jenkins restart. 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] [workflow-plugin] (JENKINS-26619) DescribableHelper does not handle GitSCMExtension
Jesse Glick reopened JENKINS-26619 DescribableHelper does not handle GitSCMExtension Change By: Jesse Glick (27/Feb/15 4:58 PM) Resolution: Fixed Status: Resolved Reopened Assignee: JesseGlick NicolasDeLoof 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] [workflow-plugin] (JENKINS-26619) DescribableHelper does not handle GitSCMExtension
Jesse Glick updated JENKINS-26619 DescribableHelper does not handle GitSCMExtension Change By: Jesse Glick (27/Feb/15 4:58 PM) Status: Reopened Open 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Jesse Glick updated JENKINS-26693 Build token root can not start Workflow plugin jobs Change By: Jesse Glick (27/Feb/15 5:00 PM) Status: Reopened Open 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] [sauce-ondemand-plugin] (JENKINS-27163) Workspace import error
Allan Kilpatrick created JENKINS-27163 Workspace import error Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 27/Feb/15 5:02 PM Description: When creating a multi-config project in jenkins and the workspace uses one of the axies with a . in the name. This is not escaped correctly. This results in an import error: Androidportraitandroid4 should beAndroidportraitandroid4.4. --- Failure: ImportError (No module named Androidportraitandroid4) ... ERROR == ERROR: Failure: ImportError (No module named Androidportraitandroid4) -- Traceback (most recent call last): File "/Users/x/.jenkins/jobs/Android/workspace/PYTHON/System-CPython-2.7/SELENIUM_DRIVER/Androidportraitandroid4.4./venv/lib/python2.7/site-packages/nose/loader.py", line 414, in loadTestsFromName addr.filename, addr.module) Project: Jenkins Priority: Major Reporter: Allan Kilpatrick 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] [hockeyapp-plugin] (JENKINS-27165) Specify release_type
Karl DeBisschop created JENKINS-27165 Specify release_type Issue Type: New Feature Assignee: Unassigned Components: hockeyapp-plugin Created: 27/Feb/15 5:32 PM Description: Wondering how hard it would be to specify release_type: 2 for alpha 0 for beta default 1 for store 3 for enterprise I'd like it to be done in such a way that I can pass a parameter of release type in so that my various builds can trigger an upload from my single HockeyApp upload. I'm looking into the plugin code myself, but I'm not really a Java developer and I've never tried to make or modify a plugin before. Not likely to be very fast. Project: Jenkins Priority: Minor Reporter: Karl DeBisschop 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] [maven-plugin] (JENKINS-27161) RedeployPublisher does not really parse the global settings from Config File Provider Plugin
Simon Devineau created JENKINS-27161 RedeployPublisher does not really parse the global settings from Config File Provider Plugin Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 27/Feb/15 2:22 PM Description: Hello, I try to use the RedeployPublisher but I have trouble to provide server credentials. Return code is: 401, ReasonPhrase: Unauthorized. The RedeployPublisher uses the settings.xml located in the maven installation conf folder. Maven RedeployPublisher use remote com.--.slave maven settings from : D:\apps\jenkins\com.-.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xml If I set this file with the server info : server iddeploymentRepo/id usernamerepouser/username passwordrepopwd/password /server it works well. But I cannot really set up this file as it is an automatic install and I have several slaves. Besides I would need to do it for each version of maven. When I set up the server credentials in my global maven from the plugin Config File Provider Plugin and remove the server section in the D:\apps\jenkins\com.--.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xml I am not able to publish anymore. I guess the RedeployPublisher does not really parse the global settings from the Config File Provider Plugin. regards Environment: Jenkins 1.599 Config File Provider Plugin 2.7.5 Project: Jenkins Labels: maven plugin redeploy Priority: Major Reporter: Simon Devineau 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] [gitlab-hook-plugin] (JENKINS-27101) Undefined method isOlderThan on automatic project creation
SCM/JIRA link daemon commented on JENKINS-27101 Undefined method isOlderThan on automatic project creation Code changed in jenkins User: Javier Palacios Path: models/services/build_scm.rb spec/services/build_scm_spec.rb http://jenkins-ci.org/commit/gitlab-hook-plugin/e1519d1bc6da511b9a69cb4cef04103e64e65dd7 Log: JENKINS-27101: set right prototype for BuildScm.with 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] [git-plugin] (JENKINS-26197) Allow prune option when using JGit
SCM/JIRA link daemon commented on JENKINS-26197 Allow prune option when using JGit Code changed in jenkins User: Stephan Pauxberger Path: src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/26ac9e58880c9442912efe89228b78f0953d9fc7 Log: JENKINS-26197 Implement correct prune strategy for JGit. Delete any remote branches matching the destination of the given refspecs. Then do the fetch and let it recreate the references. 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Yoann Dubreuil commented on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page I confirm that downgrading to 1.0 is a valid workaround. I ran git bisect to find the offending commit: 4ba5a4915 is the first commit exhibiting this behavior. https://github.com/jenkinsci/junit-plugin/commit/4ba5a491583157a90bfd472db5f657a60bb0c38e 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] [livescreenshot-plugin] (JENKINS-27151) allow dynamically generated images for the LiveScreenshot plugin
Gaetano Giunta resolved JENKINS-27151 as Not A Defect allow dynamically generated images for the LiveScreenshot plugin Change By: Gaetano Giunta (27/Feb/15 12:22 PM) Status: Open Resolved Resolution: NotADefect 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] [customtools-plugin] (JENKINS-27157) Overriding Tool location(s) has no effect
Markus Eisenmann
edited a comment on JENKINS-27157
Overriding Tool location(s) has no effect
Hi!
Yes, I've run the (test-) job on the master!
To understand my use-case:
Currently, we are using a variable like "JOBS_WORKS_ROOT", which is defined for the master and each slave (specific). This variable defines the root-directory which contains (at least) all wokspaces. The (main-) tools are located under ${JOBS_WORKS_ROOT}\shared\tools\tool-name and each job - regardless whether it runs on the master or an a slave - can use use these "relative" setup of tools.
My idea was, to configure "${JOBS_WORKS_ROOT}\shared\tools\tool-name" as home location to get the same behaviour (but with automatic download and installation).
Up to now, I've not tested, whether the location-override has an effect on slaves
As work-around I've already determined, that a (hard) directory-link (Jenkins\tools\com.cloudbees.jenkins.plugins.customtools.CustomTool - ${JOBS_WORKS_ROOT}\shared\tools) does redirect the installation to get a similar behaviour.
Best regards from Salzburg,
Markus
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-27160) display the slave name in the main job's console output
Neon Ngo created JENKINS-27160 display the slave name in the main jobs console output Issue Type: Improvement Assignee: Unassigned Components: core Created: 27/Feb/15 1:46 PM Description: I have a Jenkin's master with multiple slave setup. I would like to have the main job's console output to include the slave name where jobs are executed. e.g. Currently in Jenkins ver. 1.580.3 the main output of my Multi-configuration project look like something below: Started by an SCM change Building on master in workspace /var/lib/jenkins/jobs/test_el6_gcc4.4_nightly/workspace ... No emails were triggered. Triggering test_el6_gcc4.4_nightly Âŧ jdk6,el6 Triggering test_el6_gcc4.4_nightly Âŧ jdk8,el6 Triggering test_el6_gcc4.4_nightly Âŧ jdk7,el6 Triggering test_el6_gcc4.4_nightly Âŧ openjdk7,el6 Triggering test_el6_gcc4.4_nightly Âŧ openjdk6,el6 test_el6_gcc4.4_nightly Âŧ jdk8,el6 completed with result SUCCESS test_el6_gcc4.4_nightly Âŧ jdk7,el6 completed with result SUCCESS test_el6_gcc4.4_nightly Âŧ openjdk7,el6 completed with result SUCCESS test_el6_gcc4.4_nightly Âŧ openjdk6,el6 completed with result SUCCESS ... Finished: SUCCESS I would like it to be something like this ... Triggering test_el6_gcc4.4_nightly Âŧ openjdk6,el6 test_el6_gcc4.4_nightly Âŧ jdk8,el6 completed on slaveMachine1 with result SUCCESS test_el6_gcc4.4_nightly Âŧ jdk7,el6 completed on slaveMachine2 with result SUCCESS test_el6_gcc4.4_nightly Âŧ openjdk7,el6 completed on slaveMachine3 with result SUCCESS test_el6_gcc4.4_nightly Âŧ openjdk6,el6 completed on slaveMachine1 with result SUCCESS ... e.g. on the success or failure result line, it should include the slave name Environment: Jenkins ver. 1.580.3 on CentOS 6.6 Project: Jenkins Priority: Minor Reporter: Neon Ngo 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] [svnmerge-plugin] (JENKINS-27155) Can't find the Enable Subversion Merge Tracking option in the configuration
Hugues Chabot commented on JENKINS-27155 Cant find the Enable Subversion Merge Tracking option in the configuration Apparently the documentation is incorrect. The name of the option is "This project build a Subversion feature branch". 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon commented on JENKINS-26693 Build token root can not start Workflow plugin jobs Code changed in jenkins User: Nicolas De Loof Path: pom.xml src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java http://jenkins-ci.org/commit/build-token-root-plugin/5a6b6b7ffe24139e7137930ad5d1e7e88920100a Log: FIXED JENKINS-26693 adapt to Jobs which are not AbstractProjects 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] [maven-plugin] (JENKINS-27161) RedeployPublisher does not really parse the global settings from Config File Provider Plugin
Simon Devineau updated JENKINS-27161 RedeployPublisher does not really parse the global settings from Config File Provider Plugin Change By: Simon Devineau (27/Feb/15 2:34 PM) Description: Hello,ItrytousetheRedeployPublisherbutIhavetroubletoprovideservercredentials.Returncodeis:401,ReasonPhrase:Unauthorized.TheRedeployPublisherusesthesettings.xmllocatedinthemaveninstallationconffolder.MavenRedeployPublisheruseremotecom.---.slavemavensettingsfrom:D:\apps\jenkins\com.--.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xmlIfIsetthisfilewiththeserverinfo:serveriddeploymentRepo/idusernamerepouser/usernamepasswordrepopwd/password/serveritworkswell.ButIcannotreallysetupthisfileasitisanautomaticinstallandIhaveseveralslaves.BesidesIwouldneedtodoitforeachversionofmaven.WhenIsetuptheservercredentialsinmyglobalmavenfromthepluginConfigFileProviderPluginandremovetheserversectionintheD:\apps\jenkins\com.--.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xmlIamnotabletopublishanymore.IguesstheRedeployPublisherdoesnotreallyparsetheglobalsettingsfromtheConfigFileProviderPlugin eventifitiswrittenusingglobalsettingsconfigwithname . .. regards 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon resolved JENKINS-26693 as Fixed Build token root can not start Workflow plugin jobs Change By: SCM/JIRA link daemon (27/Feb/15 2:48 PM) Status: Open Resolved 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] [openid-plugin] (JENKINS-27159) username is the server URL
junaid shaikh created JENKINS-27159 username is the server URL Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: 2014-12-22 16_18_35-Configure Global Security [Jenkins].png Components: openid-plugin Created: 27/Feb/15 12:44 PM Description: Hi, I am not able to figure where to tinker in order to solve this. Problem description: CAS is configured with openid whihc uses LDAP as user database and used as authentication for my Jenkins server. After successful login from CAS, it gets redirected back to my jenkins server page. However on the top right corner where ideally the displayName of the user should be, it shows the openid provider URL as it was provided in the openid configuration using jenkins openid plugin. Please refer to image as shown in the screenshot Environment: chrome browser windows 7 enterprise IBM thinkpad T510 Project: Jenkins Labels: plugin openid jenkins user-id Priority: Minor Reporter: junaid shaikh 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] [git-plugin] (JENKINS-27166) CLONE - Git SCM-polling doesn't work when using a parametrized branch-name
pmv commented on JENKINS-27166 CLONE - Git SCM-polling doesnt work when using a parametrized branch-name I cloned JENKINS-14276, because this comment was made, and I believe it should have its own ticket: https://issues.jenkins-ci.org/browse/JENKINS-14276?focusedCommentId=217115page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-217115 Another user also posted a pull request: https://github.com/jenkinsci/git-plugin/pull/293 But since it was on a closed ticket I'm not sure if it was seen. Since the pull request is still open I created this ticket hoping to raise visibility. I'm seeing the issue on Git Plugin 2.3.1, Git Client 1.12.0. I will update the plugins to the latest and test (in case it was fixed by other later commits), but I didn't see anything in the changelog to address it. 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] [git-plugin] (JENKINS-27166) CLONE - Git SCM-polling doesn't work when using a parametrized branch-name
pmv
created JENKINS-27166
CLONE - Git SCM-polling doesnt work when using a parametrized branch-name
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
27/Feb/15 6:01 PM
Description:
Setup:
Git Plugin 1.1.20
a parameterized build with parameter "Branch", default "**"
Git SCM with branch specifier "${Branch}"
SCM polling activated
Intended behaviour:
if any branch changes, Jenkins checks out and builds this branch
when executed manually, the user enters the name of the branch to be built
Actual behaviour:
no changes are detected (because the "${Branch}" value isn't resolved when polling)
Project:
Jenkins
Priority:
Major
Reporter:
pmv
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] [subversion-plugin] (JENKINS-27167) Jenkins fails to update a subversion 1.6 repo (NPE)
Mason Donahue created JENKINS-27167 Jenkins fails to update a subversion 1.6 repo (NPE) Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 27/Feb/15 6:14 PM Description: We're running Jenkins 1.598 with subversion plugin 2.5. One of our two build slaves is running ubuntu 11.10; the other (jslave05) is a newly recreated box running ubuntu 14.10. Our repository is weird and won't work with subversion 1.8, which is installed on the slave. That said, my understanding is that subversion-plugin doesn't use the svn version on slaves and instead checks out using SVNKit. We have subversion-plugin set to 1.6. When a build is run for the second time on jslave05 (i.e. when the workspace exists already and it just needs to update it) it fails immediately with the following stacktrace. Removing the workspace and rebuilding seems to fix it for the next run, but the next after that will fail. Started by user mdonahue [EnvInject] - Loading node environment variables. Building remotely on jslave05 (tools workdev) in workspace /home/jenkins/hudson_builds/workspace/Build_Project-dev-PRJ-21533 FATAL: null java.lang.NullPointerException at java.util.EnumMap.init(EnumMap.java:138) at org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.init(SVNSqlJetDb.java:61) at org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.open(SVNSqlJetDb.java:119) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.openDb(SVNWCDb.java:4827) at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.parseDir(SVNWCDb.java:1901) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.detectWcGeneration(SvnOperationFactory.java:1696) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.getImplementation(SvnOperationFactory.java:1342) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1248) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2485) at hudson.scm.subversion.UpdateUpdater$TaskImpl.parseSvnInfo(UpdateUpdater.java:125) at hudson.scm.subversion.UpdateUpdater$TaskImpl.getSvnCommandToUse(UpdateUpdater.java:87) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:130) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2685) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) 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 jslave05(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:978) at hudson.FilePath.act(FilePath.java:967) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at
[JIRA] [robot-plugin] (JENKINS-26980) Enable configuration of Robot Results column in the default job list view
Michael Toothaker commented on JENKINS-26980 Enable configuration of Robot Results column in the default job list view Great, thank you! 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] [subversion-plugin] (JENKINS-27167) Jenkins fails to update a subversion 1.6 repo (NPE)
Mason Donahue
updated JENKINS-27167
Jenkins fails to update a subversion 1.6 repo (NPE)
Change By:
Mason Donahue
(27/Feb/15 6:16 PM)
Description:
WererunningJenkins1.598withsubversionplugin2.5.Oneofourtwobuildslavesisrunningubuntu11.10;theother(jslave05)isanewly
recreated
created
boxrunningubuntu14.
10
04
.Ourrepositoryisweirdandwontworkwithsubversion1.8,whichisinstalledontheslave.Thatsaid,myunderstandingisthatsubversion-plugindoesntusethesvnversiononslavesandinsteadchecksoutusingSVNKit.Wehavesubversion-pluginsetto1.6.Whenabuildisrunforthesecondtimeonjslave05(i.e.whentheworkspaceexistsalreadyanditjustneedstoupdateit)itfailsimmediatelywiththefollowingstacktrace.Removingtheworkspaceandrebuildingseemstofixitforthenextrun,butthenextafterthatwillfail.{code}Startedbyusermdonahue[EnvInject]-Loadingnodeenvironmentvariables.Buildingremotelyonjslave05(toolsworkdev)inworkspace/home/jenkins/hudson_builds/workspace/Build_Project-dev-PRJ-21533FATAL:nulljava.lang.NullPointerException atjava.util.EnumMap.init(EnumMap.java:138) atorg.tmatesoft.svn.core.internal.db.SVNSqlJetDb.init(SVNSqlJetDb.java:61) atorg.tmatesoft.svn.core.internal.db.SVNSqlJetDb.open(SVNSqlJetDb.java:119) atorg.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.openDb(SVNWCDb.java:4827) atorg.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.parseDir(SVNWCDb.java:1901) atorg.tmatesoft.svn.core.wc2.SvnOperationFactory.detectWcGeneration(SvnOperationFactory.java:1696) atorg.tmatesoft.svn.core.wc2.SvnOperationFactory.getImplementation(SvnOperationFactory.java:1342) atorg.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1248) atorg.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) atorg.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2485) athudson.scm.subversion.UpdateUpdater$TaskImpl.parseSvnInfo(UpdateUpdater.java:125) athudson.scm.subversion.UpdateUpdater$TaskImpl.getSvnCommandToUse(UpdateUpdater.java:87) athudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:130) athudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) athudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:991) athudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:972) athudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:948) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2685) athudson.remoting.UserRequest.perform(UserRequest.java:121) athudson.remoting.UserRequest.perform(UserRequest.java:49) athudson.remoting.Request$2.run(Request.java:324) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:745) at..remotecalltojslave05(NativeMethod) athudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) athudson.remoting.UserResponse.retrieve(UserRequest.java:221) athudson.remoting.Channel.call(Channel.java:752) athudson.FilePath.act(FilePath.java:978) athudson.FilePath.act(FilePath.java:967) athudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) athudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) athudson.scm.SCM.checkout(SCM.java:484) athudson.model.AbstractProject.checkout(AbstractProject.java:1270) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) athudson.model.Run.execute(Run.java:1718) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89)
[JIRA] [patch-parameter-plugin] (JENKINS-27168) Patch Parameter plugin fails while using Jdk 1.8
Harsh Shah created JENKINS-27168 Patch Parameter plugin fails while using Jdk 1.8 Issue Type: Bug Assignee: Unassigned Components: patch-parameter-plugin Created: 27/Feb/15 6:51 PM Description: Scanning for projects... INFO INFO INFO Building patch-parameter 1.3-SNAPSHOT INFO INFO INFO maven-hpi-plugin:1.93:validate (default-validate) @ patch-parameter INFO INFO maven-enforcer-plugin:1.0.1:enforce (enforce-maven) @ patch-parameter INFO INFO maven-enforcer-plugin:1.0.1:display-info (display-info) @ patch-parameter INFO Maven Version: 3.2.5 INFO JDK Version: 1.8.0_31 normalized as: 1.8.0-31 INFO OS Info: Arch: amd64 Family: dos Name: windows 7 Version: 6.1 INFO INFO maven-localizer-plugin:1.14:generate (default) @ patch-parameter INFO INFO maven-resources-plugin:2.5:resources (default-resources) @ patch-parameter debug execute contextualize INFO Using 'UTF-8' encoding to copy filtered resources. INFO Copying 4 resources INFO INFO maven-compiler-plugin:2.5:compile (default-compile) @ patch-parameter INFO Nothing to compile - all classes are up to date INFO INFO access-modifier-checker:1.4:enforce (default-enforce) @ patch-parameter INFO INFO maven-hpi-plugin:1.93:insert-test (default-insert-test) @ patch-parameter INFO INFO gmaven-plugin:1.3:generateTestStubs (test-in-groovy) @ patch-parameter INFO No sources found for Java stub generation INFO INFO maven-resources-plugin:2.5:testResources (default-testResources) @ patch-parameter debug execute contextualize INFO Using 'UTF-8' encoding to copy filtered resources. INFO Copying 1 resource INFO INFO maven-compiler-plugin:2.5:testCompile (default-testCompile) @ patch-parameter INFO Nothing to compile - all classes are up to date INFO INFO maven-hpi-plugin:1.93:test-hpl (default-test-hpl) @ patch-parameter INFO Generating E:\views\patchpulgin\patch-parameter-plugin-master\target\test-classes\the.hpl INFO INFO maven-hpi-plugin:1.93:resolve-test-dependencies (default-resolve-test-dependencies) @ patch-parameter INFO INFO gmaven-plugin:1.3:testCompile (test-in-groovy) @ patch-parameter INFO No sources found to compile INFO INFO maven-surefire-plugin:2.9:test (default-test) @ patch-parameter INFO Surefire report directory: E:\views\patchpulgin\patch-parameter-plugin-master\target\surefire-reports --- T E S T S --- Running InjectedTest Picking up existing exploded jenkins.war at E:\views\patchpulgin\patch-parameter-plugin-master\.\target\jenkins-for-test Feb 27, 2015 9:25:33 AM org.mortbay.log.Slf4jLog info INFO: Logging to org.slf4j.impl.JDK14LoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog Feb 27, 2015 9:25:33 AM org.mortbay.log.Slf4jLog info INFO: jetty-6.1.26 Feb 27, 2015 9:25:36 AM org.mortbay.log.Slf4jLog info INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet Feb 27, 2015 9:25:36 AM org.mortbay.log.Slf4jLog info INFO: Copy E:\views\patchpulgin\patch-parameter-plugin-master\target\jenkins-for-test to C:\Users\shahh5\AppData\Local\Temp\Jetty_0_0_0_0_0_jenkins.for.test___.bj8wp3\webapp Feb 27, 2015 9:25:38 AM org.mortbay.log.Slf4jLog info INFO: Started SocketConnector@0.0.0.0:55769 Feb 27, 2015 9:25:38 AM jenkins.InitReactorRunner$1 onAttained INFO: Started initialization Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs Feb 27, 2015 9:25:48 AM jenkins.InitReactorRunner$1 onAttained INFO: Completed
[JIRA] [patch-parameter-plugin] (JENKINS-27168) Patch Parameter plugin fails while using Jdk 1.8
Harsh Shah updated JENKINS-27168 Patch Parameter plugin fails while using Jdk 1.8 Change By: Harsh Shah (27/Feb/15 6:51 PM) Description: ThepluginbuildfailswhentryingmavenbuildusingJdk1.8.butitworksfineinJdk1.7.
[JIRA] [workflow-plugin] (JENKINS-27162) main job's console output does not include touchstone build
Neon Ngo created JENKINS-27162 main jobs console output does not include touchstone build Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 27/Feb/15 3:55 PM Description: One thing I believe that is missing in the current main job's (Multi-configuration project) console output is the result of the touchstone build (jdk6 in my case), Started by an SCM change Building on master in workspace /var/lib/jenkins/jobs/testjob/workspace ... Triggering testjob Âŧ jdk6 Triggering testjob Âŧ jdk8 Triggering testjob Âŧ jdk7 testjob Âŧ jdk8 completed with result SUCCESS testjob Âŧ jdk7 completed with result SUCCESS ... Finished: SUCCESS The main job's output is missing the result of the touchstone build, i.e. testjob Âŧ jdk6 completed with result SUCCESS should that output should be something like: ... Triggering testjob Âŧ jdk6 testjob Âŧ jdk6 completed with result SUCCESS Triggering testjob Âŧ jdk8 Triggering testjob Âŧ jdk7 testjob Âŧ jdk8 completed with result SUCCESS testjob Âŧ jdk7 completed with result SUCCESS ... Environment: Jenkins ver. 1.580.3 on CentOS 6.6 Project: Jenkins Priority: Minor Reporter: Neon Ngo 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] [p4-plugin] (JENKINS-26455) Removing .p4config file during force clean
Alexey Larsky commented on JENKINS-26455 Removing .p4config file during force clean As workaround it can work, but this approach influent all developers. We use the same workspace description for all. 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] [maven-plugin] (JENKINS-27161) RedeployPublisher does not really parse the global settings from Config File Provider Plugin
Simon Devineau updated JENKINS-27161 RedeployPublisher does not really parse the global settings from Config File Provider Plugin Change By: Simon Devineau (27/Feb/15 3:02 PM) Attachment: jenkins.png 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-failure-analyzer-plugin] (JENKINS-27123) Workflow support for Build Failure Analyzer
Tomas Westling commented on JENKINS-27123 Workflow support for Build Failure Analyzer At first glance, it doesn't look like we depend on anything AbstractJob/Build-specific, so expanding to Job and Run for Flows shouldn't be a problem. 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon resolved JENKINS-26693 as Fixed Build token root can not start Workflow plugin jobs Change By: SCM/JIRA link daemon (27/Feb/15 7:56 PM) Status: InProgress Resolved 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] [gradle-jpi-plugin] (JENKINS-17129) Gradle plugin does not support HudsonTestCase
Daniel Spilker resolved JENKINS-17129 as Fixed Gradle plugin does not support HudsonTestCase Change By: Daniel Spilker (27/Feb/15 8:20 PM) Status: InProgress Resolved 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] [build-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Jesse Glick reopened JENKINS-26693 Build token root can not start Workflow plugin jobs Change By: Jesse Glick (27/Feb/15 8:25 PM) Resolution: Fixed Status: Resolved Reopened 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired I've updated my pull request with a new boolean EC2 Cloud parameter to enable using the query string signer, and the fix from Martin (though I just realized I only mentioned the query string signer fix in the commit message, wasn't intentional not to mention that...). Just thought it would be handy to put the changes in one place for anyone else reading this issue until the fix makes it into a proper release build, and to make sure that if the query string signer type is needed that users can enable it. 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-26690) Build stats throws illegal argument exception on dashboard view
SCM/JIRA link daemon resolved JENKINS-26690 as Fixed Build stats throws illegal argument exception on dashboard view Change By: SCM/JIRA link daemon (27/Feb/15 8:56 PM) Status: InProgress Resolved 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] [gradle-jpi-plugin] (JENKINS-17129) Gradle plugin does not support HudsonTestCase
SCM/JIRA link daemon commented on JENKINS-17129 Gradle plugin does not support HudsonTestCase Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtension.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtensionSpec.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPluginSpec.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/3791a55fe28d3f4920c4dfb6ff7f92edd0ff69e3 Log: Merge pull request #45 from daspilker/JENKINS-17129 JENKINS-17129 Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/f165013b531f...3791a55fe28d 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] [gradle-jpi-plugin] (JENKINS-17130) Plugin messes up repository URLs
Daniel Spilker resolved JENKINS-17130 as Fixed Plugin messes up repository URLs Change By: Daniel Spilker (27/Feb/15 8:52 PM) Status: InProgress Resolved 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] [cloudfoundry-plugin] (JENKINS-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails You're right, looks like the noroute option is supposed to unbind, not remove. The Go client unbinds all routes from the application. There is a way to unbind routes from the Java client, but it's hidden in the updateApplicationUris() method. If you follow to the private removeUris() method, you'll see that it unbinds routes. So it seems that unbinding every route from an app would be simply done by passing an empty List to updateApplicationUris(). As a final note: I was actually wrong earlier when saying that createApplication() always creates a route. Passing an empty List as the `uris` parameter creates no route. Knowing this, it would be best to prevent the route creation if `noroute` is set, before calling updateApplicationUris(). 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon commented on JENKINS-26693 Build token root can not start Workflow plugin jobs Code changed in jenkins User: Nicolas De Loof Path: pom.xml src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java http://jenkins-ci.org/commit/build-token-root-plugin/fa0d5cdea4dc86f1b8d4a659260252e02cd00321 Log: FIXED JENKINS-26693 adapt to Jobs which are not AbstractProjects 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] [gradle-jpi-plugin] (JENKINS-17130) Plugin messes up repository URLs
SCM/JIRA link daemon commented on JENKINS-17130 Plugin messes up repository URLs Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md config/codenarc/rules.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtension.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifestSpec.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPluginSpec.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPomCustomizerSpec.groovy src/test/resources/org/jenkinsci/gradle/plugins/jpi/complex-pom.xml http://jenkins-ci.org/commit/gradle-jpi-plugin/44fe12847e098524f984778c905381e86bdb4bfb Log: Merge pull request #47 from daspilker/JENKINS-17130 Added configureRepositories Option Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/3791a55fe28d...44fe12847e09 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-26690) Build stats throws illegal argument exception on dashboard view
SCM/JIRA link daemon commented on JENKINS-26690 Build stats throws illegal argument exception on dashboard view Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java http://jenkins-ci.org/commit/jenkins/dac7dfe94e6c21eee92704acace2079668a023b1 Log: JENKINS-26690 Noting merge of #1586. Compare: https://github.com/jenkinsci/jenkins/compare/a452023789cc...dac7dfe94e6c 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-26690) Build stats throws illegal argument exception on dashboard view
SCM/JIRA link daemon commented on JENKINS-26690 Build stats throws illegal argument exception on dashboard view Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java http://jenkins-ci.org/commit/jenkins/db1f805d68a1aaf8e2d6d1c96cb006fc1dd4c087 Log: FIXED JENKINS-26690 Integer overflow in AbstractLazyLoadRunMap.headMap with negative arguments. 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] [p4-plugin] (JENKINS-26455) Removing .p4config file during force clean
Alexey Larsky commented on JENKINS-26455 Removing .p4config file during force clean I can't update server to latest. And keeping .p4config (or %P4CONFIG%) file will help me so much. For example you can copy it to any temp location, before removing whole dir and restore it after. 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] [workflow-plugin] (JENKINS-26513) Deserialization error of ExecutorStepExecution
Jesse Glick started work on JENKINS-26513 Deserialization error of ExecutorStepExecution Change By: Jesse Glick (27/Feb/15 9:32 PM) Status: Open InProgress 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] [matrix-project-plugin] (JENKINS-27162) main job's console output does not include touchstone build
Jesse Glick updated JENKINS-27162 main jobs console output does not include touchstone build Change By: Jesse Glick (27/Feb/15 10:10 PM) Assignee: JesseGlick Component/s: matrix-project-plugin Component/s: workflow-plugin 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] [workflow-plugin] (JENKINS-26834) Direct access to contextual [Workflow]Run
Jesse Glick commented on JENKINS-26834 Direct access to contextual [Workflow]Run Is this the correct link? Yes. I'm really interested how to get the current Run It is not currently possible, hence this issue. 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Jesse Glick started work on JENKINS-26693 Build token root can not start Workflow plugin jobs Change By: Jesse Glick (27/Feb/15 10:10 PM) Status: Open InProgress 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-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
Jesse Glick updated JENKINS-26693 Build token root can not start Workflow plugin jobs Change By: Jesse Glick (27/Feb/15 10:10 PM) Status: Reopened Open 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] [workflow-plugin] (JENKINS-26619) DescribableHelper does not handle GitSCMExtension
SCM/JIRA link daemon commented on JENKINS-26619 DescribableHelper does not handle GitSCMExtension Code changed in jenkins User: Nicolas De Loof Path: step-api/src/main/java/org/jenkinsci/plugins/workflow/structs/DescribableHelper.java http://jenkins-ci.org/commit/workflow-plugin/d438925a84bf0a16c50635a703526ddf26d6efd5 Log: FIXED JENKINS-26619 java.lang.Class#isAssignableFrom need to apply on expected type I always have to read javadoc twice to remember how to use it. 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] [workflow-plugin] (JENKINS-26619) DescribableHelper does not handle GitSCMExtension
SCM/JIRA link daemon resolved JENKINS-26619 as Fixed DescribableHelper does not handle GitSCMExtension Change By: SCM/JIRA link daemon (27/Feb/15 9:22 AM) Status: Open Resolved 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] [core] (JENKINS-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Michael Rentschler commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value @Peter Hackett: There was good reasons to use a different BUILD_ID than the timestamp. Using BUILD_TIMESTAMP instead should be a feasible change for everybody, not? There is an alternative solution available. Please read my first comment above. This Groovy-one-liner will define a BUILD_TIMESTAMP variable. The timestamp of this variable will match the exact time when Jenkins triggered the build (the time that will be shown in the build history of each job). There is no jitter like its possible if you use the current time by calling e.g. 'date' from inside your build scripts. Once this ticket is fixed, this workaround can be removed seamlessly. 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] [matrix-project-plugin] (JENKINS-27156) Git notifications trigger previous builds
Natalia Pokrovskaya created JENKINS-27156 Git notifications trigger previous builds Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: mctp1.png, mctp2.png Components: matrix-project-plugin Created: 27/Feb/15 8:58 AM Description: We have multiple jenkins multi-configuration projects which are triggered by web hooks from Stash server on repository changes. On Jenkins, the projects triggers builds on slaves connected via SSH. All this works pretty well, except that each stash notifications triggers previous build before actually proceeding current notification, i.e. say, on my Jenkins server I see 7 builds, with the last one done yesterday. After pushing a new changes on git, Jenkins, instead of running a new (8th) build on slaves, relaunch 7th build on slaves (during this time 8th build is shown as "waiting..."), and only then 8th build... Have we misconfigured something? Thank you in advance for your help! Environment: Jenkins 1.588 Atlassian Stash 3.3.0 Project: Jenkins Labels: build notification trigger git stash Priority: Minor Reporter: Natalia Pokrovskaya 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] [jira-plugin] (JENKINS-13364) Can Not Change JIRA Password
Roger Koche commented on JENKINS-13364 Can Not Change JIRA Password https://confluence.atlassian.com/pages/viewpage.action?pageId=231932759 This is from an older version of JIRA and does not work but maybe the simple option that it is showing how to circumvent is the problem. 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] [workflow-plugin] (JENKINS-26834) Direct access to contextual [Workflow]Run
Christoph VogtlÃĪnder
commented on JENKINS-26834
Direct access to contextual [Workflow]Run
The "this discussion" link in the description points to "Implemented JUnitStep ("archiveTestResults")". Is this the correct link? I'm really interested how to get the current Run in a sandboxed environment.
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] [workflow-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
Jesse Glick updated JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Change By: Jesse Glick (27/Feb/15 11:06 PM) Labels: deadlock testing threads 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] [patch-parameter-plugin] (JENKINS-27169) Patch paramter plugin's patch code is OS dependent which fails to patch cross platform files
Harsh Shah created JENKINS-27169 Patch paramter plugins patch code is OS dependent which fails to patch cross platform files Issue Type: Bug Assignee: Unassigned Attachments: failed test.jpg, noerror.jpg Components: patch-parameter-plugin Created: 27/Feb/15 11:06 PM Description: The test case in someTest class (https://github.com/jenkinsci/patch-parameter-plugin/commit/02c684a6e9d9fe40548c839ab15d2231306eb239 ) fails on windows. The code uses cloudbees/diff4j/ContextualPatch which internally uses BufferedReader to read files. BufferedReader does OS specific reading operation. So the end of file is causing the problem for the test case to pass when run on windows machine. Kindly see the attached images. Here is the link of ContextualPatch implementation https://github.com/cloudbees/diff4j/blob/master/src/main/java/com/cloudbees/diff/ContextualPatch.java Thank you for the help. H Shah Environment: JDK 7, windows 7 Project: Jenkins Priority: Major Reporter: Harsh Shah 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] [google-login-plugin] (JENKINS-27117) google login plugin not working
oeuftete commented on JENKINS-27117 google login plugin not working Seeing an identical problem. Things were working fine, but I'm trying to migrate our URL to a different domain to the Google Apps domain doing the authenticating, and that's when the problem started. Looks like the OP has a similar configuration. 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] [google-login-plugin] (JENKINS-27117) google login plugin not working
oeuftete edited a comment on JENKINS-27117 google login plugin not working Seeing an identical problem. Things were working fine, but I'm trying to migrate our URL to a different domain than the Google Apps domain doing the authenticating, and that's when the problem started. Looks like the OP has a similar configuration. 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] [svnmerge-plugin] (JENKINS-11378) Infinite Integration - Rebase Loop
ruiling huang commented on JENKINS-11378 Infinite Integration - Rebase Loop Hi, actually i do the same step as you, but after the Step 3:Configured branch project to "Integrate to upstream upon successful build", Jenkins can not successfully built the project.I get the error information like this:ERROR: Build step failed with exception java.lang.NullPointerException at hudson.scm.SVNRevisionState.getRevision(SVNRevisionState.java:24) at jenkins.plugins.svnmerge.IntegrateAction.getSvnInfo(IntegrateAction.java:149) at jenkins.plugins.svnmerge.IntegrateAction.perform(IntegrateAction.java:165) at jenkins.plugins.svnmerge.IntegrationPublisher.perform(IntegrationPublisher.java:51) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1743) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Build step 'Integrate to upstream upon successful build' marked build as failure Finished: FAILURE Can you help me? What should I do to deal with this problem? Thank you ! 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] [svnmerge-plugin] (JENKINS-27155) Can't find the Enable Subversion Merge Tracking option in the configuration
ruiling huang commented on JENKINS-27155 Cant find the Enable Subversion Merge Tracking option in the configuration Hugues Chabot, Thank your for your help,actually I had enabled the option"This project build a Subversion feature branch" and confirmed the Upstream project name is correct.But I still get the error information like this: ERROR: Build step failed with exception java.lang.NullPointerException at hudson.scm.SVNRevisionState.getRevision(SVNRevisionState.java:24) at jenkins.plugins.svnmerge.IntegrateAction.getSvnInfo(IntegrateAction.java:149) at jenkins.plugins.svnmerge.IntegrateAction.perform(IntegrateAction.java:165) at jenkins.plugins.svnmerge.IntegrationPublisher.perform(IntegrationPublisher.java:51) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1743) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Build step 'Integrate to upstream upon successful build' marked build as failure Finished: FAILURE Do I miss some pulgin ? what should deal with this error? 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] [nodejs-plugin] (JENKINS-27170) Provide Node npm bin/ folder to PATH not working for npm install
feng yu
created JENKINS-27170
Provide Node npm bin/ folder to PATH not working for npm install
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
DeepinScreenshot20150228092443.png, DeepinScreenshot20150228092548.png
Components:
nodejs-plugin
Created:
28/Feb/15 1:29 AM
Description:
I followed the plugin doc that checked "Provide Node npm bin/ folder to PATH", but it not works for npm install. You can see my screenshots.
But the console log shows "node: command not found":
$ /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npm install -g karma karma-cli karma-jasmine karma-junit-reporter karma-phantomjs-launcher karma-spec-reporter gulp gulp-concat gulp-sass gulp-minify-css gulp-rename
npm WARN engine karma-cli@0.0.4: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.0","npm":"2.5.1"})
npm WARN engine karma@0.12.31: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.0","npm":"2.5.1"})
/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/karma - /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma-cli/bin/karma
npm WARN optional dep failed, continuing fsevents@0.3.5
phantomjs@1.9.15 install /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma-phantomjs-launcher/node_modules/phantomjs
node install.js
sh: node: Command not found
ws@0.4.32 install /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
(node-gyp rebuild 2 builderror.log) || (exit 0)
/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/gulp - /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/gulp/bin/gulp.js
node-sass@2.0.1 install /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/gulp-sass/node_modules/node-sass
node scripts/install.js
sh: node: Command not found
npm ERR! Linux 3.16.0-31-generic
npm ERR! argv "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/node" "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npm" "install" "-g" "karma" "karma-cli" "karma-jasmine" "karma-junit-reporter" "karma-phantomjs-launcher" "karma-spec-reporter" "gulp" "gulp-concat" "gulp-sass" "gulp-minify-css" "gulp-rename"
npm ERR! node v0.12.0
npm ERR! npm v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! phantomjs@1.9.15 install: `node install.js`
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the phantomjs@1.9.15 install script 'node install.js'.
npm ERR! This is most likely a problem with the phantomjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls phantomjs
npm ERR! There is likely additional logging output above.
npm ERR! Linux 3.16.0-31-generic
npm ERR! argv "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/node" "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npm" "install" "-g" "karma" "karma-cli" "karma-jasmine" "karma-junit-reporter" "karma-phantomjs-launcher" "karma-spec-reporter" "gulp" "gulp-concat" "gulp-sass" "gulp-minify-css" "gulp-rename"
npm ERR! node v0.12.0
npm ERR! npm v2.5.1
npm ERR! Uncaught, unspecified "error" event.
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! http://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log
Project:
Jenkins
Labels:
[JIRA] [p4-plugin] (JENKINS-26455) Removing .p4config file during force clean
Paul Allen commented on JENKINS-26455 Removing .p4config file during force clean A few ideas/updates: There is a snapshot release 1.2.0 which includes reconcile -l. With Auto Clean it helps to reduce the number of 'p4 where' commands on 150,000 files. I hope this makes things quicker. If you still end up using the force clean option, how about versioning your .p4config in a different location and then map it into the project. e.g. //depot/product_Ace/main/... //workspace/... //depot/dev/alexey/.p4config_product_Ace //workspace/.p4config 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] [cloudfoundry-plugin] (JENKINS-27146) Deploying an applicatin w/ no-route fails because route deletion fails
Andreas Buchen commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails I have two issues: First: when reading the documentation, then deleting the route is not what we want. It would delete the route from the space, however the user might want to keep it. I assume we want to unmap it from the application. Delete a registered route from the space of the current session. Second: at least in the Java client, I can't seem to find an API to map/unmap routes. The CloudAppliation#getUris returns a list of Strings containing the routes. Do you know how to unmap the routes? If there is no API, I am wondering if we should remove the whole "if (deploymentInfo.isNoRoute())" block for now. 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] [git-plugin] (JENKINS-27166) CLONE - Git SCM-polling doesn't work when using a parametrized branch-name
pmv commented on JENKINS-27166 CLONE - Git SCM-polling doesnt work when using a parametrized branch-name Didn't have a chance to test out 2.3.5 - will try next week. 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] [workflow-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
Jesse Glick commented on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Observed to cause a timeout in WorkflowTest.executorStepRestart (JENKINS-26513). 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] [docker-build-publish-plugin] (JENKINS-27132) Build not properly inheriting environment
Mike Saffitz resolved JENKINS-27132 as Not A Defect Build not properly inheriting environment My apologies-- I had a .env file in the root of the directory that the base image was inheriting environment from without my knowledge. This isn't an issue for the docker build plugin Change By: Mike Saffitz (27/Feb/15 11:23 PM) Status: Open Resolved Resolution: NotADefect 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] [docker-build-publish-plugin] (JENKINS-27132) Build not properly inheriting environment
Mike Saffitz closed JENKINS-27132 as Not A Defect Build not properly inheriting environment Change By: Mike Saffitz (27/Feb/15 11:23 PM) 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] [workflow-plugin] (JENKINS-26123) Non-blocking build trigger step
Jesse Glick started work on JENKINS-26123 Non-blocking build trigger step Change By: Jesse Glick (27/Feb/15 10:13 PM) Status: Open InProgress 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-26690) Build stats throws illegal argument exception on dashboard view
dogfood commented on JENKINS-26690 Build stats throws illegal argument exception on dashboard view Integrated in jenkins_main_trunk #3987 FIXED JENKINS-26690 Integer overflow in AbstractLazyLoadRunMap.headMap with negative arguments. (Revision db1f805d68a1aaf8e2d6d1c96cb006fc1dd4c087) Result = SUCCESS jesse glick : db1f805d68a1aaf8e2d6d1c96cb006fc1dd4c087 Files : core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java 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] [testexecuter] (JENKINS-26965) Jenkins test on Master instead of slave have permission denied issues
johnson are commented on JENKINS-26965 Jenkins test on Master instead of slave have permission denied issues Can someone please help me with this please? 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] [customtools-plugin] (JENKINS-27157) Overriding Tool localtion(s) has no effect
Markus Eisenmann created JENKINS-27157 Overriding Tool localtion(s) has no effect Issue Type: Bug Assignee: Oleg Nenashev Components: customtools-plugin Created: 27/Feb/15 11:45 AM Description: I have tested the Custom Tools plugin to (automatically) installing a zip- or tar.gz archive; which works fine. Assuming, that is it possible to overrride the tool-location, I have configured and (alternative) Home (in Configure System - Tool Locations). The previously configured tool (eg. "gcc-4.9.2-i386") is listed in the drop-down box as "(Custom Tool) gcc-4.9.2-i386"; but the configured folder isn't used (in the job-run). The archive is still installed/unpacked in the default-directory (Ie. "C:\..\Jenkins\tools\com.cloudbees.jenkins.plugins.customtools.CustomTool\gcc-4.9.2-i386"). Best regards from Salzburg, Markus Environment: Jenkins 1.599; Windows 7 x64 Java SE Runtime Environment: 1.7.0_25-b17 Project: Jenkins Priority: Major Reporter: Markus Eisenmann 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] [customtools-plugin] (JENKINS-27158) Optionally disable adding home-directory to PATH-environment
Markus Eisenmann created JENKINS-27158 Optionally disable adding home-directory to PATH-environment Issue Type: New Feature Assignee: Oleg Nenashev Components: customtools-plugin Created: 27/Feb/15 11:56 AM Description: IMHO, on special cases it should be possible to disable adding the tools home-directory (or configured sub-folder) to the environment-variable PATH. Sometimes, I've determined side-effects/faults in some (special) batch-files, which are depending on the PATH-variable (specially on the order of added dirs). Therefore, I'm "more" prefer absolute paths (eg. matrix-builds with different GCC-version/toolchains). Best regards from Salzburg, Markus Environment: Jenkins 1.599; Windows 7 x64 Java SE Runtime Environment: 1.7.0_25-b17 Project: Jenkins Priority: Minor Reporter: Markus Eisenmann 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] [customtools-plugin] (JENKINS-27157) Overriding Tool location(s) has no effect
Markus Eisenmann updated JENKINS-27157 Overriding Tool location(s) has no effect Change By: Markus Eisenmann (27/Feb/15 11:57 AM) Summary: OverridingTool localtion location (s)hasnoeffect 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] [customtools-plugin] (JENKINS-27157) Overriding Tool location(s) has no effect
Oleg Nenashev commented on JENKINS-27157 Overriding Tool location(s) has no effect Markus, do you run your job on the master node? The described use-case definitely works well on slaves. 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.
