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

Pipeline Milestone step: Adding parameter for milestone classification

    Details

    • Similar Issues:

      Description

      Adding a parameter for milestone classification, so an older build will not override a newer build if only they belong to the same group.

      The parameter would group different milestones. The ordinal parameter is used to order the milestones in the group. The abort behavior in a group is the same as now.
      extended simplified script from above:
      sleep PARAMETER
      milestone label: 'mileStone', ordinalGroup: projectName
      sleep 5

      Example1:
      project1: started with PARAMETER = 20 (sleeps 20 sec), ordinalGroup: 'p1'
      project2: started after project1 with PARAMETER = 5, ordinalGroup: 'p2'
      --> project1 and project2 run in the same job

      Example2:
      project1: started with PARAMETER = 20 (sleeps 20 sec), ordinalGroup: 'p1'
      project2: started after project1 with PARAMETER = 5, ordinalGroup: 'p2'
      project1: started after project2 with PARAMETER = 7 (sleeps 7 sec), ordinalGroup: 'p1'
      -> first p1 is aborted through 2nd p1 build, p2 runs through.

        Attachments

          Activity

          carlosrodlop Carlos Rodríguez López created issue -
          carlosrodlop Carlos Rodríguez López made changes -
          Field Original Value New Value
          Description Adding a parameter for milestone classification, so an older build will not override a newer build if only they belong to the same group.

          The parameter groups the different milestones. The ordinal parameter is used to order the milestones in the group. The abort behavior in a group is the same as now.
          extended simplified script from above:
          sleep PARAMETER
          milestone label: 'mileStone', ordinalGroup: projectName
          sleep 5

          Example1:
          project1: started with PARAMETER = 20 (sleeps 20 sec), ordinalGroup: 'p1'
          project2: started after project1 with PARAMETER = 5, ordinalGroup: 'p2'
          --> project1 and project2 run in the same job

          Example2:
          project1: started with PARAMETER = 20 (sleeps 20 sec), ordinalGroup: 'p1'
          project2: started after project1 with PARAMETER = 5, ordinalGroup: 'p2'
          project1: started after project2 with PARAMETER = 7 (sleeps 7 sec), ordinalGroup: 'p1'
          -> first p1 is aborted through 2nd p1 build, p2 runs through.
          Adding a parameter for milestone classification, so an older build will not override a newer build if only they belong to the same group.

          The parameter would group different milestones. The ordinal parameter is used to order the milestones in the group. The abort behavior in a group is the same as now.
          extended simplified script from above:
          sleep PARAMETER
          milestone label: 'mileStone', ordinalGroup: projectName
          sleep 5

          Example1:
          project1: started with PARAMETER = 20 (sleeps 20 sec), ordinalGroup: 'p1'
          project2: started after project1 with PARAMETER = 5, ordinalGroup: 'p2'
          --> project1 and project2 run in the same job

          Example2:
          project1: started with PARAMETER = 20 (sleeps 20 sec), ordinalGroup: 'p1'
          project2: started after project1 with PARAMETER = 5, ordinalGroup: 'p2'
          project1: started after project2 with PARAMETER = 7 (sleeps 7 sec), ordinalGroup: 'p1'
          -> first p1 is aborted through 2nd p1 build, p2 runs through.

            People

            • Assignee:
              amuniz Antonio Muñiz
              Reporter:
              carlosrodlop Carlos Rodríguez López
            • Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: