Multi-deployment workflow with job-level approvals

[Chessray]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

We're currently in Bitbucket and would like to move over to GitHub. I've started testing with one repository, and I'm mostly there. However, we seem unable to replicate our current usage of Bitbucket pipelines:

• Right now, all our services run through a build step and are then auto-deployed to the first environment stage.
• We run some tests there and promote manually to the next stage whenever we feel like doing so.
• This promotion can take anywhere between minutes to weeks, depending on the service and the delivered feature. (I know we should work towards automated CD and we are, but that's still a loooooong way ahead.)
• I found this article which is close to what we need, but it states:

GitHub has a default 72-hour timeout for workflows, so approvals must happen within this timeframe.

This doesn't fit our working model which I'd like to keep in place at least for now.

Granted, we're currently on the free tier as we're still in the experimental phase; but I can't see anything that matches this idea in any of the features list, not even for Enterprise level. Am I missing something, or how do others implement this kind of practice?

[Chessray]

I was afraid something along these lines would be the only response. 🙁 Now I only need to think of a nice way to provide the container image version to use for the "promotion" steps.

We currently upload a built container into ECR and update the ECS task definitions upon deployment. I figured out a way for the image version to be handed over from the build to the autodeploy for the first environment, but I can't apply the same principle to a manually triggered step.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬