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

various pipelines have no color

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      delivery-pipeline version: 0.6.3
      Jenkins version: 1.509.4.1
    • Similar Issues:

      Description

      There are some pipelines that have no color.
      I don't know what could be causing it.
      The only commonality between the ones that have color and the ones that don't are this:

      The ones that do NOT have color were started by an upstream change in its maven dependencies. The text will look like this:
      ****Example: #336 by anonymous, started 13 hours ago

      The ones that work property were started by regular SCM changes, or by people manually kicking it off. The text will look like this (notice "USERNAME" in the text):
      ****Example: #161 by Alex Gray, anonymous, started 11 hours ago

        Attachments

          Activity

          grayaii Alex Gray created issue -
          Hide
          grayaii Alex Gray added a comment -

          If you want to reproduce this, do this:
          1 Create a maven Jenkins project whose pom contains a dependency on another Jenkins project. Call this project "Downstream Project".
          2 Create a maven Jenkins project that does nothing but compile some stuff. Call this project "Upstream Project".

          In the project that contains a dependency, check "Build whenever a SNAPSHOT dependency is built".

          Now modify the source code for "Upstream Project" and build it.
          Jenkins will automatically kick off "Downstream Project", and the build pipeline will be blank (no colors).

          If you need help reproducing this, let me know. I can probably create a zip for you.

          Show
          grayaii Alex Gray added a comment - If you want to reproduce this, do this: 1 Create a maven Jenkins project whose pom contains a dependency on another Jenkins project. Call this project "Downstream Project". 2 Create a maven Jenkins project that does nothing but compile some stuff. Call this project "Upstream Project". In the project that contains a dependency, check "Build whenever a SNAPSHOT dependency is built". Now modify the source code for "Upstream Project" and build it. Jenkins will automatically kick off "Downstream Project", and the build pipeline will be blank (no colors). If you need help reproducing this, let me know. I can probably create a zip for you.
          grayaii Alex Gray made changes -
          Field Original Value New Value
          Description There are some pipelines that have no color.
          I don't know what could be causing it.
          The only commonality between the ones that have color and the ones that don't are this:
          The ones that do NOT have color were started by Anonymous.
              Example: #336 by anonymous, started 13 hours ago
          The ones that work property, have "USERNAME" in the text:
              Example: #161 by Alex Gray, anonymous, started 11 hours ago
          There are some pipelines that have no color.
          I don't know what could be causing it.
          The only commonality between the ones that have color and the ones that don't are this:

          The ones that do NOT have color were started by an upstream change in its maven dependencies. The text will look like this:
          ****Example: #336 by anonymous, started 13 hours ago

          The ones that work property were started by regular SCM changes, or by people manually kicking it off. The text will look like this (notice "USERNAME" in the text):
          ****Example: #161 by Alex Gray, anonymous, started 11 hours ago

          patbos Patrik Boström made changes -
          Assignee Patrik Boström [ patbos ]
          Hide
          patbos Patrik Boström added a comment -

          I was able to reproduce the problem. The bug occurs when the first Jenkins job in a pipeline has a upstream job. If so it will not find the first build in the pipeline and cant resolve the statuses for the downstream jobs.

          Show
          patbos Patrik Boström added a comment - I was able to reproduce the problem. The bug occurs when the first Jenkins job in a pipeline has a upstream job. If so it will not find the first build in the pipeline and cant resolve the statuses for the downstream jobs.
          Hide
          patbos Patrik Boström added a comment -

          Fixed the bug and added some unit tests for it.

          Show
          patbos Patrik Boström added a comment - Fixed the bug and added some unit tests for it.
          Hide
          patbos Patrik Boström added a comment -

          Fixed

          Show
          patbos Patrik Boström added a comment - Fixed
          patbos Patrik Boström made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Hide
          grayaii Alex Gray added a comment -

          I'm impressed by the fast turn around! I can't wait to try it out.

          Show
          grayaii Alex Gray added a comment - I'm impressed by the fast turn around! I can't wait to try it out.
          patbos Patrik Boström made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 152064 ] JNJira + In-Review [ 207135 ]

            People

            • Assignee:
              patbos Patrik Boström
              Reporter:
              grayaii Alex Gray
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: