[JIRA] [robot-plugin] (JENKINS-34469) robotframework pipeline-plugin compatibility

142 views
Skip to first unread message

pwolf@cloudbees.com (JIRA)

unread,
May 19, 2016, 1:52:02 PM5/19/16
to jenkinsc...@googlegroups.com
Patrick Wolf updated an issue
 
Jenkins / New Feature JENKINS-34469
robotframework pipeline-plugin compatibility
Change By: Patrick Wolf
Summary: robotframework pipeline-plugin compatibility
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

themikenicholson@gmail.com (JIRA)

unread,
Jun 24, 2016, 12:33:03 AM6/24/16
to jenkinsc...@googlegroups.com
Mike Nicholson commented on New Feature JENKINS-34469
 
Re: robotframework pipeline-plugin compatibility

+1 The pipeline plugin is critical to our workflow and good CI/CD practices in general. It would be great to see this plugin working within the build pipeline.

I've attempted to add it to a Jenkinsfile as a general build step as follows:

Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml 
step([$class: 'RobotPublisher', outputPath: '.', passThreshold: 0, unstableThreshold: 0])

This results in the following stack trace when that step is run:

java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:305)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:248)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:192)
	at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104)
	at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134)
	at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113)
	at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)
	at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15)
	at WorkflowScript.run(WorkflowScript:27)
	at ___cps.transform___(Native Method)
	at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79)
	at sun.reflect.GeneratedMethodAccessor434.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)
	at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45)
	at sun.reflect.GeneratedMethodAccessor439.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
	at com.cloudbees.groovy.cps.Next.step(Next.java:58)
	at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
	at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:276)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:78)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:185)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:183)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
	at hudson.plugins.robot.RobotPublisher.<init>(RobotPublisher.java:106)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:305)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:248)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:192)
	at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104)
	at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134)
	at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113)
	at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151)
	at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15)
	... 35 more
Finished: FAILURE
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

themikenicholson@gmail.com (JIRA)

unread,
Jun 24, 2016, 12:59:01 AM6/24/16
to jenkinsc...@googlegroups.com
+1  The pipeline plugin is critical to our workflow and good CI/CD practices in general.  It would be great to see this plugin working within the build pipeline.  

I've attempted to add it to a Jenkinsfile as a general build step as follows:

{code:groovy}

step([$class: 'RobotPublisher', outputPath: '.', passThreshold: 0, unstableThreshold: 0])
{code}


This results in the following stack trace when that step is run:


{noformat}
{noformat}

EDIT: UPDATE

After digging into the code I was able to get the RobotPublisher step working with the following code:

{code:groovy}

    step([$class: 'RobotPublisher',
        outputPath: '.',
        passThreshold: 0,
        unstableThreshold: 0,
        otherFiles: ""])
{code}

Getting the parameters right was a little tricky since the plugin does not appear to be compatible with the pipeline syntax generator.  The lack of default parameters for otherFIles was causing the exception.

I'd be happy to provide screenshots or more details of the invalid output the pipeline syntax generator provides when the RobotPublisher is selected.  

mark@mark-fink.de (JIRA)

unread,
Jul 20, 2016, 3:19:01 AM7/20/16
to jenkinsc...@googlegroups.com
Mark Fink closed an issue as Not A Defect
 

cool. Thank you Mike! Works for me now

Change By: Mark Fink
Status: Open Closed
Resolution: Not A Defect

antechrestos@gmail.com (JIRA)

unread,
Mar 24, 2017, 7:30:01 AM3/24/17
to jenkinsc...@googlegroups.com
Ben EINAUDI commented on New Feature JENKINS-34469
 
Re: robotframework pipeline-plugin compatibility

Hi,

 

Thank you so much for this post, I have been wandering through the web before founding this.

I implemented this way:

 

step(
[
$class : 'RobotPublisher',
outputPath : outputDirectory,
outputFileName : "*.xml",
disableArchiveOutput : false,
passThreshold : 100,
unstableThreshold: 95.0,
otherFiles : "*.png",

]
)

 With this I can if I go under the build

  • see the results
  • navigate between files
  • have an history of the errors, thei age, and so on.

Yet I don't have nor results of the last build on the page of the job nor the button Robot Results on the left menu. How can I achieve this?

 

Thank you very much.
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

antechrestos@gmail.com (JIRA)

unread,
Mar 24, 2017, 7:35:04 AM3/24/17
to jenkinsc...@googlegroups.com
Ben EINAUDI updated an issue
Change By: Ben EINAUDI
Comment:
Hi,

 

Thank you so much for this post, I have been wandering through the web before founding this.

I implemented this way:

 
{quote}step(
[
{color:#6a8759}$class {color}: {color:#6a8759}'RobotPublisher'{color},
{color:#6a8759}outputPath {color}: outputDirectory,
{color:#6a8759}outputFileName {color}: {color:#6a8759}"*.xml"{color},
{color:#6a8759}disableArchiveOutput {color}: {color:#cc7832}false{color},
{color:#6a8759}passThreshold {color}: {color:#6897bb}100{color},
{color:#6a8759}unstableThreshold{color}: {color:#6897bb}95.0{color},
{color:#6a8759}otherFiles {color}: {color:#6a8759}"*.png"{color},

]
){quote}
 With this I can *if I go under the build*
* see the results
* navigate between files
* have an history of the errors, thei age, and so on.

Yet I don't have nor results of the last build on the page of the job nor the button _Robot Results_ on the left menu. How can I achieve this?

 

Thank you very much.

antechrestos@gmail.com (JIRA)

unread,
Mar 24, 2017, 7:36:02 AM3/24/17
to jenkinsc...@googlegroups.com
Ben EINAUDI reopened an issue
 

Hi,

 

Thank you so much for this post, I have been wandering through the web before founding this.

I implemented this way:

 

step(


[
$class : 'RobotPublisher',
outputPath : outputDirectory,
outputFileName : "*.xml",
disableArchiveOutput : false,
passThreshold : 100,
unstableThreshold: 95.0,
otherFiles : "*.png",

]
)

 With this I can if I go under the build

  • see the results
  • navigate between files
  • have an history of the errors, thei age, and so on.

    Yet I don't have nor results of the last build on the page of the job nor the button Robot Results on the left menu. How can I achieve this?

     

    Thank you very much.
    Jenkins / New Feature JENKINS-34469
    robotframework pipeline-plugin compatibility
    Change By: Ben EINAUDI
    Resolution: Not A Defect
    Status: Closed Reopened

    tatu.kairi@eficode.com (JIRA)

    unread,
    Aug 14, 2018, 9:05:01 AM8/14/18
    to jenkinsc...@googlegroups.com
    Tatu Kairi commented on New Feature JENKINS-34469
     
    Re: robotframework pipeline-plugin compatibility

    Bassam Khouri we do not have ETAs as we are maintaining this plugin alongside our full-day jobs. This is definitely on our radar, as it is annoyance to us as well.
    This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

    luca.maragnani@gmail.com (JIRA)

    unread,
    Sep 26, 2018, 9:41:14 AM9/26/18
    to jenkinsc...@googlegroups.com
    Luca Maragnani commented on New Feature JENKINS-34469
     
    Re: robotframework pipeline-plugin compatibility

    I'm using the workaround proposed. Everything works fine except the build is marked as FAILURE, even if RobotPublisher step succeed. This is the relevant part of jenkinsfile (results were obtained by previous execution of RF):

    node {

      try {
         stage('Test dnstool') {

             echo "R ${currentBuild.result} C ${currentBuild.currentResult}"

             step([
               $class : 'RobotPublisher',
               outputPath : 'myapp/output/',


               outputFileName : "*.xml",
               disableArchiveOutput : false,
               passThreshold : 100,
               unstableThreshold: 95.0,

               otherFiles : "*/selenium-screenshot.png,*/report-.csv",
             ])
    {{      }}}
          echo "R ${currentBuild.result} C ${currentBuild.currentResult}"stage('Test remedy-connector') {
       } catch (e) {
          throw(e)
       } finally {

    {{   }}}

    }

    The output is:
    [Pipeline] echoR null C SUCCESS[Pipeline] stepRobot results publisher started...
    -Parsing output xml:
    Done!
    -Copying log files to build dir:
    Done!
    -Assigning results to build:
    Done!
    -Checking thresholds:
    Done!
    Done publishing Robot results.[Pipeline] }[Pipeline] // stage[Pipeline] echoR FAILURE C FAILURE
     

    Thank you,

    Luca
    This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

    luca.maragnani@gmail.com (JIRA)

    unread,
    Sep 26, 2018, 9:42:17 AM9/26/18
    to jenkinsc...@googlegroups.com
    I'm using the workaround proposed. Everything works fine except the build is marked as FAILURE, even if RobotPublisher step succeed. This is the relevant part of jenkinsfile (results were obtained by previous execution of RF):
    {{node {}}

    {{  try {}}
    {{     stage('Test dnstool') {}}

    {{         echo "R ${currentBuild.result} C ${currentBuild.currentResult}"}}

    {{         step([}}
    {{           $class : 'RobotPublisher',}}
    {{           outputPath : 'myapp/output/',}}
    {{           outputFileName : "*.xml",}}
    {{           disableArchiveOutput : false,}}
    {{           passThreshold : 100,}}
    {{           unstableThreshold: 95.0,}}
    {{           otherFiles : "**/selenium-screenshot*.png,**/report-*.csv",}}
    {{         ])}}
    {{      }}}
    {{      echo "R ${currentBuild.result} C ${currentBuild.currentResult}"}}{{stage('Test remedy-connector') {}}
    {{   } catch (e) {}}
    {{      throw(e)}}
    {{   } finally {}}

     {{     }}}


    {{}}}

    {{The output is:}}
    {color:#9a9999}[Pipeline] echo{color}R null C SUCCESS{color:#9a9999}[Pipeline] step{color}Robot results publisher started...

    -Parsing output xml:
    Done!
    -Copying log files to build dir:
    Done!
    -Assigning results to build:
    Done!
    -Checking thresholds:
    Done!
    Done publishing Robot results.{color:#9a9999}[Pipeline] }{color}{color:#9a9999}[Pipeline] // stage{color}{color:#9a9999}[Pipeline] echo{color}R FAILURE C FAILURE
     

    Thank you,

    Luca

    luca.maragnani@gmail.com (JIRA)

    unread,
    Sep 26, 2018, 9:43:16 AM9/26/18
    to jenkinsc...@googlegroups.com

    tatu.kairi@eficode.com (JIRA)

    unread,
    Sep 26, 2018, 1:06:02 PM9/26/18
    to jenkinsc...@googlegroups.com
    Tatu Kairi commented on New Feature JENKINS-34469
     
    Re: robotframework pipeline-plugin compatibility

    Luca Maragnani

    Sorry but this is completely unreadable output. All I know is the workaround described is used daily all over the world, so I would hazard a guess you have something else going wrong in your pipeline that then fails the pipeline – not the calling of the publisher.

    luca.maragnani@gmail.com (JIRA)

    unread,
    Sep 26, 2018, 5:56:03 PM9/26/18
    to jenkinsc...@googlegroups.com
    I'm using the workaround proposed. Everything works fine except the build is marked as FAILURE, even if RobotPublisher step succeed. This is the relevant part of jenkinsfile (results were obtained by previous execution of RF):

      
    { { code:java}
     node { }}

    {{   try { }}
    {{      stage('Test dnstool myapp ') { }}

    {{              echo "R ${currentBuild.result} C ${currentBuild.currentResult}" }}

    {{              step([ }}
    {{            $class : 'RobotPublisher', }}
    {{            outputPath : 'myapp/output/', }}
    {{            outputFileName : "*.xml", }}
    {{            disableArchiveOutput : false, }}
    {{            passThreshold : 100, }}
    {{            unstableThreshold: 95.0, }}
    {{            otherFiles : "* * /selenium-screenshot * .png,* * /report- * .csv", }}
    {{          ]) }}

    {{             }
     echo "R ${currentBuild.result} C ${currentBuild.currentResult}" }}{{stage('Test remedy-connector') {}}
    {{    } catch (e) { }}
    {{       throw(e) }}
    {{    } finally { }}

           }
     }

    { { code } }}
     
    {{
    The relevant output is follows : }}
    {     color code : #9a9999 java }
    [Pipeline] echo {color}
    R null C SUCCESS {color:#9a9999}
    [Pipeline] step {color}
    Robot results publisher started...
    -Parsing output xml:
    Done!
    -Copying log files to build dir:
    Done!
    -Assigning results to build:
    Done!
    -Checking thresholds:
    Done!
    Done publishing Robot results.     {color:#9a9999}
    [Pipeline] } {color}{color:#9a9999}
    [Pipeline] // stage {color}{color:#9a9999}
    [Pipeline] echo {color}
    R FAILURE C FAILURE
      {code}

    Thank you,

    Luca

    EDIT: fixed formatting and pasted code.

    luca.maragnani@gmail.com (JIRA)

    unread,
    Sep 26, 2018, 5:58:01 PM9/26/18
    to jenkinsc...@googlegroups.com
    Luca Maragnani commented on New Feature JENKINS-34469
     
    Re: robotframework pipeline-plugin compatibility

    Tatu Kairi, I'm sorry for previous post in hurry. I'll do some more debugging in my code and jenkins setup.

    jielpe-cblv38@protonmail.com (JIRA)

    unread,
    Nov 27, 2018, 11:38:03 AM11/27/18
    to jenkinsc...@googlegroups.com
    jlpinardon commented on New Feature JENKINS-34469
     
    Re: robotframework pipeline-plugin compatibility

    I am able to publish robot results on build page within a pipeline. But I have two questions :

    1. When the pipeline runs its some stages on one node, and some other stages (including the robot tests) on another node, how can I be sure that publishing the results  as a post build action will retrieve the reports ?
      I haven't find how to specify that the post build robot results  publication step must run a the requested node.
    2. Results don't appears on the job page.
      Is there a workaround to publish results on job page, or is there a plan to integrate such results in pipelines ?

    Thanks for your help
    Best Regards
    J.L.P.

    jielpe-cblv38@protonmail.com (JIRA)

    unread,
    Jan 10, 2019, 9:30:02 AM1/10/19
    to jenkinsc...@googlegroups.com
     
    Re: robotframework pipeline-plugin compatibility

    Dear All,

    First of all, have a nice new year !

     

    I have another comment about the Robot Publisher. If it sets the build as unstable, the entire build is shown as unstable, which is the awaited situtation.
    But, when looking at the stages, be it on classical or blue ocean interface, all stages appear as unstable.
    For many users, this is really annoying, because they would like to more easily determine at first glance if a stage is OK or not.

    Indeed, it would , not only be cosmetic, but actually much more user friendly and I would say offer better ergonomics, if the stages were let green (and tagged as Passed) unless the one where publisher is used. Or for the best (but I guess it is a bit  more complex as it could need addtional confugration items) the step where robot tests are actually run.

    jielpe-cblv38@protonmail.com (JIRA)

    unread,
    Jan 10, 2019, 9:30:04 AM1/10/19
    to jenkinsc...@googlegroups.com
    Dear All,

    First of all, have a nice new year !

     

    I have another comment about the Robot Publisher. If it sets the build as unstable, the entire build is shown as unstable, which is the awaited situtation.
    But, when looking at the stages, be it on classical or blue ocean interface, all stages appear as unstable.
    For many users, this is really annoying, because they would like to more easily determine at first glance if a stage is OK or not.

    Indeed, it would , not only be cosmetic, but actually much more user friendly and I would say offer better ergonomics, if the stages were let green (and tagged as Passed) unless the one where publisher is used. Or for the best (but I guess it is a bit  more complex as it could need addtional confugration items) the step where robot tests are actually run.


    Thanks for your help.
    Best Regards
    J.L.P.

    jielpe-cblv38@protonmail.com (JIRA)

    unread,
    Jan 11, 2019, 4:39:02 AM1/11/19
    to jenkinsc...@googlegroups.com
    jlpinardon commented on New Feature JENKINS-34469
     
    Re: robotframework pipeline-plugin compatibility

    Hello,

    Sorry if it looks like I am insisting... But the (not so) cosmetic problem I reported above is so annoying for (perhaps miseducated) users that they want me to split the pipeline into two pieces because they don't clearly understand if the build (stricto sensu) is OK or not.
    It certainly not be a big job to do that, but it is not intellectually satisfying at all, and it breaks the pipeline concept.

    juho.saarinen+jenkins@gmail.com (JIRA)

    unread,
    Jan 14, 2019, 2:06:03 AM1/14/19
    to jenkinsc...@googlegroups.com
    Juho Saarinen assigned an issue to Juho Saarinen
    Change By: Juho Saarinen
    Assignee: jpiironen Juho Saarinen

    juho.saarinen+jenkins@gmail.com (JIRA)

    unread,
    Jan 25, 2019, 12:11:03 AM1/25/19
    to jenkinsc...@googlegroups.com
    Juho Saarinen commented on New Feature JENKINS-34469
     
    Re: robotframework pipeline-plugin compatibility

    I think above described thing comes from Jenkins itself. At least if stage fails, all stages before that are marked in standard UI as failed (just with a bit fainter color). Also, if there would be something that could do for it, it should be in another issue, as this is about pipeline support in general.
    Reply all
    Reply to author
    Forward
    0 new messages