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

Jenkins build number set to lower number than current build number

    XMLWordPrintable

Details

    Description

      So when I want to change my build number to some other number which is a higher value than current Jenkins is accepting in the set next build number, but if I want to set that to a lower value than the current, then Jenkins is not allowing that number. To configure it to lower values I have to delete all the builds and then reset to the lower build number I wish. Which, almost like creating a new job and starting a fresh build. It seems Jenkins only accepts build numbers in ascending order not in descending order. The issue that organizations have to face when they want to change the build number like (1000 is build number and wish to change it to 500(not used for that job) )this they have to lose the build data of previous ones which are not a good thing for any organization.

      Attachments

        Activity

          karthik546 karthik paidi created issue -
          karthik546 karthik paidi made changes -
          Field Original Value New Value
          Description So when I want to change my build number to some other number which is a higher value than current Jenkins is accepting in the set next build number, but if I want to set that to a lower value than the current, then Jenkins is not allowing that number. To configured to lower values I have to delete all the builds and then reset to the lower build number I wish which is almost like creating a new job and starting a fresh build. It seems Jenkins only accepts build numbers in ascending order not in descending order. The issue that organizations have to face when they want to change the build number like this they have to lose the build data of previous ones which are not a good thing for any organization. So when I want to change my build number to some other number which is a higher value than current Jenkins is accepting in the set next build number, but if I want to set that to a lower value than the current, then Jenkins is not allowing that number. To configure it to lower values I have to delete all the builds and then reset to the lower build number I wish. Which is almost like creating a new job and starting a fresh build. It seems Jenkins only accepts build numbers in ascending order not in descending order. The issue that organizations have to face when they want to change the build number like this they have to lose the build data of previous ones which are not a good thing for any organization.
          karthik546 karthik paidi made changes -
          Description So when I want to change my build number to some other number which is a higher value than current Jenkins is accepting in the set next build number, but if I want to set that to a lower value than the current, then Jenkins is not allowing that number. To configure it to lower values I have to delete all the builds and then reset to the lower build number I wish. Which is almost like creating a new job and starting a fresh build. It seems Jenkins only accepts build numbers in ascending order not in descending order. The issue that organizations have to face when they want to change the build number like this they have to lose the build data of previous ones which are not a good thing for any organization. So when I want to change my build number to some other number which is a higher value than current Jenkins is accepting in the set next build number, but if I want to set that to a lower value than the current, then Jenkins is not allowing that number. To configure it to lower values I have to delete all the builds and then reset to the lower build number I wish. Which, almost like creating a new job and starting a fresh build. It seems Jenkins only accepts build numbers in ascending order not in descending order. The issue that organizations have to face when they want to change the build number like (1000 is build number and wish to change it to 500)this they have to lose the build data of previous ones which are not a good thing for any organization.
          karthik546 karthik paidi made changes -
          Description So when I want to change my build number to some other number which is a higher value than current Jenkins is accepting in the set next build number, but if I want to set that to a lower value than the current, then Jenkins is not allowing that number. To configure it to lower values I have to delete all the builds and then reset to the lower build number I wish. Which, almost like creating a new job and starting a fresh build. It seems Jenkins only accepts build numbers in ascending order not in descending order. The issue that organizations have to face when they want to change the build number like (1000 is build number and wish to change it to 500)this they have to lose the build data of previous ones which are not a good thing for any organization. So when I want to change my build number to some other number which is a higher value than current Jenkins is accepting in the set next build number, but if I want to set that to a lower value than the current, then Jenkins is not allowing that number. To configure it to lower values I have to delete all the builds and then reset to the lower build number I wish. Which, almost like creating a new job and starting a fresh build. It seems Jenkins only accepts build numbers in ascending order not in descending order. The issue that organizations have to face when they want to change the build number like (1000 is build number and wish to change it to 500(not used for that job) )this they have to lose the build data of previous ones which are not a good thing for any organization.
          karthik546 karthik paidi made changes -
          Attachment Screen Shot 2017-04-26 at 2.45.38 PM.png [ 37456 ]
          karthik546 karthik paidi made changes -
          Attachment Screen Shot 2017-04-26 at 2.53.21 PM.png [ 37457 ]
          karthik546 karthik paidi made changes -
          Attachment Screen Shot 2017-04-26 at 2.45.38 PM.png [ 37456 ]
          akom Alexander Komarov made changes -
          Resolution Not A Defect [ 7 ]
          Status Open [ 1 ] Closed [ 6 ]
          karthik546 karthik paidi made changes -
          Attachment Screen Shot 2017-04-26 at 2.53.21 PM.png [ 37457 ]

          People

            akom Alexander Komarov
            karthik546 karthik paidi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: