))
Let's Automate Version Number Updates - NOT!
Manage episode 424796659 series 3474375
Contenido proporcionado por HackerNoon. Todo el contenido del podcast, incluidos episodios, gráficos y descripciones de podcast, lo carga y proporciona directamente HackerNoon o su socio de plataforma de podcast. Si cree que alguien está utilizando su trabajo protegido por derechos de autor sin su permiso, puede seguir el proceso descrito aquí https://es.player.fm/legal.
This story was originally published on HackerNoon at: https://hackernoon.com/lets-automate-version-number-updates-not-a91q3x7n.
Say you need to update (bump) your software. It’s currently at version 1.2, all the required changes have been merged, and it’s time to publish version 1.3. That’s really easy, right? Change the version in one file, commit, tag, and push. Done!
Check more stories related to futurism at: https://hackernoon.com/c/futurism. You can also check exclusive content about #automation, #development, #developers-workflow, #command-line, #latest-tech-stories, #hackernoon-top-story, #software-development, #software-architecture, and more.
This story was written by: @tanker. Learn more about this writer by checking @tanker's about page, and for more stories, please visit hackernoon.com.
Dimitri Merejkowsky was release manager at Softbank Robotics in 2008. He had to bump qiBuild, a command-line application to ease C++ development, from version 1.0.1 to 1.2. The way bumpversion works is a nice combination of the two approaches I’ve mentioned before: keep the hard-coded version number in as many files as required. Then, when bumping the project from version X to version Y:Iterate over the file list and replace all occurrences of X with Y, including in the configuration file itself.
167 episodios
Compartir
