Skip to content

Commit

Permalink
Disabling travis build
Browse files Browse the repository at this point in the history
Signed-off-by: mayank <[email protected]>
  • Loading branch information
mayank authored and kmova committed May 13, 2021
1 parent 7971afa commit cdc9c1c
Show file tree
Hide file tree
Showing 6 changed files with 10 additions and 58 deletions.
46 changes: 0 additions & 46 deletions .travis.yml

This file was deleted.

11 changes: 4 additions & 7 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -41,11 +41,11 @@ ifeq (${IMAGE_TAG}, )
export IMAGE_TAG
endif

ifeq (${TRAVIS_TAG}, )
ifeq (${RELEASE_TAG}, )
BASE_TAG = ci
export BASE_TAG
else
BASE_TAG = $(TRAVIS_TAG:v%=%)
BASE_TAG = $(RELEASE_TAG:v%=%)
export BASE_TAG
endif

Expand Down Expand Up @@ -143,11 +143,8 @@ verify-src:
# Specify the name for the binaries
PROVISIONER_NFS=provisioner-nfs

# This variable is added specifically to build amd64 images from travis.
# Once travis is deprecated, this field will be replaced by image name
# used in Makefile.buildx.mk
PROVISIONER_NFS_IMAGE?=provisioner-nfs-amd64
NFS_SERVER_IMAGE?=nfs-server-alpine-amd64
PROVISIONER_NFS_IMAGE?=provisioner-nfs
NFS_SERVER_IMAGE?=nfs-server-alpine

#Use this to build provisioner-nfs
.PHONY: provisioner-nfs
Expand Down
2 changes: 1 addition & 1 deletion RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Once the release branch is created, changelog from `changelogs/unreleased` needs

The format of the release tag is either "Release-Name-RC1" or "Release-Name" depending on whether the tag is a release candidate or a release. (Example: v1.9.0-RC1 is a GitHub release tag for the release build. v1.9.0 is the release tag that is created after the release criteria are satisfied by the release candidate builds.)

Once the release is triggered, Travis build process has to be monitored. Once Travis build is passed images are pushed to docker hub and quay.io. Images can be verified by going through docker hub and quay.io. Also the images shouldn't have any high-level vulnerabilities.
Once the release is triggered, Github Actions release workflow has to be monitored. Once the release workflow is passed images are pushed to docker hub and quay.io. Images can be verified by going through docker hub and quay.io. Also the images shouldn't have any high-level vulnerabilities.

Images for the different components are published at the following location:

Expand Down
2 changes: 1 addition & 1 deletion buildscripts/build.sh
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ cd "$DIR"
# Get the git commit
GIT_COMMIT="$(git rev-parse HEAD)"

# Set BUILDMETA based on travis tag
# Set BUILDMETA based on release tag
if [[ -n "$RELEASE_TAG" ]] && [[ $RELEASE_TAG != *"RC"* ]]; then
echo "released" > BUILDMETA
fi
Expand Down
3 changes: 2 additions & 1 deletion buildscripts/provisioner-nfs/provisioner-nfs.Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,8 @@ ENV GO111MODULE=on \
GOARCH=${TARGETARCH} \
GOARM=${TARGETVARIANT} \
DEBIAN_FRONTEND=noninteractive \
PATH="/root/go/bin:${PATH}"
PATH="/root/go/bin:${PATH}" \
RELEASE_TAG=${RELEASE_TAG}

WORKDIR /go/src/github.com/openebs/dynamic-nfs-provisioner/

Expand Down
4 changes: 2 additions & 2 deletions buildscripts/push.sh
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ then
if [ ! -z "${RELEASE_TAG}" ] ;
then
# Push with different tags if tagged as a release
# When github is tagged with a release, then Travis will
# When github is tagged with a release, then github actions will
# set the release tag in env RELEASE_TAG
TagAndPushImage "${DIMAGE}" "${RELEASE_TAG}"
TagAndPushImage "${DIMAGE}" "latest"
Expand All @@ -132,7 +132,7 @@ then
if [ ! -z "${RELEASE_TAG}" ] ;
then
# Push with different tags if tagged as a release
# When github is tagged with a release, then Travis will
# When github is tagged with a release, then github actions will
# set the release tag in env RELEASE_TAG
# Trim the `v` from the RELEASE_TAG if it exists
TagAndPushImage "quay.io/${DIMAGE}" "${RELEASE_TAG}"
Expand Down

0 comments on commit cdc9c1c

Please sign in to comment.