[JIRA] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title Sid S commented on JENKINS-27395 Re: distinguish test reports filed from different parts of workflow trejkaz, could you share your XSLT file or link to it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title
Sid S edited a comment on JENKINS-27395
Re: distinguish test reports filed from different parts of workflow
Was able to get this working as follows Documenting for future users 1. Switched from nunit3.x to mstest's .trx (xml) test output. In dotnet this simply meant swapping the logger to the mstest one even though we're still using nunit as the actual test framework i.e. {code :java } dotnet test --logger "trx;LogFileName=resultfile.trx"{code}2. Directly used the xsl file published by the mstest folks ([here|https://github.com/jenkinsci/mstest-plugin/blob/master/src/main/resources/hudson/plugins/mstest/mstest-to-junit.xsl]) to transform .trx to junit compatible .xml files. In powershell is this a simple{code :java }$Xslt = New-Object System.Xml.Xsl.XslCompiledTransform$Xslt.Load($xsltFilePath)$Xslt.Transform($xmlInputFilePath, $xmlOutputFilePath){code}3. Use a Jenkinsfile like the one below. In the traditional Jenkins UI, the stage names are get prefixed, to so tests with same namespace are now seen differently. BlueOcean UI still shows them as indistinguishable / identical duplicates {code :java }pipeline { agent {node { label 'master'} } stages {stage('variant-1') { steps {// build steps } post {always {junit 'results/*.xml'} }}stage('variant-2') { steps {// build steps } post {always {junit 'results/*.xml'} }} }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title
Sid S commented on JENKINS-27395
Re: distinguish test reports filed from different parts of workflow
Was able to get this working as follows 1. Switched from nunit3.x to mstest's .trx (xml) test output. In dotnet this simply meant swapping the logger to the mstest one even though we're still using nunit as the actual test framework i.e.
dotnet test --logger "trx;LogFileName=resultfile.trx"
2. Directly used the xsl file published by the mstest folks (here) to transform .trx to junit compatible .xml files. In powershell is this a simple
$Xslt = New-Object System.Xml.Xsl.XslCompiledTransform
$Xslt.Load($xsltFilePath)
$Xslt.Transform($xmlInputFilePath, $xmlOutputFilePath)
3. Use a Jenkinsfile like the one below. In the traditional Jenkins UI, the stage names are prefixed, to tests with same namespace are now seen differently. BlueOcean UI still shows them as indistinguishable / identical duplicates
pipeline {
agent {
node {
label 'master'
}
}
stages {
stage('variant-1') {
steps {
// build steps
}
post {
always {
junit 'results/*.xml'
}
}
}
stage('variant-2') {
steps {
// build steps
}
post {
always {
junit 'results/*.xml'
}
}
}
}
}
Add Comment
[JIRA] (JENKINS-45826) XUnit support for distinguishing test reports from different steps
Title: Message Title Sid S commented on JENKINS-45826 Re: XUnit support for distinguishing test reports from different steps Also waiting for this Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title
Sid S edited a comment on JENKINS-27395
Re: distinguish test reports filed from different parts of workflow
How do you actually consume this in a Jenkinsfile? Our tests have the same name/namespaces across different variants and each variant gets it's own build stage (it's serial for unrelated reasons below). Right now tests across multiple runs/stages are indistinguishable as identical duplicates. Currently we're using the NUnitPublisher which converts nunit3 test XMLs to junit format. We could switch from NUnitPublisher to mstest but it's unclear if we need the test transforming plugins to also be updated OR if the junit changes are sufficient (since it can pull stage names directly).Jenkins 2.124Blue Ocean 1.5.0 JUnit 1.24 Nunit 0.23 This is the pipeline being used and it doesn't work i.e. {code}pipeline { agent {node { label 'master'} } stages {stage('Build variant1') { // build steps here}stage('Publish variant 1 tests') { steps {step([$class: 'NUnitPublisher', testResultsPattern: 'results/variant1/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]) }}stage('Build variant2') { // build steps here}stage('Publish variant 2 tests') { steps {step([$class: 'NUnitPublisher', testResultsPattern: 'results/variant2/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]) }} }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title
Sid S commented on JENKINS-27395
Re: distinguish test reports filed from different parts of workflow
How do you actually consume this in a Jenkinsfile? Our tests have the same name/namespaces across different variants and each variant gets it's own build stage (it's serial for unrelated reasons below). Right now tests across multiple runs/stages are indistinguishable as identical duplicates. Currently we're using the NUnitPublisher which converts nunit3 test XMLs to junit format. We could switch from NUnitPublisher to mstest but it's unclear if we need the test transforming plugins to also be updated OR if the junit changes are sufficient (since it can pull stage names directly). Jenkins 2.124 Blue Ocean 1.5.0 This is the pipeline being used and it doesn't work i.e.
pipeline {
agent {
node {
label 'master'
}
}
stages {
stage('Build variant1') {
// build steps here
}
stage('Publish variant 1 tests') {
steps {
step([$class: 'NUnitPublisher', testResultsPattern: 'results/variant1/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true])
}
}
stage('Build variant2') {
// build steps here
}
stage('Publish variant 2 tests') {
steps {
step([$class: 'NUnitPublisher', testResultsPattern: 'results/variant2/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true])
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-47245) Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class
Title: Message Title Sid S edited a comment on JENKINS-47245 Re: Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class This is still an issue except it's Expecting "interface jenkins.tasks.SimpleBuildStep" but got "[$class: 'NUnitPublisher', testResultsPattern: 'results-all/sub.domain.com/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]" of type class java.lang.String instead Jenkins 2.124 Blue Ocean v1.5.0 Pipeline: Model API v1.2.9 Chrome v66 x64 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47245) Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class
Title: Message Title Sid S updated an issue Jenkins / JENKINS-47245 Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class Change By: Sid S Comment: This is still an issue except it's Expecting "interface jenkins.tasks.SimpleBuildStep" but got "[$class: 'NUnitPublisher', testResultsPattern: 'results-all/sub.domain.com/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]" of type class java.lang.String instead Blue Ocean v1.5.0 Pipeline: Model API v1.2.9 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47245) Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class
Title: Message Title Sid S edited a comment on JENKINS-47245 Re: Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class This is still an issue except it's Expecting "interface jenkins.tasks.SimpleBuildStep" but got "[$class: 'NUnitPublisher', testResultsPattern: 'results-all/sub.domain.com/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]" of type class java.lang.String instead Blue Ocean v1.5.0 Pipeline: Model API v1.2.9 * [|https://issues.jenkins-ci.org/secure/AddComment!default.jspa?id=185659] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47245) Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class
Title: Message Title Sid S reopened an issue This is still an issue except it's Expecting "interface jenkins.tasks.SimpleBuildStep" but got "[$class: 'NUnitPublisher', testResultsPattern: 'results-all/sub.domain.com/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]" of type class java.lang.String instead Blue Ocean v1.5.0 Pipeline: Model API v1.2.9 https://issues.jenkins-ci.org/secure/AddComment!default.jspa?id=185659 Jenkins / JENKINS-47245 Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class Change By: Sid S Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-47245) Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class
Title: Message Title Sid S commented on JENKINS-47245 Re: Ctrl+S in Pipeline Editor shows validation errors from Generic Build Step with $class This is still an issue except it's Expecting "interface jenkins.tasks.SimpleBuildStep" but got "[$class: 'NUnitPublisher', testResultsPattern: 'results-all/sub.domain.com/*.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]" of type class java.lang.String instead Blue Ocean v1.5.0 Pipeline: Model API v1.2.9 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-40058) Jobs not removed when branch gets removed in case of orphaned item strategy set
Title: Message Title Sid S commented on JENKINS-40058 Re: Jobs not removed when branch gets removed in case of orphaned item strategy set I'm also seeing that orphaned items aren't removed when specified via the jenkin's UI (a multi branch project => configure => Orphaned Item Strategy). If this works only via the Jenkinsfile, it ought to be removed from the UI to avoid confusion. A transition could be to put Stephen's comment in the UI before removing it completely. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title
Sid S edited a comment on JENKINS-34547
Re: Make WorkflowJob.concurrentBuild into a JobProperty
[~jglick]: When trying to make the entire operation contained in the Jenkinsfile single instanced, do we stick that inside the node block, outside the node block or inside/outside every stage block?Putting it inside the node block doesn't seem to prevent concurrent builds.node {properties([disableConcurrentBuilds()])// stages are here}
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.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title
Sid S commented on JENKINS-34547
Re: Make WorkflowJob.concurrentBuild into a JobProperty
Jesse Glick: When trying to make the entire operation contained in the Jenkinsfile single instanced, do we stick that inside the node block, outside the node block or inside/outside every stage block? Putting it inside the node block doesn't seem to prevent concurrent builds. {{ node { properties([disableConcurrentBuilds()]) // stages are here } }}
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.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title
Sid S edited a comment on JENKINS-34547
Re: Make WorkflowJob.concurrentBuild into a JobProperty
[~jglick]: When trying to make the entire operation contained in the Jenkinsfile single instanced, do we stick that inside the node block, outside the node block or inside/outside every stage block?Putting it inside the node block doesn't seem to prevent concurrent builds. {{ node {properties([disableConcurrentBuilds()])// stages are here} }}
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.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title Sid S commented on JENKINS-34547 Re: Make WorkflowJob.concurrentBuild into a JobProperty Jesse Glick: Why won't you mention the actual syntax here instead of RTFM? Valentin Chartier: The syntax inside the jenkins' install itself suggests properties([disableConcurrentBuilds(), pipelineTriggers([])]) I'm not sure why we need to pass the blank pipelineTriggers([]) ... but that's what it says 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.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title Sid S commented on JENKINS-34547 Re: Make WorkflowJob.concurrentBuild into a JobProperty How do users use this in their Jenkinsfile? Can't seem to find any documentation on this ... 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.
[JIRA] (JENKINS-27618) Workflow support for NUnit plugin
Title: Message Title Sid S commented on JENKINS-27618 Re: Workflow support for NUnit plugin Sebastian Godelet this is great. I did notice that if there is a single file, like "build\TestResult.xml" but if you set testResultPattern:'**TestResult.xml' then you get 2x the test failures. For some reason it double counts. Is this a known issue? 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.
[JIRA] (JENKINS-27618) Workflow support for NUnit plugin
Title: Message Title
Sid S edited a comment on JENKINS-27618
Re: Workflow support for NUnit plugin
[~sebgod] this is great. I did notice that if there is a single file, like "build\TestResult.xml" but if you set {code:java} testResultPattern:'**\\TestResult.xml' {code} then you get 2x the test failures. For some reason it double counts. Is this a known issue?
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.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title
Sid S edited a comment on JENKINS-37443
Re: Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
To anyone else reading this, you can install the NUnit Plugin (https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin) inside Jenkins. Then add {noformat}step([$class: 'NUnitPublisher', testResultsPattern: 'build\\TestResult.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]){noformat}Obviously, replace "build\TestResult.xml" with your test file name or search pattern Seems [https://issues.jenkins-ci.org/browse/JENKINS-27618]
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.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title
Sid S edited a comment on JENKINS-37443
Re: Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
To anyone else reading this, you can install the NUnit Plugin (https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin) inside Jenkins. Then add {noformat}step([$class: 'NUnitPublisher', testResultsPattern: 'build\\TestResult.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]){noformat}Obviously, replace "build\TestResult.xml" with your test file name or search patternSeems it was recently fixed at [https://issues.jenkins-ci.org/browse/JENKINS-27618]
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.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title
Sid S edited a comment on JENKINS-37443
Re: Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
To anyone else reading this, you can install the NUnit Plugin (https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin) inside Jenkins. Then add {noformat}step([$class: 'NUnitPublisher', testResultsPattern: 'build\\TestResult.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]){noformat}Obviously, replace "build\ \ TestResult.xml" with your test file name or search pattern
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.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title
Sid S edited a comment on JENKINS-37443
Re: Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
To anyone else reading this, you can install the NUnit Plugin (https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin) inside Jenkins. Then add {noformat}step([$class: 'NUnitPublisher', testResultsPattern: 'build\\TestResult.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]){noformat} Obviously, replace "build\\TestResult.xml" with your test file name or search pattern
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.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title
Sid S commented on JENKINS-37443
Re: Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
To anyone else reading this, you can install the NUnit Plugin (https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin) inside Jenkins. Then add {{step([$class: 'NUnitPublisher', testResultsPattern: 'build\\TestResult.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]) }}
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.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title
Sid S edited a comment on JENKINS-37443
Re: Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
To anyone else reading this, you can install the NUnit Plugin (https://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin) inside Jenkins. Then add { { noformat} step([$class: 'NUnitPublisher', testResultsPattern: 'build\\TestResult.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver:false, failIfNoResults: true]) {noformat } }
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.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title Sid S commented on JENKINS-37443 Re: Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline Is that still the recommended route? If so, how do you apply the xslt file for the transform? Looking for the jenkinsfile syntax ... 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.
