Skip to content
Snippets Groups Projects
Commit a4653274 authored by (INACTIVE) Marcel Bajdel (new marcel.bajdel)'s avatar (INACTIVE) Marcel Bajdel (new marcel.bajdel) :rocket:
Browse files

Checking the pipeline on changes to the README

parent 20153466
No related branches found
No related tags found
3 merge requests!20Release,!13Docker image branch,!12Docker image branch
......@@ -27,8 +27,6 @@ build_branch:
name: gcr.io/kaniko-project/executor:debug
entrypoint: [""]
script:
#install git
- apt-get update && apt-get install -y git
# specify auths for kaniko executor
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
# Read the value of DOCKER_LATEST_IMAGE_EXISTS from the artifact
......@@ -44,9 +42,6 @@ build_branch:
- changes:
- '*'
build_main: # This build will run only for main branch
stage: build_main
image:
......
......@@ -11,7 +11,7 @@ Pipeline can be distinguished into two main branches: build and test.
The build can be triggered either by a new tag or merge to the main branch. The tests validate the image and store the outcome in a .log file as an artifact. If the image with tag latest doesn't exist it will be build and pushed to the registry.
1. Use kaniko to build the image. ([kaniko](https://docs.gitlab.com/ee/ci/docker/using_kaniko.html))
2. Do just a basic test to validate the image (manifest)
2. Do just a basic test to validate the image (manifest).
## Building
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment