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

Ability to split sequence of jobs into multiple pipelines

    XMLWordPrintable

Details

    Description

      Useful if you have jobs that should be excluded from pipeline or you want to split sequence of jobs into multiple pipelines.

      Example flow:

      BUILD -> TEST -> DEPLOY DEV -> DEPLOY PROD
      
      • view BUILD
        BUILD -> TEST
        
      • view DEPLOY
        DEPLOY DEV -> DEPLOY PROD
        

      Attachments

        Issue Links

          Activity

            dawidmalina Dawid Malinowski created issue -
            dawidmalina Dawid Malinowski made changes -
            Field Original Value New Value
            Summary Ability to split sequence of jobs for multiple pipelines Ability to split sequence of jobs into multiple pipelines
            dawidmalina Dawid Malinowski made changes -
            Description Useful if you have jobs that should be excluded from pipeline or you want to split sequence of jobs for multiple pipelines.

            Example flow:
            {code}
            BUILD -> TEST -> DEPLOY DEV -> DEPLOY PROD
            {code}

            - view BUILD
            {code}
            BUILD -> TEST
            {code}

            - view DEPLOY
            {code}
            DEPLOY DEV -> DEPLOY PROD
            {code}
            Useful if you have jobs that should be excluded from pipeline or you want to split sequence of jobs into multiple pipelines.

            Example flow:
            {code}
            BUILD -> TEST -> DEPLOY DEV -> DEPLOY PROD
            {code}

            - view BUILD
            {code}
            BUILD -> TEST
            {code}

            - view DEPLOY
            {code}
            DEPLOY DEV -> DEPLOY PROD
            {code}
            dawidmalina Dawid Malinowski made changes -
            Link This issue is related to JENKINS-26210 [ JENKINS-26210 ]
            nnordrum Noah Nordrum added a comment -

            I think I've got a decent first crack at this. Here's my strategy:

            I added a lastJobRegex where I terminate searching for jobs/tasks when a task id matches the specified regex.

            I'm also looking at adding a hideJobRegex to satisfy JENKINS-26210.

            Thoughts? PR coming shortly (hopefully).

            nnordrum Noah Nordrum added a comment - I think I've got a decent first crack at this. Here's my strategy: I added a lastJobRegex where I terminate searching for jobs/tasks when a task id matches the specified regex. I'm also looking at adding a hideJobRegex to satisfy JENKINS-26210 . Thoughts? PR coming shortly (hopefully).
            dawidmalina Dawid Malinowski added a comment - Fixed in https://github.com/Diabol/delivery-pipeline-plugin/pull/144
            dawidmalina Dawid Malinowski made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            nnordrum Noah Nordrum added a comment -

            According to the testing I did for my implementation, this is missing some key logic. I'll track on the PR.

            nnordrum Noah Nordrum added a comment - According to the testing I did for my implementation, this is missing some key logic. I'll track on the PR.

            What exactly use cases are not covered. Please keep in mind that my change is not working with regexp.

            dawidmalina Dawid Malinowski added a comment - What exactly use cases are not covered. Please keep in mind that my change is not working with regexp.
            nnordrum Noah Nordrum added a comment -

            I'm thinking I was wrong now--you are filtering in a different (probably better, as I don't know this code that well) place than I was.

            Yup--all good! It was the termination of downstream jobs after the last job. You're doing it in ProjectUtil, I wasn't.

            nnordrum Noah Nordrum added a comment - I'm thinking I was wrong now--you are filtering in a different (probably better, as I don't know this code that well) place than I was. Yup--all good! It was the termination of downstream jobs after the last job. You're doing it in ProjectUtil, I wasn't.

            Released in 0.9.6

            patbos Patrik Boström added a comment - Released in 0.9.6
            patbos Patrik Boström made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 164882 ] JNJira + In-Review [ 209101 ]

            People

              dawidmalina Dawid Malinowski
              dawidmalina Dawid Malinowski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: