GitHub Actions: Approvals, Environments and Visualization DEEP DIVE

Подписаться 19 тыс.

Просмотров 24 тыс.

50% 1

GitHub Actions finally have Approvals, Environments, and Visualization!
In this video we will explore those features and we will see how to set them up and use them the best way.
How to configure an environment in GitHub Actions? How to approve a deploy in GitHub Actions? What about GitHub Actions Visualization?
We will answer those questions and more in this GitHub Actions approvals, environments and visualization deep dive.
🌟EXCLUSIVE CONTENT🌟
Do you want to access exclusive content, live chats and Q&As, polls, and even 1:1 calls with me? Join my Patreon: / coderdave
🆘 NEED HELP? 🆘
Book a 1:1 Consultation with CoderDave: geni.us/cdconsult
🙏🏻SUPPORT THE CHANNEL🙏🏻
Buy me a coffee: www.buymeacoffee.com/CoderDave
PayPal me donation: paypal.me/dabenveg
💬JOIN THE COMMUNITY
► Website: coderdave.io
► Discord: geni.us/cddiscord
► Newsletter: coderdave.io/newsletter
► Blog: dev.to/n3wt0n
► GitHub: github.com/n3wt0n
► Twitter: / davidebenvegnu
► Facebook: / coderdaveyt
🎥VIDEOS
► Automate EVERYTHING with GitHub Actions: • Automate EVERYTHING wi...
► GitHub Universe 2020 RECAP: • GitHub Universe 2020: ...
► GitHub Actions Manual Trigger: • We can START GitHub Ac...
⏲TIMESTAMPS
0:00 Intro
1:21 About Environments
1:41 Enable Environments
2:35 Environments Configuration Setting
2:56 Approvers Settings
3:44 Timer Settings
4:14 Environment Secrets
6:07 Actions Configuration to Use Environments
8:43 Environments demo
9:30 Workflow visualization
10:28 Approval process
11:32 Auditing and Deployment Tracking
12:54 Wrap Up
13:16 Bloopers
🎤PODCAST: geni.us/cdpodcast
❓QUESTIONS?
Have a question about DevOps, Cloud, Coding, or Anything Else? Post in comments section of this video!
🔴SUBSCRIBE to CoderDave here: ru-vid.com?sub...
_______________
👕GET MY MERCH: geni.us/cdmerch
🔮TOOLS I USE
► Twingate - Connect to your Private Resources SECURELY: geni.us/twingate
► TubeBuddy - #1 RU-vid channel Management tool (FREE): www.tubebuddy.com/CoderDave
► Moosend - Free Newsletter and Automation Platform: geni.us/moosend
📸🖥️GEAR AND SOFTWARE
► Music - Epidemic Sound (Get 30 days free): epidemicsound.com/referral/zf...
► Editing - Adobe Premiere Pro: geni.us/AdobeVideo
► Gear I Use for RU-vid: kit.co/CoderDave/gear-i-use-f...
► Gear I Use for Streaming: kit.co/CoderDave/gear-i-use-f...
► My Computer Setup: kit.co/CoderDave/main-compute...
► Full office setup: github.com/n3wt0n/work-from-h...
Disclaimer:
Some product links are affiliate links which means if you buy something I'll receive a small commission at no additional cost to you.
As an Amazon Associate, I earn from qualifying purchases.

Наука

Опубликовано:

2 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 46

@son7211 3 года назад

Thanks! love the detail explanation. Now this is added to my favorite 😎👍

@CoderDave 3 года назад

Thanks to you! Merry Christmas if you celebrate it and happy new year 🎊

@pluralcloud1756 3 года назад

Keep your content coming- -appreciate it

@CoderDave 3 года назад

Thanks, I definitely will ☺️

@johnpaulmoaje5358 2 года назад

Very informative. Thank you for sharing!

@CoderDave 2 года назад

Glad you enjoyed it!

@CoderDave 3 года назад

✨ *Question of the day* ✨: Do you like these new features? How do you plan to use them? *SUPPORT THE CHANNEL :* Buy me a coffee: www.buymeacoffee.com/CoderDave Join my Patreon: www.patreon.com/CoderDave PayPal me donation: paypal.me/dabenveg

@MrLablanco 7 месяцев назад

Thank you mate! very useful!

@CoderDave 6 месяцев назад

Glad it helped!

@TypeScriptTV 2 года назад

Great tutorial! It showed me how to review deployment jobs. Thanks a lot! Benny

@CoderDave 2 года назад

Glad it was helpful!

@RoshanSingh-kc6os 3 года назад

Thanks for sharing this video.. really like

@CoderDave 3 года назад

Thanks! What do you like the most in the video?

@MildronizeWangth 2 года назад

Thanks Good explanation.

@CoderDave 2 года назад

Thanks, happy you liked it ☺️

@arxi29 7 месяцев назад

great tutorial

@CoderDave 6 месяцев назад

Thank you! Cheers!

@vadimkalinin8677 Год назад

Hi Dave, thanks for a great overview. Do you perhaps know if one step or job requiring approval, say Production, was once approved will this approval be inherited by consequent steps and jobs in the same workflow? Basically speaking, am I approving a particular step or the whole workflow?

@CoderDave Год назад

Happy you found this helpful. The approval is set on the environment, and the environment is set at Job level. Therefore the approval is at job level, meaning that once approved all the steps in the job will be executed.

@vadimkalinin8677 Год назад

Thanks for replying. Yeah, although I understand the logic behind, was a little upset when found this out by trials and errors. I wanted to approve 2 reusable workflows running on same environment at once. Eventually, needed to introduce separate job in front for the purpose of approval.

@LawyerAB 2 года назад

Hello, thank you for explanation. I have a question for you please. Who transfer the code between environments? For example when developers done their codes who pushes to test environment and when testers done who pushes codes to next environment? And who creates these environments on GitHub in real projects? Thanks in advance.

@CoderDave 2 года назад

Hey, happy it's been helpful About your questions is a matter of process... in many processes, no-one pushes the code... the code is pushed to the branch once... and build once, the build creates what is know as artifact (basically the result of the build, which could be a zip file, a binary, or anything that you can deploy) and then a job in the workflow deploys that artifact to the first environment (let's say Dev). if changes need to be made, the current run is invalidated, changes are made, and a new updated artifact is deployed to Dev. when the status is ok, you can approve the next deployment and a new job in teh same workflow will deploy THE SAME ARTIFACT to the next environment, and so on so forth. It is very important to note I said "the same artifact". This means that there is no build or code change between environments. The application is built once, and then the exact same binaries are deployed to the different environments (this ensure that if a binary was working in QA, it will work in staging, prod, etc because no code is changed) About the "who creates the environments", well again it depends... could be a Release manager, the DevOps team, or anyone else with enough permissions

@ammarmansoor7783 3 года назад

Hey liked the video a lot and left a like. These new features sound like they would definitely help an agile team. But quick question. How does environment protection work with mid + sized team if you have multiple developers working on different tasks in the same repo? Lets say dev one checks in code and is waiting approval and while waiting dev 2 checks in his code and is then awaiting approval as well. What is the behavior of Github Actions pipeline in this state?

@CoderDave 3 года назад

If a deployment A is waiting for approval in an environment, and another deployment B is queued for the same environment you''ll have it both waiting for approval. Then it is a matter of which one you approve first. Anyway, the other will still be in waiting state until you either approve it or cancel it.

@fernandozpiccin 3 года назад

Great video. Does anyone know if its possible to deploy releases to specific environments?

@CoderDave 3 года назад

Thanks. Do you mean the "GitHub Releases"? If so, it is not possible to deploy the releases directly (they are basically a "storage" to fix in time whatever artifact you want. But you can have an Action workflow triggered by a release creation. In the workflow you could read the content of the release and therefore use that artifact to deploy to the environment you want.

@Chatsworth1979 3 года назад

Question about what you discuss at the 12:00 mark: I created an environment. Then I clicked the code view, on the right where your screen shows Releases, Packages, and Environments mine shows Releases, Packages, and Languages. I did not actually build and deploy to the Environment, I simply created and configured one Environment. Could that be why? Maybe a build and deployment is required? Thanks for any info.

@CoderDave 3 года назад

That's correct, it won't show unless there been a deployment activity on that environment

@lee45283 Год назад

Great video, it’s very cool feature. Shame you need an enterprise subscription, seems a pretty common requirement even for small teams

@CoderDave Год назад

Very true!

@swathiashok2586 Год назад

How do I disable email notification for the review deployments approval,as I donot need email notification, is there any settings to do this at organization level instead of manually unsubscribing it can we do it in settings?

@CoderDave Год назад

I believe that, at least for now, it is not possible

@swathiashok2586 Год назад

Hey can u pls lemme know if we can modify If a job is not approved within 30 days, the workflow run will be automatically canceled. 30days to lesser number and how?

@CoderDave Год назад

Unfortunately at the moment it is not possible to change that value

@414121 3 года назад

The Environment setting, in my case, only appears on the public repository. Is that your case?

@CoderDave 3 года назад

Yes, that’s correct. I believe I mention this also in the video, Environments are available only for public repos. If you have GitHub Enterprise, then it’s available also on private repos.

@414121 3 года назад

@@CoderDave Yes, I did not notice when you comment. I re-watched the video. Thanks to and congrats on your work.

@kamalkamals 2 года назад

on settings on my project cannot found environement option

@CoderDave 2 года назад

Is it a private repo? If so it is normal, environments are available only on public repos. If you want to have them on private repos you need to be on GitHub Enterprise 😕

@kamalkamals 2 года назад

@@CoderDave yep yep it s enable by default if using normal account but not free for organization :(

@akashmohapatra1008 2 года назад

for private repository what to do ?

@CoderDave 2 года назад

Unfortunately, this is not available for private repos on either personal account or teams plan :( GitHub has decided to make this available on private repos only in the GitHub Enterprise Cloud (GHEC) :( If you are on private repos but not on GHEC, then you'd need to use some kind of workaround

@raj080288 2 года назад

Would the environment variables deploy automatically to their servers?

@CoderDave 2 года назад

Not sure what you mean. You still have the deployment steps for your environments/servers/targets in the workflow. The Environment section of the job specifications allows you to control things like environment-specific secrets, approvals, etc