[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Shah Chowdhury reopened an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: Shah Chowdhury Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.3081.1565821081022%40Atlassian.JIRA.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Shah Chowdhury commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. We ended up reverting back to the old (2.25) level. Branch Names in the Raw Logs is critical for us. We have various tools/log-formatters that parse through raw logs. Please put this back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.3066.1565821020395%40Atlassian.JIRA.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title Shah Chowdhury commented on JENKINS-55137 Re: No branch name in logs from parallel branches anymore? We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196204.1544601655000.7704.1562806440251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54763) Branch name disappear after plugin upgrade (>= 2.26)
Title: Message Title Shah Chowdhury commented on JENKINS-54763 Re: Branch name disappear after plugin upgrade (>= 2.26) We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195569.1542867431000.7702.1562806380163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Shah Chowdhury commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. https://issues.jenkins-ci.org/browse/JENKINS-54304?focusedCommentId=357033=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-357033 "Regarding branch names in the raw logs, I think it would be possible to add them back" We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.4743.1562602800434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Shah Chowdhury commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. https://issues.jenkins-ci.org/browse/JENKINS-54304?focusedCommentId=357033=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-357033 We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.4715.1562602620786%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Shah Chowdhury updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: Shah Chowdhury Comment: https://issues.jenkins-ci.org/browse/JENKINS-54304?focusedCommentId=357033=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-357033 We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194952.1540802341000.4729.1562602620994%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58283) Jenkins UI erases envinject config data with promoted-builds 3.3
Title: Message Title Shah Chowdhury created an issue Jenkins / JENKINS-58283 Jenkins UI erases envinject config data with promoted-builds 3.3 Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin, promoted-builds-plugin Created: 2019-07-01 12:17 Environment: Jenkins: 2.164.3 promoted-builds: 3.3 envinject: 1.91.4 Priority: Major Reporter: Shah Chowdhury After upgrading the promoted-builds plugin to 3.3, when you save a Jenkins project configuration containing envinject plugin configuration data through the UI, it erases/loses all the configuration for the envinject plugin. Downgrading promoted-builds to 2.28.1 resolves the issue. Add Comment
[JIRA] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, {color:#14892c}* Works works fine in Jenkins 1.651.1*{color}
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title Shah Chowdhury updated an issue Jenkins / JENKINS-35113 Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin Change By: Shah Chowdhury *Works in Jenkins 1.651.1*Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file ' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, *Works fin fine in Jenkins 1.651.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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title Shah Chowdhury updated an issue Jenkins / JENKINS-35113 Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin Change By: Shah Chowdhury Summary: Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file ' in 'Parameterized Trigger' 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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437} *Works in Jenkins 1.651.1* {color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, * {color:#d04437} Works fine in Jenkins 1.651.1 {color} *
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, *{color:# d04437 14892c }Works fine in Jenkins 1.651.1{color}*
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, {color: red}{color: # d04437 14892c }*Works fine in Jenkins 1.651.1*{color} {color}
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, {color:red} {color:#d04437} *Works fine in Jenkins 1.651.1*{color} {color}
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, {color: #14892c red }*Works fine in Jenkins 1.651.1*{color}
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, * {color:#14892c} * Works fine in Jenkins 1.651.1 * {color} *
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin
Title: Message Title Shah Chowdhury updated an issue Jenkins / JENKINS-35113 Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin Change By: Shah Chowdhury Summary: Upgrade to 1.651.2 or 2.6.x broke breaks 'Parameters from properties' in 'Parameterized Trigger' 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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x broke 'Parameters from properties' in 'Parameterized Trigger' plugin
Title: Message Title Shah Chowdhury created an issue Jenkins / JENKINS-35113 Upgrade to 1.651.2 or 2.6.x broke 'Parameters from properties' in 'Parameterized Trigger' plugin Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/May/25 2:28 AM Environment: Jenkins 1.651.2 or 2.6 Parameterized Trigger Plugin 2.30 Priority: Critical Reporter: Shah Chowdhury Works in Jenkins 1.651.1 Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin. Steps to recreate: Create two Jenkins projects: proj1 and proj2 In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file Build proj1 which should trigger proj2
[JIRA] [multijob-plugin] (JENKINS-32483) java.io.IOException: Failed to write url on api/xml?depth=1
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-32483
java.io.IOException: Failed to write url on api/xml?depth=1
Change By:
Shah Chowdhury
API URL /job//api/xml?depth=1 causes exception. Note that 'depth=0' works fine. {{ java.io.IOException: Failed to write url at org.kohsuke.stapler.export.Property.writeTo(Property.java:122) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeTo(Model.java:164) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doXml(Api.java:100) at sun.reflect.GeneratedMethodAccessor1170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:619) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$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.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at
[JIRA] [multijob-plugin] (JENKINS-32483) java.io.IOException: Failed to write url on api/xml?depth=1
Title: Message Title Shah Chowdhury started work on JENKINS-32483 Change By: Shah Chowdhury 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] [multijob-plugin] (JENKINS-32483) java.io.IOException: Failed to write url on api/xml?depth=1
Title: Message Title Shah Chowdhury stopped work on JENKINS-32483 Change By: Shah Chowdhury Status: In Progress Open 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-32483) java.io.IOException: Failed to write url on api/xml?depth=1
Title: Message Title
Shah Chowdhury created an issue
Jenkins / JENKINS-32483
java.io.IOException: Failed to write url on api/xml?depth=1
Issue Type:
Bug
Assignee:
Unassigned
Components:
multijob-plugin
Created:
16/Jan/16 10:41 AM
Environment:
Jenkins ver. 1.640 MultiJob Plugin 1.20
Priority:
Critical
Reporter:
Shah Chowdhury
API URL /job//api/xml?depth=1 causes exception. Note that 'depth=0' works fine.
{{ java.io.IOException: Failed to write url at org.kohsuke.stapler.export.Property.writeTo(Property.java:122) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at
