Explore >> Select a destination
|
You are here 
|
janik6n.net | ||
| | | | |
actuated.dev
|
|
| | | | | Learn how to publish container images for both Arm and Intel machines from 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. | |
| | | | |
blog.oddbit.com
|
|
| | | | | At work we have a cluster of IBM Power 9 systems running OpenShift. The problem with this environment is that nobody runs Power 9 on their desktop, and Docker Hub only offers automatic build support for the x86 architecture. This means there's no convenient options for building Power 9 Docker images...or so I thought. It turns out that Docker provides GitHub actions that make the process of producing multi-architecture images quite simple. | |
| | | | |
heltweg.org
|
|
| | | Deploy to google kubernetes engine using gitlab ci | ||
