From the course: GitHub Actions Cert Prep by Microsoft Press
Unlock this course with a free trial
Join today to access over 25,500 courses taught by industry experts.
Remove workflow artifacts from GitHub - GitHub Tutorial
From the course: GitHub Actions Cert Prep by Microsoft Press
Remove workflow artifacts from GitHub
- [Instructor] Why would you want to do this? I mentioned that your runners are building your app and there may be one or more artifacts that runner can bring back to you and you can download and use elsewhere, whatever the case may be. Well, we have to think about it more broadly. Again, I hate to keep bringing up cost and price, but it's the core of business, especially now in 2024. So pricing and cost is certainly very important. You're paying for minutes, potentially you're paying for cloud storage, for your packages, for your caches. So if you have outdated or unused artifacts, you may want to purge those. You should know that there's a 90 day for public repos and private repos 30 day, automatic retention period for artifacts. So they're only kept around for so long anyway. So you might want to think of in terms of governance with your development team, creating a workflow to actually archive artifacts somewhere else, persistently, maybe in Azure blob storage. We can initiate…
Contents
-
-
-
-
-
-
-
Learning objectives29s
-
(Locked)
Configure caching of workflow dependencies2m 7s
-
(Locked)
Identify steps to pass data between jobs in a workflow3m 4s
-
(Locked)
Remove workflow artifacts from GitHub3m 30s
-
(Locked)
Add a workflow status badge1m 15s
-
(Locked)
Add environment protections2m 17s
-
(Locked)
Define a matrix of different job configurations2m 40s
-
(Locked)
Implement workflow approval gates19m 40s
-
-
-
-
-
-
-
-
-
-
-