/explore
|
You are here 
|
github.com | ||
| | | | |
particule.io
|
|
| | | | | ||
| | | | |
www.cybershu.eu
IntroductionIn this article, we will explore the use of Kaniko and JFrog with GitHub Actions to build and push a Docker image to JFrog Artifactory. This solu... |
|
| | | | | ||
| | | | |
martinheinz.dev
Every project - regardless of whether you are working on web app, some data science or AI - can benefit from well configured CI/CD, Docker images that ... |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
