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年前
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.