[JIRA] [job-dsl-plugin] (JENKINS-29501) add support for Crittercism dSYM Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29501 Re: add support for Crittercism dSYM Plugin Code changed in jenkins User: Marc Guenther Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/CrittercismDsymRecorderContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/d068f91efe667eaec4cc8cc8526923af9a1f38ea Log: JENKINS-29501 added support for crittercism plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-30295) Mercurial changeset numbers no longer work with newer versions of email-ext-plugin
Title: Message Title
Iris Hupkens created an issue
Jenkins / JENKINS-30295
Mercurial changeset numbers no longer work with newer versions of email-ext-plugin
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin, mercurial-plugin
Created:
04/Sep/15 9:23 AM
Environment:
Jenkins version 1.591 Mercurial Plugin version 1.51 Email Extension Plugin version 2.40.5 (upgraded from 2.34)
Priority:
Major
Reporter:
Iris Hupkens
Starting with version 2.40 of the Email Extension Plugin, it uses 'getCommitId' on the ChangeLogSet.Entry object to get the commit id. However, the Mercurial Plugin only provides this information through the MercurialChangeset.getRevision method, which the Email Extension Plugin used to access through reflection.
This is breaking e-mail configurations that used to work with Email Extension Plugin version 2.34. Specifically, the problem is that the %r (revision) formatting option for the $ {CHANGES}
option no longer works and will always show as 'null'.
I suspect that the %d (date) option might be broken for a similar reason, though I have not tested that: In this commit: https://github.com/jenkinsci/email-ext-plugin/commit/6453a56cdcc82d2d7f085e8dba9c2b7032cb112a the Email Extension Plugin seems to have been modified to use
[JIRA] [rabbitmq-consumer-plugin] (JENKINS-30297) Meaningless hashed user password of rabbitmq consumer plugin
Title: Message Title Sunchan Lee created an issue Jenkins / JENKINS-30297 Meaningless hashed user password of rabbitmq consumer plugin Issue Type: Bug Assignee: Unassigned Attachments: consumer.jpg Components: rabbitmq-consumer-plugin Created: 04/Sep/15 10:15 AM Environment: Operating System : Ubuntu 14.04 on docker JDK : OpenJDK 7 Jenkins version : 1.565.3 Plugin version : 2.7 Running : Directly (just only executed war file after download) Browser : Chrome 45.0.2454.85 (64-bit) on OS X Priority: Minor Reporter: Sunchan Lee I saw some characters in 'user password' field after saving settings although I left it blank. Please see attached image, 'consumer.jpg'. So I opened configuration file, org.jenkinsci.plugins.rabbitmqconsumer.GlobalRabbitmqConfiguration.xml and then found a hashed value like '_onZ0hovXkMgFroQGV47AXw_==' in 'userPassword' entity. I don't know about origin of that hash value. This plugin performs action for updating rabbitmq connection if I left
[JIRA] [job-dsl-plugin] (JENKINS-29501) add support for Crittercism dSYM Plugin
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.38. Jenkins / JENKINS-29501 add support for Crittercism dSYM Plugin Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-30294) Error on login popup screen : /login?from=%2Fjob%2FJobName3%2FconfigSubmit
Title: Message Title ashutosh yadav assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-30294 Error on login popup screen : /login?from=%2Fjob%2FJobName3%2FconfigSubmit Change By: ashutosh yadav Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Piyush Jain edited a comment on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I am using latest 1.10 workflow plugin in Jenkins 1.609.2 LTS Jenkins. I am seeing same issue while executing batch command, it do not return back to command prompt. 1. *jenkins-wrap.bat (on windows slave)*call "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-main.bat" > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-log.txt" 2>&1echo %ERRORLEVEL% > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-result.txt" 2. * * jenkins-main.bat (on windows slave)* * cd %ITEST_HOME% %OSP_SDVT_3RDGEN_BASELINE_COMMAND% 3. * * jenkins-result.txt (on windows slave) * * 0 4. *jenkins-log.txt(on windows slave) *C:\JenkinsSlave\workspace\osp_test_pipeline_taml>cd C:\Program Files (x86)\Spirent Communications\iTest 4.2 C:\Program Files (x86)\Spirent Communications\iTest 4.2>itestcli -rw -P project://SDVT_Smokecheck/Tier2/Parmeters/OSP_Tier1_SmokeCheck.ffpt -p upgrade/imagepath_ta5k=/TAML.D2287/OSP/ -p upgrade/aucfilename_ta5k=OSP-TAMLD2287.auc -w C:\iTest\3GEN project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftcitestcli Command Processor Version 4.2.2Copyright (c) 2006-2013, Spirent CommunicationsExecuting testcase: 'project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftc' ...Execution started at: Fri Sep 04 03:59:40 CDT 2015Test owner: Sev. OriginSession Step Index Procedure Message===Info executionmain Execution startedPass analysis 18.1 3.1main Baseline test passedPass execution 18.1 3.1main Test case Smoke_System_GreenUp has passed.Info execution Execution completed (2s)Execution finished at: Fri Sep 04 03:59:43 CDT 2015Execution Status: Pass---This script runs fine , shows execution status Pass, but jenkins build gets hung after that in workflow based builds , seems like exit command is not getting auto updated in jenkins-wrap.bat & jenkins-main.bat files.can someone look into it & fix it asap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Piyush Jain edited a comment on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I am using latest 1.10 workflow plugin in Jenkins 1.609.2 LTS Jenkins. I am seeing same issue while executing batch command, it do not return back to command prompt.*jenkins-wrap.bat (on windows slave)*call "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-main.bat" > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-log.txt" 2>&1echo %ERRORLEVEL% > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-result.txt"* * jenkins-main.bat (on windows slave)* * cd %ITEST_HOME% %OSP_SDVT_3RDGEN_BASELINE_COMMAND% * * jenkins-result.txt (on windows slave) * * 0 *jenkins-log.txt(on windows slave) *C:\JenkinsSlave\workspace\osp_test_pipeline_taml>cd C:\Program Files (x86)\Spirent Communications\iTest 4.2 C:\Program Files (x86)\Spirent Communications\iTest 4.2>itestcli -rw -P project://SDVT_Smokecheck/Tier2/Parmeters/OSP_Tier1_SmokeCheck.ffpt -p upgrade/imagepath_ta5k=/TAML.D2287/OSP/ -p upgrade/aucfilename_ta5k=OSP-TAMLD2287.auc -w C:\iTest\3GEN project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftcitestcli Command Processor Version 4.2.2Copyright (c) 2006-2013, Spirent CommunicationsExecuting testcase: 'project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftc' ...Execution started at: Fri Sep 04 03:59:40 CDT 2015Test owner: Sev. OriginSession Step Index Procedure Message===Info executionmain Execution startedPass analysis 18.1 3.1main Baseline test passedPass execution 18.1 3.1main Test case Smoke_System_GreenUp has passed.Info execution Execution completed (2s)Execution finished at: Fri Sep 04 03:59:43 CDT 2015Execution Status: Pass---This script runs fine , shows execution status Pass, but jenkins build gets hung after that in workflow based builds , seems like exit command is not getting auto updated in jenkins-wrap.bat & jenkins-main.bat files.can someone look into it & fix it asap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-pipeline-plugin] (JENKINS-29477) View bad for Build Pipeline Plugin
Title: Message Title
John Wynne commented on JENKINS-29477
Re: View bad for Build Pipeline Plugin
Thanks a million Phillip! That's fixed it alright! I agree that your solution should be the resolution for this ticket:
#main-panel
Unknown macro: { margin-left}
I'm not active with git either and am quite new to this, but cheers for your help!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-29477) View bad for Build Pipeline Plugin
Title: Message Title
John Wynne edited a comment on JENKINS-29477
Re: View bad for Build Pipeline Plugin
Thanks a million Phillip! That's fixed it alright! :)I agree that your solution should be the resolution for this ticket: {quote}#main-panel / { margin-left:0px; display: inline-block; min-width:100%; / }{quote}I'm not active with git either and am quite new to this, but cheers for your help!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-30302) Matrix parent takes executor slot and blocks children
Title: Message Title Joachim Herb created an issue Jenkins / JENKINS-30302 Matrix parent takes executor slot and blocks children Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 04/Sep/15 11:50 AM Environment: Jenkins: 1.627 Matrix Project Plugin: 1.6 Labels: plugin configuration Priority: Major Reporter: Joachim Herb The problem reported in https://issues.jenkins-ci.org/browse/JENKINS-23902 (Matrix parent takes executor slot and blocks children) is still occuring. I have 4 build executors and 4 (or more) jobs should be started by build triggers with the option "Block until the triggered projects finish their builds" set. This results in 4 parent matrix jobs filling up the build executors so no actual build jobs can be started leading to a dead lock. Only killing some of these parent jobs results in the start of the actuall build jobs.
[JIRA] [_test] (JENKINS-30303) After upgrading Jenkins to 1.609.2 and JDK 1.8.0_45, previous build history show timestamps of 45 year old
Title: Message Title Mike HongMa created an issue Jenkins / JENKINS-30303 After upgrading Jenkins to 1.609.2 and JDK 1.8.0_45, previous build history show timestamps of 45 year old Issue Type: Bug Assignee: Oleg Nenashev Attachments: screen_shot.docx Components: _test Created: 04/Sep/15 12:24 PM Environment: Redhat Linux JDK 1.8.0_45 Jenkins 1.609.2 Priority: Minor Reporter: Mike HongMa Add Comment
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Piyush Jain edited a comment on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I am using latest 1.10 workflow plugin in Jenkins 1.609.2 LTS Jenkins. I am seeing same issue while executing batch command, it do not return back to command prompt.1. * jenkins-wrap.bat (on windows slave)*call "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-main.bat" > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-log.txt" 2>&1echo %ERRORLEVEL% > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-result.txt"2. *jenkins-main.bat (on windows slave)*cd %ITEST_HOME% %OSP_SDVT_3RDGEN_BASELINE_COMMAND% 3. *jenkins-result.txt (on windows slave)*0 4. *jenkins-log.txt(on windows slave)*C:\JenkinsSlave\workspace\osp_test_pipeline_taml>cd C:\Program Files (x86)\Spirent Communications\iTest 4.2 C:\Program Files (x86)\Spirent Communications\iTest 4.2>itestcli -rw -P project://SDVT_Smokecheck/Tier2/Parmeters/OSP_Tier1_SmokeCheck.ffpt -p upgrade/imagepath_ta5k=/TAML.D2287/OSP/ -p upgrade/aucfilename_ta5k=OSP-TAMLD2287.auc -w C:\iTest\3GEN project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftcitestcli Command Processor Version 4.2.2Copyright (c) 2006-2013, Spirent CommunicationsExecuting testcase: 'project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftc' ...Execution started at: Fri Sep 04 03:59:40 CDT 2015Test owner: Sev. OriginSession Step Index Procedure Message===Info executionmain Execution startedPass analysis 18.1 3.1main Baseline test passedPass execution 18.1 3.1main Test case Smoke_System_GreenUp has passed.Info execution Execution completed (2s)Execution finished at: Fri Sep 04 03:59:43 CDT 2015Execution Status: Pass---This script runs fine , shows execution status Pass, but jenkins build gets hung after that in workflow based builds , seems like exit command is not getting auto updated in jenkins-wrap.bat & jenkins-main.bat files.can someone look into it & fix it asap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [gitlab-plugin] (JENKINS-30298) Gitlab plugin doesn't start build automatically on request from gitlab server
Title: Message Title Igor Vasilev created an issue Jenkins / JENKINS-30298 Gitlab plugin doesn't start build automatically on request from gitlab server Issue Type: Bug Assignee: Unassigned Components: gitlab-plugin Created: 04/Sep/15 10:16 AM Environment: Plugin version 1.1.26 Jenkins 1.627 Gitlab 7.12.1 Priority: Minor Reporter: Igor Vasilev Gitlab tries to start the build but the plugin raises an exception: WARNING: Error while serving http://HOST/project/PROJECT java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor217.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:409) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) 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
[JIRA] [other] (JENKINS-30294) Error on login popup screen : /login?from=%2Fjob%2FJobName3%2FconfigSubmit
Title: Message Title
ashutosh yadav updated an issue
Jenkins / JENKINS-30294
Error on login popup screen : /login?from=%2Fjob%2FJobName3%2FconfigSubmit
Change By:
ashutosh yadav
My Jenkins was idle for sometime and then i got a pop screen asking for login again. I gave my credentials and then clicked on login, But nothing happened. The login button does not work .Again i closed the popup and the clicked on login at the top right corner , gave the credentials and clicked on loging , but got the below error :javax.servlet.ServletException: This page expects a form submission but had only {} at org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:910) at hudson.model.Job.doConfigSubmit(Job.java:1183) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:794) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) 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$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:723) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Piyush Jain commented on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I am using latest 1.10 workflow plugin in Jenkins 1.609.2 LTS Jenkins. I am seeing same issue while executing batch command, it do not return back to command prompt. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-24208) ignore users in GitHub plugin
Title: Message Title Christophe Lallement commented on JENKINS-24208 Re: ignore users in GitHub plugin I'm exactly in the same configuration: Our jenkins instance hosts some some jobs typed as "Continuous delivery". Thos jobs are triggered by github with this plugin. So it means we compile, package execute some test and release it automatically The release means changing version inside the pom.xml and pushing into the remote repository in order to share the new version (snapshot) across all developers. ... and there we enter in a loop because after pushing, github detect a change and call back again jenkins So it could be nice in the admin section of the plugin (or maybe per project) to be able to enter a "blacklist/ignore) username. In case where this username field is set, the plugin ignore commit done by this user Do you think possible to do this type of enhancement ? Thx Christophe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tasks-plugin] (JENKINS-30289) Tasks plugin exception
Title: Message Title Ulli Hafner closed an issue as Duplicate Jenkins / JENKINS-30289 Tasks plugin exception Change By: Ulli Hafner Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Piyush Jain edited a comment on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I am using latest 1.10 workflow plugin in Jenkins 1.609.2 LTS Jenkins. I am seeing same issue while executing batch command, it do not return back to command prompt. *jenkins-wrap.bat (on windows slave)*call "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-main.bat" > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-log.txt" 2>&1echo %ERRORLEVEL% > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-result.txt"*jenkins-main.bat (on windows slave)*cd %ITEST_HOME% %OSP_SDVT_3RDGEN_BASELINE_COMMAND% *jenkins-result.txt (on windows slave) * 0 *jenkins-log.txt(on windows slave) *C:\JenkinsSlave\workspace\osp_test_pipeline_taml>cd C:\Program Files (x86)\Spirent Communications\iTest 4.2 C:\Program Files (x86)\Spirent Communications\iTest 4.2>itestcli -rw -P project://SDVT_Smokecheck/Tier2/Parmeters/OSP_Tier1_SmokeCheck.ffpt -p upgrade/imagepath_ta5k=/TAML.D2287/OSP/ -p upgrade/aucfilename_ta5k=OSP-TAMLD2287.auc -w C:\iTest\3GEN project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftcitestcli Command Processor Version 4.2.2Copyright (c) 2006-2013, Spirent CommunicationsExecuting testcase: 'project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftc' ...Execution started at: Fri Sep 04 03:59:40 CDT 2015Test owner: Sev. OriginSession Step Index Procedure Message===Info executionmain Execution startedPass analysis 18.1 3.1main Baseline test passedPass execution 18.1 3.1main Test case Smoke_System_GreenUp has passed.Info execution Execution completed (2s)Execution finished at: Fri Sep 04 03:59:43 CDT 2015Execution Status: Pass---This script runs fine , shows execution status Pass, but jenkins build gets hung after that in workflow based builds , seems like exit command is not getting auto updated in jenkins-wrap.bat & jenkins-main.bat files.can someone look into it & fix it asap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Piyush Jain edited a comment on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I am using latest 1.10 workflow plugin in Jenkins 1.609.2 LTS Jenkins. I am seeing same issue while executing batch command, it do not return back to command prompt.*jenkins-wrap.bat (on windows slave)*call "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-main.bat" > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-log.txt" 2>&1echo %ERRORLEVEL% > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-result.txt"*jenkins-main.bat (on windows slave)*cd %ITEST_HOME% %OSP_SDVT_3RDGEN_BASELINE_COMMAND% *jenkins-result.txt (on windows slave) * 0 *jenkins-log.txt(on windows slave) *C:\JenkinsSlave\workspace\osp_test_pipeline_taml>cd C:\Program Files (x86)\Spirent Communications\iTest 4.2 C:\Program Files (x86)\Spirent Communications\iTest 4.2>itestcli -rw -P project://SDVT_Smokecheck/Tier2/Parmeters/OSP_Tier1_SmokeCheck.ffpt -p upgrade/imagepath_ta5k=/TAML.D2287/OSP/ -p upgrade/aucfilename_ta5k=OSP-TAMLD2287.auc -w C:\iTest\3GEN project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftcitestcli Command Processor Version 4.2.2Copyright (c) 2006-2013, Spirent CommunicationsExecuting testcase: 'project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftc' ...Execution started at: Fri Sep 04 03:59:40 CDT 2015Test owner: Sev. OriginSession Step Index Procedure Message===Info executionmain Execution startedPass analysis 18.1 3.1main Baseline test passedPass execution 18.1 3.1main Test case Smoke_System_GreenUp has passed.Info execution Execution completed (2s)Execution finished at: Fri Sep 04 03:59:43 CDT 2015Execution Status: Pass---This script runs fine , shows execution status Pass, but jenkins build gets hung after that in workflow based builds , seems like exit command is not getting auto updated in jenkins-wrap.bat & jenkins-main.bat files.can someone look into it & fix it asap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Piyush Jain edited a comment on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I am using latest 1.10 workflow plugin in Jenkins 1.609.2 LTS Jenkins. I am seeing same issue while executing batch command, it do not return back to command prompt. All these four files are auto generated by jenkins workflow on jenkins slave workspace 1. *jenkins-wrap.bat (on windows slave)*call "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-main.bat" > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-log.txt" 2>&1echo %ERRORLEVEL% > "C:\JenkinsSlave\workspace\osp_test_pipeline_taml\.0401c727\jenkins-result.txt"2. *jenkins-main.bat (on windows slave)*cd %ITEST_HOME% %OSP_SDVT_3RDGEN_BASELINE_COMMAND% 3. *jenkins-result.txt (on windows slave)*0 4. *jenkins-log.txt(on windows slave)*C:\JenkinsSlave\workspace\osp_test_pipeline_taml>cd C:\Program Files (x86)\Spirent Communications\iTest 4.2 C:\Program Files (x86)\Spirent Communications\iTest 4.2>itestcli -rw -P project://SDVT_Smokecheck/Tier2/Parmeters/OSP_Tier1_SmokeCheck.ffpt -p upgrade/imagepath_ta5k=/TAML.D2287/OSP/ -p upgrade/aucfilename_ta5k=OSP-TAMLD2287.auc -w C:\iTest\3GEN project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftcitestcli Command Processor Version 4.2.2Copyright (c) 2006-2013, Spirent CommunicationsExecuting testcase: 'project://SDVT_Smokecheck/Tier2/TestCases/Smoke_System_GreenUp.fftc' ...Execution started at: Fri Sep 04 03:59:40 CDT 2015Test owner: Sev. OriginSession Step Index Procedure Message===Info executionmain Execution startedPass analysis 18.1 3.1main Baseline test passedPass execution 18.1 3.1main Test case Smoke_System_GreenUp has passed.Info execution Execution completed (2s)Execution finished at: Fri Sep 04 03:59:43 CDT 2015Execution Status: Pass---This script runs fine , shows execution status Pass, but jenkins build gets hung after that in workflow based builds , seems like exit command is not getting auto updated in jenkins-wrap.bat & jenkins-main.bat files.can someone look into it & fix it asap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-30221) Job DSL plugin should expose additional DeliveryPipelineView configuration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30221 Re: Job DSL plugin should expose additional DeliveryPipelineView configuration Code changed in jenkins User: alexander.komarov Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/views/DeliveryPipelineView.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/views/DeliveryPipelineViewSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f6ce8d023a7c05f57104b48504dd1106ff033c18 Log: Implementation of JENKINS-30221 , support for additional settings in the Delivery Pipeline View configuration Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-30221) Job DSL plugin should expose additional DeliveryPipelineView configuration
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.38. Jenkins / JENKINS-30221 Job DSL plugin should expose additional DeliveryPipelineView configuration Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title Victor Martinez created an issue Jenkins / JENKINS-30296 Infinite loop (pooling changes continuously) when using "*/master" branches to build Issue Type: Bug Assignee: Nicolas De Loof Attachments: Failure.png, Failure_History.png, Workaround.png Components: git-plugin Created: 04/Sep/15 10:00 AM Environment: Git plugin version: 2.3.5 Jenkins version: 1.599 Labels: git-plugin pollscm polling Priority: Major Reporter: Victor Martinez Hi there, For some reason if the branch value is set as "*/master" it keeps polling and building forever even though it doesn't have any scm polling configuration at all, firstly you need to trigger that job manually once and then that
[JIRA] [conditional-buildstep-plugin] (JENKINS-30299) Conditional Build plugin - allow drag-drop of build steps into conditional wrapper
Title: Message Title Matthew Allwood created an issue Jenkins / JENKINS-30299 Conditional Build plugin - allow drag-drop of build steps into conditional wrapper Issue Type: Improvement Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin Created: 04/Sep/15 11:26 AM Environment: Windows, Jenkins 1.627 Priority: Minor Reporter: Matthew Allwood You are already able to drag-drop buildsteps to change the ordering. It would be very useful if you could also drag an existing buildstep into a conditional buildstep (either single or multiple). As an alternative if that's not possible then allow a copy mechanism to copy an existing buildstep that could then be deleted (though this would make it hard to remove buildsteps from the conditional wrapper, so may need an 'unwrap' facility that copies the wrapped step into the main list of buildsteps) I'd imagine this would be supported by default if the behaviour is implemented, but dragging between conditional wrappers would also be nice to have.
[JIRA] [github-plugin] (JENKINS-24208) ignore users in GitHub plugin
Title: Message Title Christophe Lallement edited a comment on JENKINS-24208 Re: ignore users in GitHub plugin I'm exactly in the same configuration:Our jenkins instance hosts some some jobs typed as "Continuous delivery". Thos Those jobs are triggered by github with this plugin.So it means we compile, package execute some test and then release it automatically The At some point, release means changing version inside the pom.xml and pushing into the remote repository in order to share the new version (snapshot) across all developers and there we enter in a loop because after pushing, github detect a change and call back again jenkinsSo it could be nice in the admin section of the plugin (or maybe per project) to be able to enter a "blacklist/ignore) username.In case where this username field is set, the plugin ignore commit done by this userDo you think possible to do this type of enhancement ?ThxChristophe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-27250) p4 plugin does not respect line endings setting
Title: Message Title Rami Alia commented on JENKINS-27250 Re: p4 plugin does not respect line endings setting Hello, I wanted to add that on windows attempting to set Unix line endings or any line ending other than Local in manual spec (no .RSRC file) is not being respected with 1.3.0. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30300) Unable to specify a branch to build when using paramatized job
Title: Message Title Adrian Moisey created an issue Jenkins / JENKINS-30300 Unable to specify a branch to build when using paramatized job Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 04/Sep/15 11:37 AM Priority: Minor Reporter: Adrian Moisey When having a job that is configured to build multiple branches, it is impossible to use the paramatized build to run a particular job. Instead the latest branch is build. If I have a job that builds "origin/master", "origin/release" and "origin/$branch" (for the parameter), and I try build "origin/potato", then the last built branch always builds, not the one I specify in the parameter. Add Comment
[JIRA] [other] (JENKINS-30294) Error on login popup screen : /login?from=%2Fjob%2FJobName3%2FconfigSubmit
Title: Message Title ashutosh yadav commented on JENKINS-30294 Re: Error on login popup screen : /login?from=%2Fjob%2FJobName3%2FconfigSubmit Not sure whom to assign this issue. Please suggest Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rabbitmq-consumer-plugin] (JENKINS-30297) Meaningless hashed user password of rabbitmq consumer plugin
Title: Message Title Sunchan Lee updated an issue Jenkins / JENKINS-30297 Meaningless hashed user password of rabbitmq consumer plugin Change By: Sunchan Lee I saw some characters in 'user password' field after saving settings although I left it blank.Please see attached image, 'consumer.jpg'.So I opened configuration file, org.jenkinsci.plugins.rabbitmqconsumer.GlobalRabbitmqConfiguration.xml and then found a hashed value like '_onZ0hovXkMgFroQGV47AXw_==' in 'userPassword' entity.I don't know about origin of that hash value.This plugin performs action for updating rabbitmq connection if I left 'user password' blank again because blank password is not same with saved hash value.I think this is a minor bug and can be resolved easily.So I'll try to solve this problem if anybody doesn't resolve this issue . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-29477) View bad for Build Pipeline Plugin
Title: Message Title
John Wynne edited a comment on JENKINS-29477
Re: View bad for Build Pipeline Plugin
Thanks a million Phillip! That's fixed it alright! :)I agree that your solution should be the resolution for this ticket: {quote} #main-panel/{ margin-left:0px; display: inline-block; min-width:100%; /} {quote}I'm not active with git either and am quite new to this, but cheers for your help!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-29477) View bad for Build Pipeline Plugin
Title: Message Title
Phillip K. commented on JENKINS-29477
Re: View bad for Build Pipeline Plugin
Hey John! I only tested the the css with overflowing content. Inline-block apdapts its size to the size of its content. Sorry for that! This modified rule should remove the left margin, prevent overflowing content and expand the box to at least the width of your screen. I tested it with Firefox only.
#main-panel { margin-left:0px; display: inline-block; min-width:100%; }
I'm not an active github user, so i will not promise anything, but i will try to get this modification into the repo.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30301) JenkinsRule.WebClient.setThrowExceptionOnScriptError(false) generates a Javascript exception itself
Title: Message Title
Kirill Shepitko created an issue
Jenkins / JENKINS-30301
JenkinsRule.WebClient.setThrowExceptionOnScriptError(false) generates a _javascript_ exception itself
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
04/Sep/15 11:40 AM
Environment:
Jenkins version: 1.580.3 OS: Windows 7 Professional Java version: 1.8
Priority:
Minor
Reporter:
Kirill Shepitko
I wrote an integration test for my post-build action aka Publisher following the guidelines in https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test to test configuration round-trip.
To prevent test from failing with _javascript_ scripts I set JenkinsRule.WebClient.setThrowExceptionOnScriptError(false). However, after this I got the following in my test output console:
Sep 04, 2015 12:01:13 PM com.gargoylesoftware.htmlunit._javascript_._javascript_Engine handleJavaScriptException
INFO: Caught script exception
=== EXCEPTION START
EcmaError: lineNumber=[26] column=[0] lineSource=[ if (inputs[i].type == "checkbox" || inputs[i].type == "radio") {] name=[TypeError] sourceName=[http://localhost:54301/jenkins/adjuncts/2bdd1129/lib/form/confirm.js]
[JIRA] [core] (JENKINS-30303) After upgrading Jenkins to 1.609.2 and JDK 1.8.0_45, previous build history show timestamps of 45 year old
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-30303 After upgrading Jenkins to 1.609.2 and JDK 1.8.0_45, previous build history show timestamps of 45 year old Which versions did you use before? Change By: Oleg Nenashev Component/s: core Component/s: _test Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstestrunner-plugin] (JENKINS-30292) MSTestRunner Plugin not visible in Conditional BuildStep Plugin
Title: Message Title Dominik Bartholdi assigned an issue to Ido Ran Jenkins / JENKINS-30292 MSTestRunner Plugin not visible in Conditional BuildStep Plugin Change By: Dominik Bartholdi Component/s: conditional-buildstep-plugin Assignee: Dominik Bartholdi Ido Ran Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-30306) SCM plugin stops working after adding a slave
Title: Message Title Jeff Weiss created an issue Jenkins / JENKINS-30306 SCM plugin stops working after adding a slave Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 04/Sep/15 1:21 PM Environment: CentOS 7 Priority: Minor Reporter: Jeff Weiss After adding a slave, the plugin stops working and gives the following stacktrace. Seems to be trying to interfere with a slave and failing. Why it's even attempting to do that, I have no idea. ep 04, 2015 12:51:53 PM hudson.model.Executor finish2 WARNING: Executor #1 for cislave01.. : executing jobxx #501 termination trace hudson.model.Computer$TerminationRequest: Termination requested at Mon Aug 31 15:25:13 UTC 2015 by Thread[Handling POST /ci1/computer/cislave01../doDisconnect from 24.163.59.216 : RequestHandlerThread11,5,main] [id=32] from HTTP request for https://ci../ci1/computer/cislave01../doDisconnect at hudson.model.Computer.recordTermination(Computer.java:208) at hudson.model.Computer.disconnect(Computer.java:479) at hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:596) at hudson.slaves.SlaveComputer.doDoDisconnect(SlaveComputer.java:589) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at
[JIRA] [jira-plugin] (JENKINS-30305) Allow CLI parameter submission for JiraVersionParameterDefinition
Title: Message Title Radek Antoniuk created an issue Jenkins / JENKINS-30305 Allow CLI parameter submission for JiraVersionParameterDefinition Issue Type: Improvement Assignee: Radek Antoniuk Components: jira-plugin Created: 04/Sep/15 1:00 PM Priority: Minor Reporter: Radek Antoniuk Currently the plugin does not allow configuration via CLI, which make it impossible for us to automate some build with something like : java -jar jenkins-cli.jar -s https://ci.example.com/ build Project-2.33-Release -f -p JiraBuild=2.33.28 CLI parameter submission is not supported for the class hudson.plugins.jira.versionparameter.JiraVersionParameterDefinition type. Add Comment
[JIRA] [junit-plugin] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title rsandell commented on JENKINS-27395 Re: distinguish test reports filed from different parts of workflow I didn't notice this ticket until after I wrote https://github.com/jenkinsci/junit-plugin/pull/27 and https://github.com/jenkinsci/parallel-test-executor-plugin/pull/16 My suggested approach doesn't provide any visual difference in the test report, since suite names isn't rendered anywhere iiuc. But it serves a way for other parts of the flow to use that info, like the parallel test executor. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30283) syntax error determining changeset
Title: Message Title Mark Waite commented on JENKINS-30283 Re: syntax error determining changeset I launched a Jenkins master on my CentOS 7 machine and confirmed that it is able to show changes correctly through both the "Recent Changes" and the "Changes" links of the job page. The CentOS 7 machine I'm running also has git 1.8.3.1, just as your does. Are you clicking a link other that "Changes" or "Recent Changes" when you see that problem? It almost seems as if something is causing the quotes surrounding the format definition to be stripped from the string before it is passed to the git program. I'm sorry, but I'm at a loss to guess what makes your configuration different from mine, and different from others which are running successfully. Is there anything in the Jenkins environment which might cause the quoting to be altered? Do you have a script named "git" which is somehow earlier in the path and which then attempts to pass its arguments to the actual git implementation? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-30291) Side effect of Email-ext plugin to Git
Title: Message Title Alex Earl commented on JENKINS-30291 Re: Side effect of Email-ext plugin to Git Email-ext doesn't change any environment variables. I really doubt this is caused by email ext. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30283) syntax error determining changeset
Title: Message Title Douglas Seay closed an issue as Fixed User error. In an earlier test of git I had shimmed in something which echo'd the command before exec'ing the real git. That extra output must have messed up some parsing. Getting rid of the shim fixed it. I'm sorry to have bothered everyone. Jenkins / JENKINS-30283 syntax error determining changeset Change By: Douglas Seay Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title Mark Waite commented on JENKINS-30296 Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build Can you post your job definition which is showing the problem, the git polling log which reports the change, and any other hints that might help someone else duplicate the problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-30242) Update to 1.13.2 breaks global configuration submission when jira-plugin installed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30242 Re: Update to 1.13.2 breaks global configuration submission when jira-plugin installed Code changed in jenkins User: Radosław Antoniuk Path: src/main/java/hudson/plugins/jira/JiraProjectProperty.java src/test/java/hudson/plugins/jira/EmptyFriendlyURLConverterTest.java http://jenkins-ci.org/commit/jira-plugin/286a5320efb653f4ffb8be23a9b0f452c3ac15c4 Log: Merge pull request #60 from lanwen/ JENKINS-30242 _fix [FIXES JENKINS-30242] don't cast object in converter to string Compare: https://github.com/jenkinsci/jira-plugin/compare/b14eac482984...286a5320efb6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-30226) MultiJob getting "stuck" after all child jobs complete
Title: Message Title Robert Schultheis commented on JENKINS-30226 Re: MultiJob getting "stuck" after all child jobs complete This is our threaddump: "Executor #3 for master : executing testing_a #492" Id=33948 Group=main TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@78bff354 at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@78bff354 at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) at java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:389) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:216) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) at hudson.model.Run.execute(Run.java:1741) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) It looks different than yours Camilo Sperberg. Wish I had ideas... but I dont. Have attempted to use the 'stress' command line tool to induce CPU and IO load to get it to reproduce less randomly. When it has reproduced... I've noticed that there is high CPU load on the box. But my many attempts at that were not sucessful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-30283) syntax error determining changeset
Title: Message Title Douglas Seay commented on JENKINS-30283 Re: syntax error determining changeset Mark, thanks for taking time from your conference to talk to me about this. I appreciate it. I agree that it is likely to be on my end in that I don't think I'm doing anything that isn't pretty close to default. I'd hope that clicking boxes isn't going to break this sort of thing. The line "git whatchanged --no-abbrev -M --format=commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b -n 1024 d90fbc8159fcfe465fad42c4af4c5b502111e709 ^d90fbc8159fcfe465fad42c4af4c5b502111e709" shows the problem. The word "commit" is not one of the valid values for --format. My guess is that string construction is what has gone wonky. I don't have any idea how I could have broken that. Just in case, here are more version numbers from rpm [RHEL7.0] doug@doug-rhel7-base:~> rpm --query --all | grep -i java | sort java-1.8.0-openjdk-1.8.0.51-1.b16.el7_1.x86_64 java-1.8.0-openjdk-headless-1.8.0.51-1.b16.el7_1.x86_64 javapackages-tools-3.4.1-6.el7_0.noarch python-javapackages-3.4.1-6.el7_0.noarch tzdata-java-2015e-1.el7.noarch [RHEL7.0] doug@doug-rhel7-base:~> rpm --query --all | grep -i git | sort crontabs-1.11-6.20121102git.el7.noarch git-1.8.3.1-4.el7.x86_64 git-daemon-1.8.3.1-4.el7.x86_64 git-svn-1.8.3.1-4.el7.x86_64 libertas-sd8686-firmware-20140213-0.3.git4164c23.el7.noarch libertas-sd8787-firmware-20140213-0.3.git4164c23.el7.noarch libertas-usb8388-firmware-20140213-0.3.git4164c23.el7.noarch linux-firmware-20140213-0.3.git4164c23.el7.noarch ModemManager-glib-1.1.0-6.git20130913.el7.x86_64 NetworkManager-0.9.9.1-13.git20140326.4dba720.el7.x86_64 NetworkManager-config-server-0.9.9.1-13.git20140326.4dba720.el7.x86_64 NetworkManager-glib-0.9.9.1-13.git20140326.4dba720.el7.x86_64 NetworkManager-tui-0.9.9.1-13.git20140326.4dba720.el7.x86_64 perl-Git-1.8.3.1-4.el7.noarch xdg-utils-1.1.0-0.16.20120809git.el7.noarch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-30276) Jenkins GIT Plugin fails on initial clone
Title: Message Title Mark Waite commented on JENKINS-30276 Re: Jenkins GIT Plugin fails on initial clone I'm impressed if it is a bug in the plugin, since that would mean you've found a case which 6+ other installations of the plugin have not detected. That is certainly possible, though it seems less likely than there being something which changed locally on your machine that caused the problem to occur. The stack trace includes: Cannot read file C:\Jenkins\caches\git-02c0446b939beedabfea0b1e39a6132f\.git\config That is a surprising name for a file being attempted to read. It seems to include a SHA1 in the directory name. Is that intentional? Is the workspace intentionally stored in a directory named "caches" with a job name "git-02c0446b939beedabfea0b1e39a6132f"? Can you provide steps that will allow someone else to duplicate the bug outside your environment? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-29900) links of trendDetails are 404 Error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29900 Re: links of trendDetails are 404 Error Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/test/java/plugins/AbstractAnalysisTest.java http://jenkins-ci.org/commit/acceptance-test-harness/e38955e49e1ef6d147d8b09191d59674e46022f3 Log: JENKINS-29900 Improved test so that detail trend graph is verified, too. Still has a workaround for JENKINS-30304. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-30308) Make it possible to use Job parameter as list of needed resources
Title: Message Title Thomas Van Engeland created an issue Jenkins / JENKINS-30308 Make it possible to use Job parameter as list of needed resources Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 04/Sep/15 1:28 PM Priority: Major Reporter: Thomas Van Engeland It would be great if it was possible to use a Job parameter as list of needed resources. My problem: I have a Job which runs a test. The test to run is given to the test Runner Job as an argument. A have a lot of these tests which can run in parallel depending on the resources needed by the test. It would be nice if I just have 1 test runner Job which takes the test to run and the needed resources as a parameter. Add Comment
[JIRA] [p4-plugin] (JENKINS-30307) Matrix variables cannot be used in workspace view path or stream path
Title: Message Title
Rami Alia created an issue
Jenkins / JENKINS-30307
Matrix variables cannot be used in workspace view path or stream path
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
04/Sep/15 1:28 PM
Environment:
Windows 8, Perforce 2014.3, Jenkins
Priority:
Trivial
Reporter:
Rami Alia
Matrix variables cannot be used in stream and manual workspaces. So given a target target and dev/main variable you can't set a stream depot of //depot/$ {target} or use ${target}
in the work space paths.
Add Comment
[JIRA] [core] (JENKINS-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27223 Re: Clicking Login when you have 30+ slaves defaults you to the bottom of the web page Daniel Beck Could you attach a screenshot? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30283) syntax error determining changeset
Title: Message Title Mark Waite commented on JENKINS-30283 Re: syntax error determining changeset It was not the extra output, but the failure to handle args with spaces in the shim. That is very hard to do in a shell script Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30304) Footer hides trend graph links
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-30304 Footer hides trend graph links Issue Type: Bug Assignee: Unassigned Attachments: Bildschirmfoto 2015-09-04 um 14.41.42.png Components: core Created: 04/Sep/15 12:44 PM Labels: user-experience Priority: Minor Reporter: Ulli Hafner In the project view (job page) the links below the last trend graph are not clickable since the footer overlaps these links. It happens only if you have several trend graphs so you need to scroll the page in order to view the bottom one.
[JIRA] [p4-plugin] (JENKINS-24025) Unable to set line ending format for stream workspace
Title: Message Title Rami Alia commented on JENKINS-24025 Re: Unable to set line ending format for stream workspace On 1.3.0 you cannot set line endings at all in manual. I've had to resort to static workspaces for some environments. Specifically am unable to set unix line endings on windows jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-29900) links of trendDetails are 404 Error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29900 Re: links of trendDetails are 404 Error Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/AbstractProjectAction.java src/main/java/hudson/plugins/analysis/graph/BuildResultGraph.java src/main/java/hudson/plugins/analysis/graph/GraphConfigurationView.java http://jenkins-ci.org/commit/analysis-core-plugin/77df032dc5870e09a75768d77ae0f552e6d5aef4 Log: [FIXED JENKINS-29900] Use prefix "../../" for URLs in detail trend graph view. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-29900) links of trendDetails are 404 Error
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29900 links of trendDetails are 404 Error Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30304) Footer hides trend graph links
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30304 Re: Footer hides trend graph links Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/test/java/plugins/AbstractAnalysisTest.java http://jenkins-ci.org/commit/acceptance-test-harness/e38955e49e1ef6d147d8b09191d59674e46022f3 Log: JENKINS-29900 Improved test so that detail trend graph is verified, too. Still has a workaround for JENKINS-30304. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-30305) Allow CLI parameter submission for JiraVersionParameterDefinition
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-30305 Allow CLI parameter submission for JiraVersionParameterDefinition Change By: Radek Antoniuk Labels: jira-plugin-2.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-30305) Allow CLI parameter submission for JiraVersionParameterDefinition
Title: Message Title Radek Antoniuk resolved as Fixed Now merged into master. Jenkins / JENKINS-30305 Allow CLI parameter submission for JiraVersionParameterDefinition Change By: Radek Antoniuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-30291) Side effect of Email-ext plugin to Git
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-30291 Side effect of Email-ext plugin to Git Change By: Mark Waite Component/s: git-client-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30304) Footer hides trend graph links
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-30304 Footer hides trend graph links Change By: Ulli Hafner In the project view (job page) the links below the last trend graph are not clickable since the footer overlaps these links. It happens only if you have several trend graphs so you need to scroll the page in order to view the bottom one.In order to reproduce this bug, the [ test case | https://github.com/jenkinsci/acceptance-test-harness/blob/e38955e49e1ef6d147d8b09191d59674e46022f3/src/test/java/plugins/AbstractAnalysisTest.java#L120 ] could be adapted so that the analysis-collector plug-in is running this test. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Title: Message Title Daniel Beck commented on JENKINS-27223 Re: Clicking Login when you have 30+ slaves defaults you to the bottom of the web page Manuel Jesús Recena Soto Trivial to reproduce, just set master to 100 executors and click 'login' on the top right. Doesn't need a screenshot or video. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30290) PR build NOT working
Title: Message Title sam flint commented on JENKINS-30290 Re: PR build NOT working This was due to jenkins user not having "admin" permissions on github. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30290) PR build NOT working
Title: Message Title sam flint closed an issue as Fixed Just needed another day Jenkins / JENKINS-30290 PR build NOT working Change By: sam flint Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title Thomas Goeppel commented on JENKINS-30269 Re: Add workflow support for resource locking This would be highly appreciated for controlling nodes that can run one (1) instance of a software that's needed in a build at a time. A different approach would be 'labelled executors', or alternatively 'virtual slaves'. Personally I would prefer such a solution to resource locking (of course, counting software licences is a different use case). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-24208) ignore users in GitHub plugin
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-24208 ignore users in GitHub plugin Change By: Kirill Merkushev Attachment: gitscm.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27223 Re: Clicking Login when you have 30+ slaves defaults you to the bottom of the web page Daniel Beck Ok. I'll take a look. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30290) PR build NOT working
Title: Message Title sam flint resolved as Fixed Jenkins / JENKINS-30290 PR build NOT working Change By: sam flint Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30304) Footer hides trend graph links
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-30304 Footer hides trend graph links Change By: Ulli Hafner In the project view (job page) the links below the last trend graph are not clickable since the footer overlaps these links. It happens only if you have several trend graphs so you need to scroll the page in order to view the bottom one. In order to reproduce this bug, the test case https://github.com/jenkinsci/acceptance-test-harness/blob/e38955e49e1ef6d147d8b09191d59674e46022f3/src/test/java/plugins/AbstractAnalysisTest.java#L120 could be adapted so that the analysis-collector plug-in is running this test. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-disk-usage-simple-plugin] (JENKINS-30311) List JENKINS_HOME and its first level sub directories disk usages
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-30311 List JENKINS_HOME and its first level sub directories disk usages Issue Type: New Feature Assignee: Unassigned Components: cloudbees-disk-usage-simple-plugin Created: 04/Sep/15 6:15 PM Environment: cloudbees disk usage simple plugin 0.3 Priority: Minor Reporter: Arnaud Héritier Sometimes space isn't used only by jobs but by the config history plugin folder, the plugins or fingerprints ... Add Comment
[JIRA] [mailer-plugin] (JENKINS-26740) Failed to set Jenkins Identity header on email. java.lang.NullPointerException
Title: Message Title moodysma moodysma commented on JENKINS-26740 Re: Failed to set Jenkins Identity header on email. java.lang.NullPointerException still having this issue, is there a workaround? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30283) syntax error determining changeset
Title: Message Title Mark Waite resolved as Not A Defect Jenkins / JENKINS-30283 syntax error determining changeset Change By: Mark Waite Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30283) syntax error determining changeset
Title: Message Title Mark Waite reopened an issue Jenkins / JENKINS-30283 syntax error determining changeset Change By: Mark Waite Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30283) syntax error determining changeset
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-30283 syntax error determining changeset Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-disk-usage-simple-plugin] (JENKINS-30310) Provide more details about jobs usages
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-30310 Provide more details about jobs usages Issue Type: New Feature Assignee: Unassigned Components: cloudbees-disk-usage-simple-plugin Created: 04/Sep/15 6:12 PM Environment: cloudbees disk usage simple plugin 0.3 Priority: Minor Reporter: Arnaud Héritier Sometimes the space is used by logs, sometimes by archived artifacts (automatically done by maven jobs) ... It's not easy to know which discard option we should correctly configure Add Comment
[JIRA] [multijob-plugin] (JENKINS-30226) MultiJob getting "stuck" after all child jobs complete
Title: Message Title Robert Schultheis commented on JENKINS-30226 Re: MultiJob getting "stuck" after all child jobs complete got another hit... this time the thread dump looks like yours Camilo Sperberg Executor #4 for master : executing SuperSmoker #3177 "Executor #4 for master : executing SuperSmoker #3177" Id=83611 Group=main RUNNABLE at java.util.TreeMap.put(TreeMap.java:567) at java.util.AbstractMap.putAll(AbstractMap.java:273) at java.util.TreeMap.putAll(TreeMap.java:322) at org.jenkinsci.plugins.envinject.EnvInjectVarList.(EnvInjectVarList.java:26) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.getTarget(EnvInjectPluginAction.java:20) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.buildEnvVars(EnvInjectPluginAction.java:24) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947) at org.jenkinsci.plugins.tokenmacro.impl.EnvironmentVariableMacro.evaluate(EnvironmentVariableMacro.java:23) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:189) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:182) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:154) at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setDisplayName(BuildNameSetter.java:50) at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.access$000(BuildNameSetter.java:26) at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter$1.tearDown(BuildNameSetter.java:42) at hudson.model.Build$BuildExecution.doRun(Build.java:173) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) at hudson.model.Run.execute(Run.java:1744) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Im trying some more versions of jenkins + mutlijob plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cloudbees-disk-usage-simple-plugin] (JENKINS-30309) Allow to launch a cleanup on all jobs
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-30309 Allow to launch a cleanup on all jobs Issue Type: New Feature Assignee: Unassigned Components: cloudbees-disk-usage-simple-plugin Created: 04/Sep/15 6:10 PM Environment: cloudbees disk usage simple plugin 0.3 Priority: Minor Reporter: Arnaud Héritier To launch the discard on all jobs in one operation and not have to click on all jobs if you changed the configuration of all jobs using the slicing configuration plugin for exemple Add Comment
[JIRA] [github-plugin] (JENKINS-24208) ignore users in GitHub plugin
Title: Message Title Christophe Lallement commented on JENKINS-24208 Re: ignore users in GitHub plugin Kirill Merkushev I gonna test it but I think It can not help because in fact there is no polling. Job is trigerred by github itself, git information is just used to checkout/rebase the master branch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-30312) Rundeck plugin not properly passing multi value job optios
Title: Message Title Ryan Shows created an issue Jenkins / JENKINS-30312 Rundeck plugin not properly passing multi value job optios Issue Type: Bug Assignee: Vincent Behar Components: rundeck-plugin Created: 04/Sep/15 7:17 PM Priority: Major Reporter: Ryan Shows When passing job options when I have a multi-value options with a comma delimited list there is an issue. Specifically I am trying to pass a list of nodes for a job to run on which is then used by the rundeck job as the node filter. In all cases the job is only run against the node which comes after the first comma. Here is the sample job options from jenkins. infUsername=none infPassword= env=dev version=$POM_VERSION identifier=:war nodes=dtkcpiu09,dtkpciu18 <-- This is the offending line Add Comment
[JIRA] [jira-plugin] (JENKINS-18316) JiraSite.DescriptorImpl$doValidation does not validate alternativeUrl
Title: Message Title Radek Antoniuk resolved as Fixed This was fixed long time ago here: https://github.com/jenkinsci/jira-plugin/commit/4f55c2757f7780e7ccc584b041df28314bf994e5 Jenkins / JENKINS-18316 JiraSite.DescriptorImpl$doValidation does not validate alternativeUrl Change By: Radek Antoniuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Clark Boylan updated an issue Jenkins / JENKINS-27514 Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Thread dump from Jenkins master upgraded to ssh slaves plugin 1.10 but otherwise the same as the previous thread dump example. Change By: Clark Boylan Attachment: 20150904-jenkins03.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around
Title: Message Title Jesse Glick commented on JENKINS-12875 Re: "No valid crumb was included in the request" errors all around Would like to understand better how a header name being a _javascript_ identifier opens one to attack It is complicated but has to do with how the crumb is offered to legitimate clients. Anyway the fix is well understood and filed, “just” needs to be tested and reviewed by someone qualified in web security. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-30313) Build passes even if Mercurial returns an error
Title: Message Title Brandon Coleman created an issue Jenkins / JENKINS-30313 Build passes even if Mercurial returns an error Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 04/Sep/15 7:55 PM Environment: Windows Server 2008 Priority: Blocker Reporter: Brandon Coleman Jenkins continues to build a job when a mercurial returns an error. Section that should have failed: c:\python27\scripts\hg.bat --config extensions.largefiles= update --clean --rev stable abort: d:\Jenkins\jobs\This is a test project that should break but runs successfully\workspace\This is a test project that should break but runs successfully\.hglf/sites/ama_main/departments/engineering/pdf/Martin_Road_Plan/Flooding_Mitigation_Conceptual_Eval_Final.pdf: The system cannot find the path specified running errorlevel for the same command from the command line returns 255 Full log of a job below: Started by user Coleman, Brandon Building on master in workspace d:\Jenkins\jobs\This is a test project that should break but runs successfully\workspace\This is a test project that should break but runs successfully Acquired master cache lock. [43574B1BAE5B4759D1B76C50474205426641B9D4-web] $ c:\python27\scripts\hg.bat --config extensions.largefiles= pull pulling from D:\Repositories\web searching for changes no
[JIRA] [github-plugin] (JENKINS-27136) Workflow support for GitHub Push Triggers
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27136 Re: Workflow support for GitHub Push Triggers Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/e1d0fe62ae5ca7b4cd93e9603321d88eff71d72b Log: JENKINS-25977 JENKINS-27136 Noting some merges. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25977 Re: Make publishers of analysis-core a SimpleBuildStep Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/e1d0fe62ae5ca7b4cd93e9603321d88eff71d72b Log: JENKINS-25977 JENKINS-27136 Noting some merges. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-13500) Jira plugin post "integrated in" comment on every build
Title: Message Title Radek Antoniuk resolved as Duplicate Closing as duplicate of JENKINS-17156 Jenkins / JENKINS-13500 Jira plugin post "integrated in" comment on every build Change By: Radek Antoniuk Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30300) Unable to specify a branch to build when using parameterized job with multiple branches
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-30300 Unable to specify a branch to build when using parameterized job with multiple branches Change By: Mark Waite Summary: Unable to specify a branch to build when using paramatized parameterized job with multiple branches Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Clark Boylan edited a comment on JENKINS-27514 Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Thread dump from Jenkins master upgraded to ssh slaves plugin 1.10 but otherwise the same as the previous thread dump example. We thought that 1.10 may have fixed the bug but doesn't appear to have done so. Attaching this thread dump in case the information is sufficiently new and different to be helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-30313) Checkout continues even if `hg update` returns an error
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30313 Checkout continues even if `hg update` returns an error Not known whether reproducible from scratch. Code does check exit status of the command. Change By: Jesse Glick Summary: Build passes Checkout continues even if Mercurial `hg update` returns an error Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Jesse Glick commented on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete Piyush Jain your issue sounds more like JENKINS-27419, perhaps. Impossible to be sure without a way to reproduce from scratch. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title
Jesse Glick commented on JENKINS-30252
Re: Provide easy access to git branch name in multibranch workflow scripts
Yes you are missing something. For example, in the stock CD demo (1.10), adding
echo "running from ${env.JOB_NAME.replaceFirst('.+/', '')}"
works (after approving method java.lang.String replaceFirst java.lang.String java.lang.String for the sandbox).
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-30314) Unable to connect using Jabber plugin (bad-request)
Title: Message Title Brian Pugh created an issue Jenkins / JENKINS-30314 Unable to connect using Jabber plugin (bad-request) Issue Type: Bug Assignee: kutzi Components: jabber-plugin Created: 04/Sep/15 9:12 PM Environment: Jenkins ver. 1.627 java.runtime.version 1.7.0_79-b14 instant-messaging 1.35 ircbot 2.26 jabber 1.35 Labels: plugin plugins jabber Priority: Major Reporter: Brian Pugh IRCBot connects, but Jabber bot fails. Same account on another client (Messages.app on OS X) works as expected. Finest-level logging: Sep 04, 2015 1:48:29 PM FINEST hudson.plugins.jabber.im.transport.JabberConnectionDebugger RCV PKT: Sep 04, 2015 1:49:59 PM INFO hudson.plugins.jabber.im.transport.JabberIMConnection createConnection Trying to connect to XMPP on /example.com Sep 04, 2015 1:49:59 PM FINE hudson.plugins.jabber.im.transport.JabberConnectionDebugger SENT: Sep 04, 2015
[JIRA] [jira-plugin] (JENKINS-11018) JIRA comment will mix other JIRA ID in JIRA Plugin
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce This code was changed long time ago, this issue should not happen. If it does, a new bug should be reported. Jenkins / JENKINS-11018 JIRA comment will mix other JIRA ID in JIRA Plugin Change By: Radek Antoniuk Status: Open Resolved Assignee: Kohsuke Kawaguchi Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [naginator-plugin] (JENKINS-17626) Retry count resets when job with other parameters is successful
Title: Message Title ikedam started work on JENKINS-17626 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-21482) Configure functionality for a job stops working when JIRa issue updater configured in previous edit
Title: Message Title Radek Antoniuk commented on JENKINS-21482 Re: Configure functionality for a job stops working when JIRa issue updater configured in previous edit Can you check with the current plugin version? If the issue is still happening, please add Jenkins, JIRA and plugin version info. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-23257) Non well-formed response from JIRA error is hard to diagnose
Title: Message Title Radek Antoniuk commented on JENKINS-23257 Re: Non well-formed response from JIRA error is hard to diagnose The current plugin version is using REST API. Do you think we can close this bug? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-12976) TypeError: checkUrl uses Form.findMatchingInput which is not available
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Closing old issues - if this still happens with current Jenkins LTS version and current plugin version, please reopen. Thanks! Jenkins / JENKINS-12976 TypeError: checkUrl uses Form.findMatchingInput which is not available Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-29212) Jobfilter does not work on cloudbees subfolders
Title: Message Title Fawzy Manaa commented on JENKINS-29212 Re: Jobfilter does not work on cloudbees subfolders Bernd, did you ever find a way around this? I am experiencing the same issue... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-30315) Build Token Root returns 404 error - Possibly Proxy/Auth issue?
Title: Message Title
M Chon updated an issue
Jenkins / JENKINS-30315
Build Token Root returns 404 error - Possibly Proxy/Auth issue?
Change By:
M Chon
Our Jenkins servers require {{ --auth-no-challenge }} and {{--no-proxy flags}} to be passed to wget when triggering builds.I installed the Build Root Token Plugin today and attempted to use the buildByToken URI. It failed. It is not clear why.The documentation indicates it should "just work".The only thing different about my environment are the flags which need to be passed to wget.===Regular URI, is successful:==={quote}$ wget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET_WIPE=false[1] 22861mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREETResolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.HTTP request sent, awaiting response... 201 CreatedLength: 0Saving to: ‘buildWithParameters?token=SECONDSTREET.3’[ <=> ] 0 --.-K/s in 0s2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0][1]+ Donewget -v --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}===buildByToken URI, fails:==={ quote} { { $ wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET_WIPE=false[1] 22948mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREETResolving ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)... 43.148.4.200Connecting to ussdisbldsl01.am.sony.com (ussdisbldsl01.am.sony.com)|43.148.4.200|:443... connected.HTTP request sent, awaiting response... 404 Not Found2015-09-04 15:03:34 ERROR 404: Not Found.[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://ussdisbldsl01.am.sony.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}} {quote}
Add Comment
[JIRA] [build-token-root-plugin] (JENKINS-30315) Build Token Root returns 404 error - Possibly Proxy/Auth issue?
Title: Message Title
M Chon updated an issue
Jenkins / JENKINS-30315
Build Token Root returns 404 error - Possibly Proxy/Auth issue?
Change By:
M Chon
Our Jenkins servers require *{{ --auth-no-challenge }}* and *{{ --no-proxy }}* flags to be passed to wget when triggering builds.I installed the Build Root Token Plugin today and attempted to use the buildByToken URI. It failed. It is not clear why.The documentation indicates it should "just work".The only thing different about my environment are the flags which need to be passed to wget.===Regular URI, is successful:==={quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET_WIPE=false[1] 22861mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREETResolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.HTTP request sent, awaiting response... 201 CreatedLength: 0Saving to: ‘buildWithParameters?token=SECONDSTREET.3’[ <=> ] 0 --.-K/s in 0s2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0][1]+ Donewget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}===buildByToken URI, fails:==={quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET_WIPE=false[1] 22948mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREETResolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.HTTP request sent, awaiting response... 404 Not Found2015-09-04 15:03:34 ERROR 404: Not Found.[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}
Add Comment
[JIRA] [build-token-root-plugin] (JENKINS-30315) Build Token Root returns 404 error - Possibly Proxy/Auth issue?
Title: Message Title
M Chon updated an issue
Jenkins / JENKINS-30315
Build Token Root returns 404 error - Possibly Proxy/Auth issue?
Change By:
M Chon
Our Jenkins servers require {{ --auth-no-challenge }} and {{ --no-proxy flags }} to be passed to wget when triggering builds.I installed the Build Root Token Plugin today and attempted to use the buildByToken URI. It failed. It is not clear why.The documentation indicates it should "just work".The only thing different about my environment are the flags which need to be passed to wget.===Regular URI, is successful:==={quote}$ wget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET_WIPE=false[1] 22861mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:02:30-- https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREETResolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.HTTP request sent, awaiting response... 201 CreatedLength: 0Saving to: ‘buildWithParameters?token=SECONDSTREET.3’[ <=> ] 0 --.-K/s in 0s2015-09-04 15:02:30 (0.00 B/s) - ‘buildWithParameters?token=SECONDSTREET.3’ saved [0/0][1]+ Donewget -v --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildWithParameters?token=SECONDSTREET{quote}===buildByToken URI, fails:==={quote}{{$ wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET_WIPE=false[1] 22948mchon@USLVEKJCI02:~/cid-dev/Cid$ --2015-09-04 15:03:33-- https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREETResolving jenkins.am.blah.com (jenkins.am.blah.com)... 43.148.4.200Connecting to jenkins.am.blah.com (jenkins.am.blah.com)|43.148.4.200|:443... connected.HTTP request sent, awaiting response... 404 Not Found2015-09-04 15:03:34 ERROR 404: Not Found.[1]+ Exit 8 wget --auth-no-challenge --no-proxy https://jenkins.am.blah.com/job/mchon_admin/buildByToken/buildWithParameters?token=SECONDSTREET}}{quote}
Add Comment
[JIRA] [build-token-root-plugin] (JENKINS-30315) Build Token Root returns 404 error - Possibly Proxy/Auth issue?
Title: Message Title M Chon commented on JENKINS-30315 Re: Build Token Root returns 404 error - Possibly Proxy/Auth issue? BTW, in checking the Jenkins log, neither event (succesfully triggered, or unsuccessfully triggered) appears in the log upon launch. Only the successful build appears in the log upon completion: INFO: mchon_admin #25 main build action completed: SUCCESS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
