title: How to deal Semantic Versioning on Jenkins
body: <p>I'm beginning on Jenkins in my work place. We use semantic versioning with Teamcity and I want to implement the same on Jenkins. My problem appears when I store the artifacts in builds folder ($JENKINS_HOME/jobs/$JOB_NAME/builds/$BUILD_NUMBER) because Jenkins use only the build_number to create the folder for build so when I have to reset de Build_number the future artifacts will be stored in the folder of previous builds. </p>
  
  <blockquote>
    <p>For example:</p>
    
    <p><em>I have build 1.3.1_develop.1 stored, when I reset Build_Number the next build should be 1.3.2_develop.1 and it should be stored in the
    folder 1 of build 1.3.1_develop.1</em></p>
  </blockquote>
  
  <p>My question is if someone could explain me how to deal with automatic semantic versioning on jenkins because we reset the build number we increase the mayor, minor and patch number.</p>
  
  <p>Jenkins Version: 2.89.4
  Jobs--> We use jobs to compile Vuejs for front and to deploy back with python (If this helps)</p>
  
  <p>Thanks for any help.</p>