1 Answer
- Newest
- Most votes
- Most comments
0
Hi, In. this article, you have sem auto-versionning for an AWS Pipeline with code on GitHub repo: https://alexrmoran.medium.com/automatic-semver-versioning-using-github-actions-and-deploying-to-aws-pipeline-5fcbf7e5cce4
AWS Commit is equivalent to Azure Repo and GitHub repos
If you combine this article, with this AWS doc re. semver for AWS CodeBuild, you can achieve what you're after.
Best,
Didier
Relevant content
- asked 2 years ago
- asked a year ago
- asked 9 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hi, the article mentions MAJOR.MINOR.PATCH, but what I'm trying to do is MAJOR.MINOR.PATCH.BUILD, with BUILD being an auto increment on every pipeline run. Even a manual pipeline run should auto increment the BUILD number, which semver seems to only do on a commit (?)