[JIRA] [xunit] (JENKINS-21247) [xunit] fails to parse junit test report with a single ignored testcase
Greg Temchenko commented on JENKINS-21247 [xunit] fails to parse junit test report with a single ignored testcase I guess it comes from gradle. It's been recently fixed in https://github.com/gradle/gradle/pull/247 but not release yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
Greg Temchenko commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? When do you plan the next release? This is the highly anticipated feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-20647) Uncaught TypeError: Cannot read property 'click' of undefined (when trying to add mercurial repo)
Greg Temchenko updated JENKINS-20647 Uncaught TypeError: Cannot read property click of undefined (when trying to add mercurial repo) Change By: Greg Temchenko (19/Nov/13 3:32 AM) Environment: Jenkinsv1.534,GoogleChromeandSafari. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-20647) Uncaught TypeError: Cannot read property 'click' of undefined (when trying to add mercurial repo)
Greg Temchenko created JENKINS-20647 Uncaught TypeError: Cannot read property click of undefined (when trying to add mercurial repo) Issue Type: Bug Assignee: Kevin Bell Components: multiple-scms Created: 19/Nov/13 3:31 AM Description: I can't add Mercurial repository using Multiple SCMs. When I click "Mercurial" in the drop-down list "Add SCM", nothing happens and I can see in Chrome console the error message: Uncaught TypeError: Cannot read property 'click' of undefined (element-min.js:7) Adding Subversion and CVS repos works well, the problem only with mercurial. Project: Jenkins Priority: Major Reporter: Greg Temchenko This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-17806) Retry logic locks in case Jenkins is going to shutdown
Greg Temchenko created JENKINS-17806 Retry logic locks in case Jenkins is going to shutdown Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 30/Apr/13 6:15 PM Description: If Jenkins is going to shutdown and don't start new tasks, and the build flow job restarts a task (using retry() statement) and waits when it's done, then we have Jenkins locked when it can't shutdown and can't trigger new jobs. Project: Jenkins Priority: Minor Reporter: Greg Temchenko This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14595) I should be able to source a flow definition from SCM
Greg Temchenko commented on JENKINS-14595 I should be able to source a flow definition from SCM As a workaround, you can use Job Config History Plugin http://wiki.hudson-ci.org/display/HUDSON/JobConfigHistory+Plugin to track changes. 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
[JIRA] (JENKINS-13883) Support option to omit cleaning
Greg Temchenko created JENKINS-13883:
Summary: Support option to omit cleaning
Key: JENKINS-13883
URL: https://issues.jenkins-ci.org/browse/JENKINS-13883
Project: Jenkins
Issue Type: Improvement
Components: mercurial
Reporter: Greg Temchenko
Assignee: Kohsuke Kawaguchi
Currently there's an option Clean Build that does some extra cleaning
{code:java}
// file: ./src/main/java/hudson/plugins/mercurial/MercurialSCM.java
if(clean) {
if (hg.cleanAll().pwd(repository).join() != 0) {
listener.error(Failed to clean unversioned files);
throw new AbortException(Failed to clean unversioned files);
}
}
{code}
But if this option isn't checked the plugin still clean all local modifications
cause it calls hg update with --clean option.
{code}
// file: ./src/main/java/hudson/plugins/mercurial/MercurialSCM.java
updateExitCode = hg.run(update, --clean, --rev,
getBranch(env)).pwd(repository).join();
{code}
It would be useful to have an option not cleaning local modifications. If it's
possible to do so when Clean Build unchecked it looks pretty simple to
implement. But I'm not sure it's a proper way to do that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13377) Duration in history is not correct
Greg Temchenko created JENKINS-13377: Summary: Duration in history is not correct Key: JENKINS-13377 URL: https://issues.jenkins-ci.org/browse/JENKINS-13377 Project: Jenkins Issue Type: Bug Components: junit Reporter: Greg Temchenko Duration is wrong in history in case described in JENKINS-12457 when test suite splitted into 2 files. If we have 2 cases with the same names we have to use an object only for one of them but merge the duration of them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results
[ https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161319#comment-161319 ] Greg Temchenko commented on JENKINS-13214: -- I would describe it as incapability between [LabeledTestGroupsPublisher Plugin|http://wiki.hudson-ci.org/display/HUDSON/LabeledTestGroupsPublisher+Plugin] and the new version of Jenkins. Tests with the same name are no longer reported in the test results --- Key: JENKINS-13214 URL: https://issues.jenkins-ci.org/browse/JENKINS-13214 Project: Jenkins Issue Type: Bug Components: maven2 Affects Versions: current Reporter: ajbanck Assignee: kutzi Attachments: xml_result.zip After updating from 1.425 to 1.456 test results will only show one test for tests having the same name. Test set having tests executed with parameters: ... ..Executing TestMyTest#testDefault(true) ..Executing TestMyTest#testDefault(false) .Finished test set [Unit Tests] on Fri Mar 23 12:26:08 CET 2012. Executed [132] tests. Resulting test results: xml ... testcase time=0.047 classname=TestMyTest name=testDefault/ testcase time=0.043 classname=TestMyTest name=testDefault/ /testsuite In version 1.425 the 132 test results where correctly displayed. In version 1.456 the test results page is only having one entry for these tests, total amount of tests reported is no longer valid and is the count per test method and not the count of tests actually executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
