Explore >> Select a destination
|
You are here 
|
devopsjournal.io | ||
| | | | |
chringel.dev
|
|
| | | | | This post shows an example workflow to automatically deploy the latest version of a Hugo website using GitHub Actions. | |
| | | | |
www.architect.io
|
|
| | | | | Learn how to automate the steps to build, test, and deploy your code using GitHub Actions. | |
| | | | |
wittchen.io
|
|
| | | | | Recently GitHub introduced really interesting feature to their service called Actions. Actions can be used for automating various tasks related to the repositories like CI, CD, testing, deployment and whatnot. The general concept is as follows: We can create so called action, which can be based on a JavaScript project or a Docker container. We can also use existing actions in the Marketplace. Next, we can create workflow in the yml file, where we define our workflow. Workflow can consist of on a job with many steps using different actions. We can also define multiple jobs, where one depends on another. Workflows can be triggered in many ways. E.g. by push, pull request, creating issue, publishing release, scheduled event or external event. | |
| | | | |
bravenewgeek.com
|
|
| | | Like most industry jargon, "DevOps" means a lot of things to a lot of different people. While many folks view it as specific to certain tooling or practices, such as CI/CD or Infrastructure as Code... | ||
