Teams struggle to build and deploy exact Git-tagged releases
Teams using managed build and hosting services want a Git tag to identify the exact version to build, deploy, or roll back to. In the reports, some services instead built from branch heads, pushing teams to create extra branches or force-push a deployment branch. The requests are several years old, so current platform support and demand need to be checked before building.
For mobile and web development teams shipping versioned releases. Mentioned from Feb 2019 to Mar 2022 on GitHub.
9 different people described this problem in 3 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 6.2/10
- Frequency
- 8.3/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
A workaround is creating a new branch off each tag you want a build config for and setting it up as a new build config in AppCenter, which is time consuming
I was able to use the "Incoming webhooks" feature to get amplify to only builds the app when a "release" event is triggered in GitHub, but it's still building the latest version of the branch, making reverting to a previous release/branch in GitHub pointless.
MichaelRoberts-FlashParking on GitHub (aws-amplify/amplify-hosting)Dec 2020Asked for a toolHas a workaround
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 5 places to find your first customers
- 8 more quotes from people who have this problem
- Current workarounds, existing solutions and risks