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

Add custom path for storing and viewing robot framework results in robot plugin

XMLWordPrintable

      By default Jenkins Robot Plugin collects log files from agent (Where robot tests run) to Controller at certain location and read the logs and display Robot framework Test summary.

       

      But If we want to maintain seperate log server to store all the logs instead of storing in controller or if we want to store in different path of the controller there is no option to point to different server or path to read data from logs and view all statistics related to PASS/FAIL count.

          [JENKINS-71096] Add custom path for storing and viewing robot framework results in robot plugin

          Michael added a comment -

          Sorry for the flip-flop. I clicked the assignee field accidentally.

          Michael added a comment - Sorry for the flip-flop. I clicked the assignee field accidentally.

          Aleksi Simell added a comment -

          Hi poeticmichael,

          Sorry for the delay. A workaround for this is to use a specific artifact storage and store the log files there already during the pipeline (or during a post stage) as a separate step. Would this solve your use case?

          As a general rule of thumb, we don't want to implement features that can be easily done with one or two additional steps in pipelines. It might be a trivial feature for the end user, but can potentially add a lot of complexity to the plugin code relative to the usefulness and is not necessarily part of the plugin's primary function (i.e. parse log files and show the data in Jenkins).

          Aleksi Simell added a comment - Hi poeticmichael , Sorry for the delay. A workaround for this is to use a specific artifact storage and store the log files there already during the pipeline (or during a post stage) as a separate step. Would this solve your use case? As a general rule of thumb, we don't want to implement features that can be easily done with one or two additional steps in pipelines. It might be a trivial feature for the end user, but can potentially add a lot of complexity to the plugin code relative to the usefulness and is not necessarily part of the plugin's primary function (i.e. parse log files and show the data in Jenkins).

          Tatu Kairi added a comment -

          Closing due to not going to implement this feature. As Aleksi commented, storing the report files is not the main function of the plugin

          Tatu Kairi added a comment - Closing due to not going to implement this feature. As Aleksi commented, storing the report files is not the main function of the plugin

            aleksisimell Aleksi Simell
            arunkumar784 Arunkumar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: