Get Log for each Jenkins pipeline stage












5















Anyone know how I can get the separate logs (for each pipeline stage) as the Blue Ocean shows. I need to attach them to Jira but I can not find them.
Any idea?



enter image description here










share|improve this question



























    5















    Anyone know how I can get the separate logs (for each pipeline stage) as the Blue Ocean shows. I need to attach them to Jira but I can not find them.
    Any idea?



    enter image description here










    share|improve this question

























      5












      5








      5








      Anyone know how I can get the separate logs (for each pipeline stage) as the Blue Ocean shows. I need to attach them to Jira but I can not find them.
      Any idea?



      enter image description here










      share|improve this question














      Anyone know how I can get the separate logs (for each pipeline stage) as the Blue Ocean shows. I need to attach them to Jira but I can not find them.
      Any idea?



      enter image description here







      jenkins jenkins-pipeline jenkins-blueocean






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 9:48









      Alessandra DiasAlessandra Dias

      465




      465
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I'm doing the same thing with the global pipeline library I'm building. This is good for cases where you just want to email the logs of a particular failed stage. Here's how hope it helps. On the sample pipeline below a job named test is executed once (build #1)



          Sample pipeline



          pipeline {
          agent any
          stages{
          stage("Compile") {
          steps {
          script {
          echo "Compiling..."
          }
          }
          }
          stage("Test") {
          steps {
          script {
          echo "Testing..."
          }
          }
          }
          stage("Build") {
          steps {
          script {
          echo "Building..."
          }
          }
          }
          }
          }




          1. Access the API to see execution details. Notice that each object of this JSON includes the attributes id and result.
            http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/




            [
            {
            *snip*
            "actions": ,
            "displayDescription": null,
            "displayName": "Compile",
            "durationInMillis": 341,
            "id": "6",
            "input": null,
            "result": "SUCCESS",
            "startTime": "2018-11-24T18:14:16.196+0800",
            "state": "FINISHED",
            "type": "STAGE",
            "causeOfBlockage": null,
            "edges": [
            {
            "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
            "id": "15",
            "type": "STAGE"
            }
            ],
            "firstParent": null,
            "restartable": true
            },
            {
            *snip*
            "actions": ,
            "displayDescription": null,
            "displayName": "Test",
            "durationInMillis": 246,
            "id": "15",
            "input": null,
            "result": "SUCCESS",
            "startTime": "2018-11-24T18:14:16.693+0800",
            "state": "FINISHED",
            "type": "STAGE",
            "causeOfBlockage": null,
            "edges": [
            {
            "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
            "id": "24",
            "type": "STAGE"
            }
            ],
            "firstParent": "6",
            "restartable": true
            },
            {
            *snip*
            "actions": ,
            "displayDescription": null,
            "displayName": "Build",
            "durationInMillis": 270,
            "id": "24",
            "input": null,
            "result": "SUCCESS",
            "startTime": "2018-11-24T18:14:17.188+0800",
            "state": "FINISHED",
            "type": "STAGE",
            "causeOfBlockage": null,
            "edges": ,
            "firstParent": "15",
            "restartable": true
            }
            ]


          2. Use result to check the status of a stage (SUCCESS, FAILED, ABORTED, etc...)



          3. Use id to get into a particular stage, for this example the logs of Test stage which has an id of 15.



            http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/15/log/




            Testing...







          share|improve this answer


























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444196%2fget-log-for-each-jenkins-pipeline-stage%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I'm doing the same thing with the global pipeline library I'm building. This is good for cases where you just want to email the logs of a particular failed stage. Here's how hope it helps. On the sample pipeline below a job named test is executed once (build #1)



            Sample pipeline



            pipeline {
            agent any
            stages{
            stage("Compile") {
            steps {
            script {
            echo "Compiling..."
            }
            }
            }
            stage("Test") {
            steps {
            script {
            echo "Testing..."
            }
            }
            }
            stage("Build") {
            steps {
            script {
            echo "Building..."
            }
            }
            }
            }
            }




            1. Access the API to see execution details. Notice that each object of this JSON includes the attributes id and result.
              http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/




              [
              {
              *snip*
              "actions": ,
              "displayDescription": null,
              "displayName": "Compile",
              "durationInMillis": 341,
              "id": "6",
              "input": null,
              "result": "SUCCESS",
              "startTime": "2018-11-24T18:14:16.196+0800",
              "state": "FINISHED",
              "type": "STAGE",
              "causeOfBlockage": null,
              "edges": [
              {
              "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
              "id": "15",
              "type": "STAGE"
              }
              ],
              "firstParent": null,
              "restartable": true
              },
              {
              *snip*
              "actions": ,
              "displayDescription": null,
              "displayName": "Test",
              "durationInMillis": 246,
              "id": "15",
              "input": null,
              "result": "SUCCESS",
              "startTime": "2018-11-24T18:14:16.693+0800",
              "state": "FINISHED",
              "type": "STAGE",
              "causeOfBlockage": null,
              "edges": [
              {
              "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
              "id": "24",
              "type": "STAGE"
              }
              ],
              "firstParent": "6",
              "restartable": true
              },
              {
              *snip*
              "actions": ,
              "displayDescription": null,
              "displayName": "Build",
              "durationInMillis": 270,
              "id": "24",
              "input": null,
              "result": "SUCCESS",
              "startTime": "2018-11-24T18:14:17.188+0800",
              "state": "FINISHED",
              "type": "STAGE",
              "causeOfBlockage": null,
              "edges": ,
              "firstParent": "15",
              "restartable": true
              }
              ]


            2. Use result to check the status of a stage (SUCCESS, FAILED, ABORTED, etc...)



            3. Use id to get into a particular stage, for this example the logs of Test stage which has an id of 15.



              http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/15/log/




              Testing...







            share|improve this answer






























              0














              I'm doing the same thing with the global pipeline library I'm building. This is good for cases where you just want to email the logs of a particular failed stage. Here's how hope it helps. On the sample pipeline below a job named test is executed once (build #1)



              Sample pipeline



              pipeline {
              agent any
              stages{
              stage("Compile") {
              steps {
              script {
              echo "Compiling..."
              }
              }
              }
              stage("Test") {
              steps {
              script {
              echo "Testing..."
              }
              }
              }
              stage("Build") {
              steps {
              script {
              echo "Building..."
              }
              }
              }
              }
              }




              1. Access the API to see execution details. Notice that each object of this JSON includes the attributes id and result.
                http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/




                [
                {
                *snip*
                "actions": ,
                "displayDescription": null,
                "displayName": "Compile",
                "durationInMillis": 341,
                "id": "6",
                "input": null,
                "result": "SUCCESS",
                "startTime": "2018-11-24T18:14:16.196+0800",
                "state": "FINISHED",
                "type": "STAGE",
                "causeOfBlockage": null,
                "edges": [
                {
                "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
                "id": "15",
                "type": "STAGE"
                }
                ],
                "firstParent": null,
                "restartable": true
                },
                {
                *snip*
                "actions": ,
                "displayDescription": null,
                "displayName": "Test",
                "durationInMillis": 246,
                "id": "15",
                "input": null,
                "result": "SUCCESS",
                "startTime": "2018-11-24T18:14:16.693+0800",
                "state": "FINISHED",
                "type": "STAGE",
                "causeOfBlockage": null,
                "edges": [
                {
                "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
                "id": "24",
                "type": "STAGE"
                }
                ],
                "firstParent": "6",
                "restartable": true
                },
                {
                *snip*
                "actions": ,
                "displayDescription": null,
                "displayName": "Build",
                "durationInMillis": 270,
                "id": "24",
                "input": null,
                "result": "SUCCESS",
                "startTime": "2018-11-24T18:14:17.188+0800",
                "state": "FINISHED",
                "type": "STAGE",
                "causeOfBlockage": null,
                "edges": ,
                "firstParent": "15",
                "restartable": true
                }
                ]


              2. Use result to check the status of a stage (SUCCESS, FAILED, ABORTED, etc...)



              3. Use id to get into a particular stage, for this example the logs of Test stage which has an id of 15.



                http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/15/log/




                Testing...







              share|improve this answer




























                0












                0








                0







                I'm doing the same thing with the global pipeline library I'm building. This is good for cases where you just want to email the logs of a particular failed stage. Here's how hope it helps. On the sample pipeline below a job named test is executed once (build #1)



                Sample pipeline



                pipeline {
                agent any
                stages{
                stage("Compile") {
                steps {
                script {
                echo "Compiling..."
                }
                }
                }
                stage("Test") {
                steps {
                script {
                echo "Testing..."
                }
                }
                }
                stage("Build") {
                steps {
                script {
                echo "Building..."
                }
                }
                }
                }
                }




                1. Access the API to see execution details. Notice that each object of this JSON includes the attributes id and result.
                  http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/




                  [
                  {
                  *snip*
                  "actions": ,
                  "displayDescription": null,
                  "displayName": "Compile",
                  "durationInMillis": 341,
                  "id": "6",
                  "input": null,
                  "result": "SUCCESS",
                  "startTime": "2018-11-24T18:14:16.196+0800",
                  "state": "FINISHED",
                  "type": "STAGE",
                  "causeOfBlockage": null,
                  "edges": [
                  {
                  "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
                  "id": "15",
                  "type": "STAGE"
                  }
                  ],
                  "firstParent": null,
                  "restartable": true
                  },
                  {
                  *snip*
                  "actions": ,
                  "displayDescription": null,
                  "displayName": "Test",
                  "durationInMillis": 246,
                  "id": "15",
                  "input": null,
                  "result": "SUCCESS",
                  "startTime": "2018-11-24T18:14:16.693+0800",
                  "state": "FINISHED",
                  "type": "STAGE",
                  "causeOfBlockage": null,
                  "edges": [
                  {
                  "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
                  "id": "24",
                  "type": "STAGE"
                  }
                  ],
                  "firstParent": "6",
                  "restartable": true
                  },
                  {
                  *snip*
                  "actions": ,
                  "displayDescription": null,
                  "displayName": "Build",
                  "durationInMillis": 270,
                  "id": "24",
                  "input": null,
                  "result": "SUCCESS",
                  "startTime": "2018-11-24T18:14:17.188+0800",
                  "state": "FINISHED",
                  "type": "STAGE",
                  "causeOfBlockage": null,
                  "edges": ,
                  "firstParent": "15",
                  "restartable": true
                  }
                  ]


                2. Use result to check the status of a stage (SUCCESS, FAILED, ABORTED, etc...)



                3. Use id to get into a particular stage, for this example the logs of Test stage which has an id of 15.



                  http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/15/log/




                  Testing...







                share|improve this answer















                I'm doing the same thing with the global pipeline library I'm building. This is good for cases where you just want to email the logs of a particular failed stage. Here's how hope it helps. On the sample pipeline below a job named test is executed once (build #1)



                Sample pipeline



                pipeline {
                agent any
                stages{
                stage("Compile") {
                steps {
                script {
                echo "Compiling..."
                }
                }
                }
                stage("Test") {
                steps {
                script {
                echo "Testing..."
                }
                }
                }
                stage("Build") {
                steps {
                script {
                echo "Building..."
                }
                }
                }
                }
                }




                1. Access the API to see execution details. Notice that each object of this JSON includes the attributes id and result.
                  http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/




                  [
                  {
                  *snip*
                  "actions": ,
                  "displayDescription": null,
                  "displayName": "Compile",
                  "durationInMillis": 341,
                  "id": "6",
                  "input": null,
                  "result": "SUCCESS",
                  "startTime": "2018-11-24T18:14:16.196+0800",
                  "state": "FINISHED",
                  "type": "STAGE",
                  "causeOfBlockage": null,
                  "edges": [
                  {
                  "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
                  "id": "15",
                  "type": "STAGE"
                  }
                  ],
                  "firstParent": null,
                  "restartable": true
                  },
                  {
                  *snip*
                  "actions": ,
                  "displayDescription": null,
                  "displayName": "Test",
                  "durationInMillis": 246,
                  "id": "15",
                  "input": null,
                  "result": "SUCCESS",
                  "startTime": "2018-11-24T18:14:16.693+0800",
                  "state": "FINISHED",
                  "type": "STAGE",
                  "causeOfBlockage": null,
                  "edges": [
                  {
                  "_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
                  "id": "24",
                  "type": "STAGE"
                  }
                  ],
                  "firstParent": "6",
                  "restartable": true
                  },
                  {
                  *snip*
                  "actions": ,
                  "displayDescription": null,
                  "displayName": "Build",
                  "durationInMillis": 270,
                  "id": "24",
                  "input": null,
                  "result": "SUCCESS",
                  "startTime": "2018-11-24T18:14:17.188+0800",
                  "state": "FINISHED",
                  "type": "STAGE",
                  "causeOfBlockage": null,
                  "edges": ,
                  "firstParent": "15",
                  "restartable": true
                  }
                  ]


                2. Use result to check the status of a stage (SUCCESS, FAILED, ABORTED, etc...)



                3. Use id to get into a particular stage, for this example the logs of Test stage which has an id of 15.



                  http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test/runs/1/nodes/15/log/




                  Testing...








                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 27 '18 at 4:38

























                answered Nov 24 '18 at 10:51









                Quirino GervacioQuirino Gervacio

                91679




                91679
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444196%2fget-log-for-each-jenkins-pipeline-stage%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    Origin of the phrase “under your belt”?