3개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
What do you mean by "GIT TAG is not supported"?
CodePipeline is running based on CodeBuild which is based on CodeCommit (git repo), this is AWS based scenario.
So, you can perform any GIT commands you want in a buildspec + CodeCommit supports Git Tag
답변함 9달 전
0
Hey
You are correct, right now tags are not supported There was a similar question here.
Maybe you can also implement something like this for git tags? https://aws.amazon.com/blogs/devops/multi-branch-codepipeline-strategy-with-event-driven-architecture/
답변함 9달 전
0
Git tags are now supported in V2 https://aws.amazon.com/about-aws/whats-new/2023/10/aws-codepipeline-triggering-git-tags/
답변함 4달 전
관련 콘텐츠
AWS 공식업데이트됨 2년 전- AWS 공식업데이트됨 2년 전
I think he means to say when your initiator is AWS Codepipeline, git tag is not supported in that case. Yes in Codebuild, git tag is supported but not sure how to use that with Codepipeline, as you need to do ECS deploy after codebuild that is supported by Codepipeline, I mean yes you can do those same steps in Codebuild as well but ECS deploy might need some extra work.
I think the biggest hurdle for DevOps is to allow Developers to be in charge of the deployment process and when they want to switch between different version tags or different branches for deployments. I have seem this, Jenkins made it real easier with the help of Build with Parameter where you select the environment from a dropdown and select the branch/tag using an input text field and then proceeed with release.
Something like this might solve most of the issues usually Gitflow based startups are complaining about.