Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34469

robotframework pipeline-plugin compatibility

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Reopened (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: robot-plugin
    • Labels:
    • Environment:
      Jenkins ver. 1.656
    • Similar Issues:

      Description

      I am using the Jenkins pipeline and I want to include the test results from robotframework. The robot-plugin did not even make the list of required plugins so I assume it is not working??!

      https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md#build-steps-and-post-build-actions

      It would be great to have robotframework results so please let me know what you think.

        Attachments

          Activity

          Hide
          lucamaro Luca Maragnani added a comment -

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

          Show
          lucamaro Luca Maragnani added a comment - Tatu Kairi , I'm sorry for previous post in hurry. I'll do some more debugging in my code and jenkins setup.
          Hide
          jlpinardon jlpinardon added a comment -

          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.

          Show
          jlpinardon jlpinardon added a comment - I am able to publish robot results on build page within a pipeline. But I have two questions : 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. 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.
          Hide
          jlpinardon jlpinardon added a comment - - edited

          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.

          Show
          jlpinardon jlpinardon added a comment - - edited 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.
          Hide
          jlpinardon jlpinardon added a comment -

          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.

          Show
          jlpinardon jlpinardon added a comment - 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.
          Hide
          hifi Juho Saarinen added a comment -

          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.

          Show
          hifi Juho Saarinen added a comment - 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.

            People

            • Assignee:
              hifi Juho Saarinen
              Reporter:
              markfink Mark Fink
            • Votes:
              16 Vote for this issue
              Watchers:
              21 Start watching this issue

              Dates

              • Created:
                Updated: