From ee6dff2676a1ca89acc63c066345fb6b56d9ea11 Mon Sep 17 00:00:00 2001 From: Sunny Date: Wed, 29 Jan 2020 14:54:17 +0530 Subject: [PATCH] kube-scheduler publish --- .travis.yml | 16 ++++++++++++++++ README.md | 10 ++++++++++ publish.sh | 8 ++++++++ 3 files changed, 34 insertions(+) create mode 100644 .travis.yml create mode 100644 README.md create mode 100644 publish.sh diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 0000000..0b21980 --- /dev/null +++ b/.travis.yml @@ -0,0 +1,16 @@ +language: go +dist: bionic +services: + - docker +go: + - 1.13.5 +env: + global: + - CONTAINER_TAG=v1.17.0 +script: + - docker build . -f kube-scheduler/Dockerfile -t storageos/kube-scheduler:latest +deploy: + - provider: script + script: bash publish.sh + on: + tags: true diff --git a/README.md b/README.md new file mode 100644 index 0000000..eb7929b --- /dev/null +++ b/README.md @@ -0,0 +1,10 @@ +## kube-scheduler release branch + +This branch is for automated release of kube-scheduler container images only. +To create a new release, ensure that the `CONTAINER_TAG` in .travis.yaml is the +tag for the new release and create a git tag from this branch, `kube-scheduler`. +Git tags trigger a release build in the CI. Changes to the branch only builds +the container image. + +Any change related to kube-scheduler build, including k8s version upgrade, +should be done in the [Dockerfile](kube-scheduler/Dockerfile). diff --git a/publish.sh b/publish.sh new file mode 100644 index 0000000..c009f60 --- /dev/null +++ b/publish.sh @@ -0,0 +1,8 @@ +#!/usr/bin/env bash + +set -Eeuxo pipefail + +docker login -u "$REGISTRY_USER" -p "$REGISTRY_KEY" "$CONTAINER_REGISTRY" +NEW_IMAGE="$CONTAINER_REGISTRY/$PID/kube-scheduler:$CONTAINER_TAG" +docker tag storageos/kube-scheduler:latest "$NEW_IMAGE" +docker push "$NEW_IMAGE"