[JIRA] (JENKINS-48631) Automatically remove the cache created on disk when lightweight checkout is used
Title: Message Title Lorenzo Solano Martinez commented on JENKINS-48631 Re: Automatically remove the cache created on disk when lightweight checkout is used Any updates or workaround with this one? I'm filling up a 20GBs in minutes. 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.187285.151369896.15776.1559157300325%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33450) xUnit compatibility with NUnit 3
Title: Message Title
Lorenzo Solano Martinez commented on JENKINS-33450
Re: xUnit compatibility with NUnit 3
Hi Will Appleby and Jason Carlberg, I did a simmilar trick, as follow: From https://github.com/nunit/nunit-console on branch release/3.5 I found the following test scenario
Name-space: NUnit.ConsoleRunner.Tests
Test Class: CommandLineTests
Scenario: ResultOptionWithFilePathAndFormat()
Options: ConsoleOptions options = new ConsoleOptions("tests.dll", "-result:results.xml;format=nunit2");
After changing my NUnit run step on Jenkins from old v2 console runner to V3 "%NUNIT3_HOME%\nunit3-console.exe" NUnitTests.nunit /config=%MSBuildConfiguration% --framework=net-4.5 -result:TestResult.xml;format=nunit2 The last option is what did the trick: -result:TestResult.xml;format=nunit2 , that way you tell the console runner to write the output in the V2 format and also to use the legacy (v2 default) name TestResult.xml. I'm also waiting to use a future release of the xUnit plugin with support for NUnit 3.x. I believe that the conversion process is a little bit slower for the v3 console runner. Environment:
Windows 2012 R2
Jenkins: 1.651.1
xUnit Plugin: 1.102
NUnit: 3.5 (framework and console runner with v2 driver / plugin)
Add Comment
[JIRA] (JENKINS-27860) Build does not stop if it is marked as Failure
Title: Message Title Lorenzo Solano Martinez commented on JENKINS-27860 Re: Build does not stop if it is marked as Failure Similar issue as Chee Yee. After the Process xUnit (for NUnit 2 and 3) step my build have more tasks to run. I want a "Fail Fast" behavior in order to speedup the feedback loop. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
