Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build / Integrate a GHA approval workflow #256

Closed
dtoki opened this issue Aug 21, 2020 · 8 comments
Closed

Build / Integrate a GHA approval workflow #256

dtoki opened this issue Aug 21, 2020 · 8 comments
Assignees

Comments

@dtoki
Copy link
Contributor

dtoki commented Aug 21, 2020

See Comment: #238 (comment)
Parent Issue: #238

@dtoki dtoki self-assigned this Aug 21, 2020
@dtoki dtoki changed the title Build GHA approval workflow Build / Integrate GHA approval workflow Aug 21, 2020
@dtoki dtoki changed the title Build / Integrate GHA approval workflow Build / Integrate a GHA approval workflow Aug 21, 2020
@dtoki
Copy link
Contributor Author

dtoki commented Sep 16, 2020

@commitdev/zero

Working on the approval step for GHA & Zero, GitHub does not have an explicit approval workflow mechanism for promoting a successful stage deploy to prod. I have two possible solutions, both possible:

  1. A new issue is open if the stage build is successful with the changelogs and links to a GHA prod deployment workflow the user manually triggers.

  2. A GH bot comment on the open pr if the stage build is successful, and links to a GHA prod deployment workflow the user manually triggers.

What do you guys think is the better approach here?

@bmonkman
Copy link
Contributor

2 sounds better to me. What does the "manually triggers" step look like though? Is it as easy as just clicking the link in the comment from the bot?

@dtoki
Copy link
Contributor Author

dtoki commented Sep 16, 2020

Looks like this -> then click on run workflow.

@bmonkman
Copy link
Contributor

Sounds like that might be okay. Maybe try it out and let's see how it feels?

@dtoki
Copy link
Contributor Author

dtoki commented Sep 17, 2020

Here's how it feels
dtoki-test-org/frontend-11111#1

@bmonkman
Copy link
Contributor

bmonkman commented Sep 17, 2020

The text looks like this:

Deploy to production

Staging S3 Sync: ⚙️success
Manually trigger production deployment here

I would say the header should be something "Staging Deployment Complete"
Then we should list a couple of the build steps along with "s3 sync" with their status like building artifact, tests
Also when clicking the "here" link I just see the production deploys page with nothing on it. How does someone run the production workflow from there?

@dtoki
Copy link
Contributor Author

dtoki commented Sep 17, 2020

Right 👍🏽! the text there is just a placeholder; having the build step details is probably a good idea!
you have to click Run Workflow -> Run Workflow

I think it might also be useful to also include a visual aid in the comment like 👇
Screen Shot 2020-09-17 at 3 05 22 PM

@dtoki
Copy link
Contributor Author

dtoki commented Sep 17, 2020

I'm changing the workflow to use the build artifact and not clone the repo, should be up in a bit...

Seems like you have to use the API to download an artifact from a diffrent workflow.

actions/upload-artifact#62 (comment)

@dtoki dtoki closed this as completed Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants