Answers: <p>No, but you can just ignore it which you would be doing anyway if it wasn't there.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-03-01T11:16:52.753Z
Answers: Answers in SE are more useful when they are not a simple yes or no but also provide some information about the subject matter.
Answers: Evgeny Zislis
Answers: CC BY-SA 3.0
Answers: 2017-02-28T20:47:25.550Z
Answers: 2017-02-28T20:47:25.550Z
Answers: coderanger
Answers: <p>It's not possible to avoid setting the <code>BUILD_NUMBER</code> environment variable, but you can avoid using it. Try using the Jenkins plugin <a href="https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin" rel="noreferrer">Build Name Setter Plugin</a>. It adds an option in your build configuration to set the build name to whatever you want, and you can ignore the <code>BUILD_NUMBER</code> environment variable this way.</p>
  
  <p>Consider <code>1.250.5</code> versus <code>1.250.${BUILD_NUMBER}</code>. The former will be constant no matter how many times you build and the latter will increment by one every time you build. It's also possible to use other macro values in between ${} to make more interesting dynamic build numbers.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-02-28T22:28:40.397Z
Answers: 2017-02-28T22:28:40.397Z
Answers: Peter G
Body: <p>I have a job which is running very frequently, so I'd like to avoid high number of builds. Is there any way to drop job build numbers, so the job is constantly ran, but without high numbers of builds?</p>
  
Tags: <jenkins><jenkins-plugins><builds>
Title: Is it possible to build Jenkins jobs without using build numbers?
UserDisplayName: kenorb
ThreadText: # Is it possible to build Jenkins jobs without using build numbers?
  
  (Asked by: username_0 on 2017-02-28)
  
  I have a job which is running very frequently, so I'd like to avoid high number of builds. Is there any way to drop job build numbers, so the job is constantly ran, but without high numbers of builds?
  
  **Tags:** jenkins, jenkins-plugins, builds
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2017-02-28. Score: 7 | Accepted answer
  
  It's not possible to avoid setting the `BUILD_NUMBER` environment variable, but you can avoid using it. Try using the Jenkins plugin [Build Name Setter Plugin](https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin). It adds an option in your build configuration to set the build name to whatever you want, and you can ignore the `BUILD_NUMBER` environment variable this way.
  
  Consider `1.250.5` versus `1.250.${BUILD_NUMBER}`. The former will be constant no matter how many times you build and the latter will increment by one every time you build. It's also possible to use other macro values in between ${} to make more interesting dynamic build numbers.
  
  
  ---
  
  ### Answer by username_1 on 2017-02-28. Score: -3
  
  No, but you can just ignore it which you would be doing anyway if it wasn't there.
  
  > **Comments:**
  > **username_2**: Answers in SE are more useful when they are not a simple yes or no but also provide some information about the subject matter.  
  
  ---
  
  