Hey all, I'm trying to improve our release process and would like to hear how others manage this in their projects.Our current process is far from optimal.. We use feature branches which get merged into dev -> test -> staging -> prod. Versioning is done manually using npm version on the dev branch before builds/deploys to that environment. I've just recently set up basic build/release pipelines in Azure Devops which is something I've been pushing for quite some time (work on a development team but not for a traditional software shop - the "cloud" is scary apparently. Everything has been onprem solutions up until recent).I realize this is a very broad question and there are a million different ways to manage this, I'm looking for general process flow, tools/utils that may be helpful, reading resources, etc.. This is such a broad topic, I'm having trouble finding a clear path to follow. All opinions are welcome!Slightly off-topic but open to advice if any cares to comment:One specific application has a Vue frontend/node backend. Two different repos, both need to be versioned per release. The web app displays the version number on the UI so it needs to be present during build time, the vue cli uses node to compile the app/templates. This makes me think versioning would have to be done in the build pipeline but then again npm version creates a commit so this would probably create a loop if builds were triggered by commits.., idk? - thinking out loud. git pre-commit hook maybe?
Submitted November 01, 2019 at 03:39PM by ABadWomanDriver
No comments:
Post a Comment