Just an idea, but if I understand you well, you may want to split the concept of Jenkins build number and the build number for you application. Maybe an SQLite db (or any other database type) where you could read/write with your main version, and make an incremental entry for the version build number and the related jenkins build number. This way you could keep a track of the matching version without altering the Jenkins behaviors and avoiding Jenkins build number clash.
Using either sh/bat and sqlite command line this should be easy to do. You can also put a cgi or wsgi web page that could display/search into the db if needed. Keep the db on the master and access it with the master node and this should work. My new thumb rules with pipeline, if you can do it outside of pipeline script itself it's way easier and robust to do so. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3275a328-0e19-4cfe-a8a8-1cac98710a52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
