[JIRA] [tasks-plugin] (JENKINS-22744) cp1251 encoding issue when viewing Details tab
Martin Ende commented on JENKINS-22744 cp1251 encoding issue when viewing Details tab I published a task scanner acceptance test which reproduces the exact behaviour for a FreeStyle Job with your java file in PR#58: https://github.com/uhafner/acceptance-test-harness/pull/58 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tasks-plugin] (JENKINS-22744) cp1251 encoding issue when viewing Details tab
Martin Ende edited a comment on JENKINS-22744 cp1251 encoding issue when viewing Details tab I would like to support the investigation of that issue by creating a test case in the scope of the acceptance test harness project which helps to reproduce the issue. Unfortunately, I had some problems with the Java file attached to this issue. When I download it with Firefox running under Ubuntu, it seems to be automatically saved as ISO-8859-1 and I cannot convert it into windows-1251. I'll try to download it under Windows tomorrow. I hope that this will preserve the original encoding as the cp1251 is a windows proprietary encoding. Edit: Download under Windows preserves the original file encoding. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tasks-plugin] (JENKINS-22744) cp1251 encoding issue when viewing Details tab
Martin Ende commented on JENKINS-22744 cp1251 encoding issue when viewing Details tab I would like to support the investigation of that issue by creating a test case in the scope of the acceptance test harness project which helps to reproduce the issue. Unfortunately, I had some problems with the Java file attached to this issue. When I download it with Firefox running under Ubuntu, it seems to be automatically saved as ISO-8859-1 and I cannot convert it into windows-1251. I'll try to download it under Windows tomorrow. I hope that this will preserve the original encoding as the cp1251 is a windows proprietary encoding. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter] (JENKINS-23129) Node Parameter option run next build only if build succeeds does not consider the publisher's result
Martin Ende created JENKINS-23129 Node Parameter option run next build only if build succeeds does not consider the publishers result Issue Type: Bug Affects Versions: current Assignee: Dominik Bartholdi Components: nodelabelparameter Created: 21/May/14 2:23 PM Description: If you configure a Job with a Node Parameter and the following configuration run next build only if build succeeds node eligibility set to "All Nodes" and you select multiple nodes to build the job, the next build will always be triggered by the result of the main build action although a post build step (e.g. JUnit Test publisher) will mark the build as failed or unstable. I was expecting that the overall result will be considered before running the next build. I added three test cases to the NodeLabelParameterTest class of the acceptance test harness project to underline this One causes the main build to fail. In that case everything works as expected, subsequent builds are not started after the first build fails The other two test cases use publishers to change the build result. In both cases the job will be built on all nodes. Environment: Jenkins 1.563 Project: Jenkins Priority: Major Reporter: Martin Ende This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter] (JENKINS-23014) Inconsistent parameter display for pending builds due to offline nodes when using the Node Parameter
Martin Ende created JENKINS-23014 Inconsistent parameter display for pending builds due to offline nodes when using the Node Parameter Issue Type: Bug Affects Versions: current Assignee: Dominik Bartholdi Components: nodelabelparameter Created: 13/May/14 10:32 PM Description: If you create a job adding a Node parameter (e.g. slavename) with option disallow multi node selection and node eligibility set to All Nodes. If you then select an offline node (e.g. slave4) for the build you'll get a pending build entry in the Build History area on the left on the job's page. Then within this entry the Node Parameter is specified with NodeParameterValue: slavename=slave4 If change the job's parameter settings to allow multi node selection and you select two nodes, e.g. one online (e.g. slave 3), one offline (e.g. slave4), you'll also get a pending build entry. But this time the parameter is inconsistently mentioned as LabelParameterValue: slavename=slave4 My expectation was that in both cases the parameter is given as NodeParameterValue. This issue has been observed during test development for the acceptance-test-harness project. Environment: Jenkins 1.559 Project: Jenkins Priority: Trivial Reporter: Martin Ende This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
