[JIRA] [core] (JENKINS-18259) Unable to delete slave.log in plugin tests
ikedam commented on JENKINS-18259 Unable to delete slave.log in plugin tests This seems caused in following ways: HudsonTestCase org.jvnet.hudson.test.HudsonTestCase$ComputerListenerImpl is not registered to Jenkins. This is for changes to TestExtensionLoader with Jenkins 1.482, 5dd905f2a2 and 4557a436bf. JenkinsRule Just not deleted temporary files with Jenkins < 1.482. It would fail at the beginning. org.jvnet.hudson.test.JenkinsRule.ComputerListenerImpl exists, but does not work at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18262) HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
ikedam created JENKINS-18262 HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Jun/13 8:42 AM Description: Original design: HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl register channels of launched slaves in order to close at the tearDown phase. They are registered to Jenkins with @TestExtension Current status: They does not work. @TestExtension can be used for classes enclosed by test case classes. JenkinsRule.ComputerListenerImpl does not work at all. HudsonTestCase.ComputerListenerImpl worked in Jenkins < 1.482 for HudsonTestCase is a super class of enclosing classes. But in Jenkins 1.482, @TestExtension works only when the encolosing class is exactly the test case class. This change is 5dd905f2a2 and 4557a436bf. Environment: Jenkins >= 1.482 Project: Jenkins Priority: Minor Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18262) HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
ikedam
updated JENKINS-18262
HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
Change By:
ikedam
(08/Jun/13 8:44 AM)
Description:
Original design:* {{HudsonTestCase.ComputerListenerImpl}} and {{JenkinsRule.ComputerListenerImpl}} register channels of launched slaves in order to close at the tearDown phase.* They are registered to Jenkins with {{@TestExtension}}Current status:* They does not work.* {{@TestExtension}} can be used for classes enclosed by test case classes.* JenkinsRule.ComputerListenerImpl does not work at all.* HudsonTestCase.ComputerListenerImpl worked in Jenkins < 1.482 for HudsonTestCase is a super class of enclosing classes. But in Jenkins 1.482, {{@TestExtension}} works only when the encolosing class is exactly the test case class.** This change is [5dd905f2a2|https://github.com/jenkinsci/jenkins/commit/5dd905f2a2c5316f170034c9026f6ff0eb0e2a2c] and [4557a436bf|https://github.com/jenkinsci/jenkins/commit/4557a436bf71db6cb18d0838f655a960b1adbd25].
Problems caused by this:* Log files of slaves are left open, and fail to delete temporary directories in Windows: JENKINS-18259
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] [core] (JENKINS-18262) HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
ikedam commented on JENKINS-18262 HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work Supposed solutions: A. Register ComputerListenerImpl to Jenkins not using annotations(@TestExtension). B. Create a new annotation alternate to @TestExtension. C. Register channels not using ComputerListener. 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] [core] (JENKINS-18262) HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
ikedam edited a comment on JENKINS-18262 HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work Supposed solutions: A. Register ComputerListenerImpl to Jenkins not using annotations(@TestExtension). B. Create a new annotation alternate to @TestExtension. C. Allow @TestExtension to accept inner classes in HudsonTestCase and JenkinsRule. D. Register channels not using ComputerListener. 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] [core] (JENKINS-18262) HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work
ikedam commented on JENKINS-18262 HudsonTestCase.ComputerListenerImpl and JenkinsRule.ComputerListenerImpl does not work > A. Register ComputerListenerImpl to Jenkins not using annotations(@TestExtension). There seems no interface to register extensions at runtime. > B. Create a new annotation alternate to @TestExtension. > C. Allow @TestExtension to accept inner classes in HudsonTestCase and JenkinsRule. This seems not so good idea for this is used only for ComputerListenerImpl. HudsonTestCase and JenkinsRule does not register any other extensions. A left way: D. Register channels not using ComputerListener. 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] [core] (JENKINS-15120) Minimize round trips for slave class loading
SCM/JIRA link daemon commented on JENKINS-15120 Minimize round trips for slave class loading Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/ClassicPluginStrategy.java maven-plugin/src/main/java/hudson/maven/Maven3Builder.java pom.xml http://jenkins-ci.org/commit/jenkins/f7330d7a158eff6705706b1f812993a9b918c351 Log: [FIXED JENKINS-15120] integrated the newer release of remoting jar caching won't work with class file directory, so plugin WEB-INF/classes are now exploded as WEB-INF/lib/classes.jar (This should also solve the problem of slow plugin extraction in the presene of Anti-virus software on Windows.) because the structure of the exploded jar file has changed, I changed the up-to-date check timestamp file name to force re-extraction in existing installations. Compare: https://github.com/jenkinsci/jenkins/compare/b1f5d28f90ca...f7330d7a158e 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] [core] (JENKINS-15120) Minimize round trips for slave class loading
SCM/JIRA link daemon resolved JENKINS-15120 as Fixed Minimize round trips for slave class loading Change By: SCM/JIRA link daemon (08/Jun/13 9:24 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15120) Minimize round trips for slave class loading
dogfood commented on JENKINS-15120 Minimize round trips for slave class loading Integrated in jenkins_main_trunk #2582 [FIXED JENKINS-15120] (Revision f7330d7a158eff6705706b1f812993a9b918c351) Result = UNSTABLE kohsuke : f7330d7a158eff6705706b1f812993a9b918c351 Files : maven-plugin/src/main/java/hudson/maven/Maven3Builder.java pom.xml core/src/main/java/hudson/ClassicPluginStrategy.java changelog.html 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] [subversion] (JENKINS-4613) Log message when svn URL is wrong could be better
kutzi commented on JENKINS-4613 Log message when svn URL is wrong could be better @cander: is this still a problem? If so, would you still be willing to submit a pull request? 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] [core] (JENKINS-3093) Cancelling a build loses the change history
kutzi resolved JENKINS-3093 as Duplicate Cancelling a build loses the change history Sounds like a duplicate of JENKINS-8440. Please reopen, if it's not fixed in version 1.48 of the subversion plugin Change By: kutzi (08/Jun/13 10:59 AM) Status: Open Resolved Resolution: Duplicate 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] [xunit] (JENKINS-18263) py.test generated test reports are no longer being parsed as valid
Drew Reed created JENKINS-18263 py.test generated test reports are no longer being parsed as valid Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 08/Jun/13 4:38 PM Description: Junit xml files produced by py.test (http://pytest.org) are no longer being parsed. Console output shows [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 2 test report file(s) were found with the pattern 'test_artifacts/**/*.xml' relative to '/home/jenkins/tests/workspace/VCHIq_USB_Driver_Test' for the testing framework 'JUnit'. [xUnit] [ERROR] - The result file '/home/jenkins/tests/workspace/VCHIq_USB_Driver_Test/test_artifacts/sanity_vchiq.xml' for the metric 'JUnit' is not valid. The result file has been skipped. [xUnit] [INFO] - Fail BUILD because 'set build failed if errors' option is activated. [xUnit] [INFO] - There are errors when processing test results. [xUnit] [INFO] - Skipping tests recording. [xUnit] [INFO] - Stop build. and the xml file looks as follows "" errors="0" failures="0" skips="0" tests="1" time="33.353">" name="test_loadkernel" time="31.3439750671"/> I believe it the skips attribute that is no longer being considered valid. Project: Jenkins Priority: Major Reporter: Drew Reed 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] [parameterized-trigger] (JENKINS-18264) Support multiple build buttons with different attributes
Avishay Halpren created JENKINS-18264 Support multiple build buttons with different attributes Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger, ui-changes Created: 08/Jun/13 9:14 PM Description: A parameterized build should contain the ability to press a different button to create a build with different params. for example: a deploy job with parameters from (source control branch) to (server name) chould contain 3 butttons named: Test,QA,Prod each button contains the from and to correct values without the need to feel it up Project: Jenkins Priority: Major Reporter: Avishay Halpren 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] [parameterized-trigger] (JENKINS-18264) Support multiple build buttons with different attributes
Avishay Halpren updated JENKINS-18264 Support multiple build buttons with different attributes Change By: Avishay Halpren (08/Jun/13 9:15 PM) Priority: Major Minor 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] [rake] (JENKINS-7530) Rake plugin fails when Job configured to use (Default) Rake installation.
john smith commented on JENKINS-7530 Rake plugin fails when Job configured to use (Default) Rake installation. I am also using Rake plugin 1.7.7 and see this issue. My machine is also a windows slave. 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] [job-dsl-plugin] (JENKINS-18075) Add method to schedule a job after it has been created/modified
Justin Ryan started work on JENKINS-18075 Add method to schedule a job after it has been created/modified Change By: Justin Ryan (09/Jun/13 1:14 AM) Status: Open In Progress 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] [job-dsl-plugin] (JENKINS-16363) Allow selection of job type
Justin Ryan resolved JENKINS-16363 as Fixed Allow selection of job type It was added as part of maven support. Multi-module support further supported it. Change By: Justin Ryan (09/Jun/13 1:44 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-8962) Cannot change parameter value for promotion re-execution
Clecio Varjao commented on JENKINS-8962 Cannot change parameter value for promotion re-execution I've submitted a pull request: https://github.com/jenkinsci/promoted-builds-plugin/pull/27 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] [mstest] (JENKINS-18265) MSTest plugin doesn't report test failures
dlindberg created JENKINS-18265 MSTest plugin doesn't report test failures Issue Type: Bug Affects Versions: current Assignee: acmarques Attachments: test.results (1).trx Components: mstest Created: 09/Jun/13 2:14 AM Description: MSTest failures are not being reported. The output from the build looks like this: [ncover] Starting execution... [ncover] Process 'QTAgent' [PID 2424] has begun profiling. [ncover] [ncover] Results Top Level Tests [ncover] --- --- [ncover] Error LindbergCorp.StringFileTranslator.Test.TranslatorTests.TestConversion [ncover] Error LindbergCorp.StringFileTranslator.Test.TranslatorTests.TestConversionFrench [ncover] Error LindbergCorp.StringFileTranslator.Test.TranslatorTests.TestFileNotFound [ncover] Process 'QTAgent' [PID 2424] has finished profiling. [ncover] 0/3 test(s) Passed, 3 Error [ncover] [ncover] Summary [ncover] --- [ncover] Test Run Error. [ncover] Error 3 [ncover] [ncover] Total 3 [ncover] Results file: E:\Jenkins\workspace\LindbergCorp.StringFileTranslator\TestResults\Release\test.results.trx But the plugin reports all tests are successful Environment: Windows 2012 Project: Jenkins Labels: plugin Priority: Major Reporter: dlindberg 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] [mstest] (JENKINS-18265) MSTest plugin doesn't report test failures
dlindberg updated JENKINS-18265 MSTest plugin doesn't report test failures This is what Jenkins shows. Change By: dlindberg (09/Jun/13 2:20 AM) Attachment: Screen Shot 2013-06-08 at 22.19.20.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
