[JIRA] [matrix-project-plugin] (JENKINS-30632) Multijob running specific matrix configuration results in java.null.reference
Title: Message Title Serge Zukov created an issue Jenkins / JENKINS-30632 Multijob running specific matrix configuration results in java.null.reference Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin, multijob-plugin Created: 24/Sep/15 4:45 PM Environment: Windows 2008R2 Jenkins 1.630 Matrix project plugin 1.6 Multijob plugin 1.18 Parameterized trigger plugin 2.29 Labels: plugin Priority: Minor Reporter: Serge Zukov Suppose you have matrix project called "configuredmatrix" with single dimension called "config" having two possible values "A" and "B". Create a new multijob instance called "multijobA" add new MultiJob phase In the job fields start typing "configurematrix"; Note that UI will offer three options: "configurematrix", "configurematrix/config=A" and "configurematrix/config=B" Choose "configurematrix/config=A" Save your multijob project Run your multijob project and check the console output for following: Starting build job configurematrix/config=A.
[JIRA] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov commented on JENKINS-29019 Re: FitNesse 1.13 does not render properly FitNesse history Confirm to be resolved in 1.6. 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] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov edited a comment on JENKINS-29019 Re: FitNesse 1.13 does not render properly FitNesse history Confirmtoberesolvedin1.6. Thisissuecouldbeclosednow. 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] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov closed an issue as Fixed Thank you for fixing this. Jenkins / JENKINS-29019 FitNesse 1.13 does not render properly FitNesse history Change By: Serge Zukov Status: InProgress 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] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov edited a comment on JENKINS-29019 Re: FitNesse 1.13 does not render properly FitNesse history Confirmtobefixed Wehavethesingletableback in1.5 howeverthecolumnheadersdonotshowbuildnumbersyet.HTMLsnippetoftableheaderlookslikethis:thwidth=25pxahref=""> 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] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov commented on JENKINS-29019 Re: FitNesse 1.13 does not render properly FitNesse history Confirm to be fixed in 1.5 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] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov created an issue Jenkins / JENKINS-29019 FitNesse 1.13 does not render properly FitNesse history Issue Type: Bug Assignee: Antoine Aumjaud Components: fitnesse-plugin Created: 22/Jun/15 8:03 PM Environment: Jenkins 1.617, FitNesse plugin 1.13 Priority: Major Reporter: Serge Zukov After upgrade to FitNesse plugin 1.13 (from 1.12) FitNesse History is no longer rendered as a single table. FitNesse history shows one table per each FitNesse test name without actual test value. Add Comment
[JIRA] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Title: Message Title Serge Zukov commented on JENKINS-27940 Re: Consider using jUnit output from FitNesse The one and only benefit INHO is to plug into existing JENKINS test results infrastructure. FitNesse results are a bit of sidestep from rest of test results in Jenkins (yes, for the good reason) however it limits things user can achieve with it. For example you cannot accumulate FitNesse test results from several jobs into one (this feature is for junit tests only AFAIK). P.S. FitNesse junit output could be extended to embed things JENKINS needs (I implemented an absolute bare minimum). 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] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Title: Message Title Serge Zukov commented on JENKINS-27938 Re: Unable to expand collapsed SLIM tables You won't need my page to reproduce it: FitNesse.SuiteAcceptanceTests.SuiteSlimTests.ChainWithInstanceTest In captured test results do something with will not be expandable. Yes, you are right - the issue affects collapsed scenarios. Does not affect collapsed page sections. 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] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Title: Message Title Serge Zukov updated an issue Jenkins / JENKINS-27940 Consider using jUnit output from FitNesse Change By: Serge Zukov Issue Type: NewFeature Improvement 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] [fitnesse-plugin] (JENKINS-12380) Display results whilst build is in progress
Title: Message Title Serge Zukov edited a comment on JENKINS-12380 Re: Display results whilst build is in progress Justto thrown throw anidea:Intheorythiscouldbeachievedbyusingtextformatwhenqueryingtestexecution.TheproblemisthatFitNessedoesnotsupportRESTcallsforretrievinglatesttestresultthereforeshowingcurrentnicereportwillnotbepossible. 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] [fitnesse-plugin] (JENKINS-27936) When few FitNesse test results being published in a single job they renamed into Summary
Title: Message Title Serge Zukov updated an issue Jenkins / JENKINS-27936 When few FitNesse test results being published in a single job they renamed into Summary Change By: Serge Zukov Priority: Minor Major 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] [fitnesse-plugin] (JENKINS-27936) When few FitNesse test results being published in a single job they renamed into Summary
Title: Message Title Serge Zukov commented on JENKINS-27936 Re: When few FitNesse test results being published in a single job they renamed into Summary Apparently publishing multiple test results under a single build using plugin 1.12 is broken. If you publish two XML files then you will have two SUMMARY entries in FitNesse result with exact same content under each of the summaries. I believe the latest published XML takes precedence. I increased priority from minor to major. 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] [fitnesse-plugin] (JENKINS-12380) Display results whilst build is in progress
Title: Message Title Serge Zukov commented on JENKINS-12380 Re: Display results whilst build is in progress Just to thrown an idea: In theory this could be achieved by using text format when querying test execution. The problem is that FitNesse does not support REST calls for retrieving latest test result therefore showing current nice report will not be possible. 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Serge Zukov commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 to Daniel: yes, 1.611 is also affected. Sorry, I've missed the version number in the title. In my case project uses both copy and performance plugins. I'm confirming that rolling back to 1.609 resolves the issue. 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] [performance-plugin] (JENKINS-28110) NoStaplerConstructorException for Jenkins 1.610
Serge Zukov commented on JENKINS-28110 NoStaplerConstructorException for Jenkins 1.610 Yes, it did work on 1.609. Maybe relevant: 1.610 broke copy artifact plugin. 1.611 fixed the copy artifact. This issue with performance plugin was introduced in either 1.610 or 1.611 (I suspect the later). I cannot be more precise because I rolled back from 1.610 to 1.609. Now I'm rolling from 1.611 to 1.609. 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] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Serge Zukov created JENKINS-27938 Unable to expand collapsed SLIM tables Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:41 PM Description: New styling added in the latest FitNesse plugin makes SLIM tables appear as collapsed inside captured details, however there is no way to expand them. It seems like FitNesse plugin is missing some essential java-script to allow those tables behave same way they do in FitNesse. Another option is that java-script is included but unable to interact with elements inside Jenkins page. Environment: FitNesse plugin 1.12 Jenkins 1.600 Project: Jenkins Priority: Minor Reporter: Serge Zukov 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] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Serge Zukov created JENKINS-27940 Consider using jUnit output from FitNesse Issue Type: New Feature Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:54 PM Description: In addition to XML format current version of FitNesse supports jUnit format output. It is very basic at this point (but could expended). Environment: FitNesse plugin 1.12 Jenkins 1.600 Project: Jenkins Priority: Minor Reporter: Serge Zukov 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] [fitnesse-plugin] (JENKINS-27936) When few FitNesse test results being published in a single job they renamed into Summary
Serge Zukov created JENKINS-27936 When few FitNesse test results being published in a single job they renamed into Summary Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:33 PM Description: Expected: Test name for published test results to always match content of rootPath. Actual: When job contains more than one FitNesse test results published then test name appears as "Summary". Steps to reproduce: Given you have two test suites: TestSuite1 and TestSuite2 In a single job run TestSuite1 and produce TestSuite1.xml Run TestSuite2 and produce TestSuite2.xml Publish FitNesse tests using *.xml as a mask Upon execution FitNesse test results (and test history) will contain Summary as test name. P.S. Same would occur if you use copy artifacts plugin to collect all FitNesse XML files into a single job and publish them simultaneously. Environment: Jenkins ver. 1.608; FitNesse Plugin 1.12 Project: Jenkins Priority: Minor Reporter: Serge Zukov 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.
