Skip to content

Latest commit

 

History

History
40 lines (27 loc) · 1.3 KB

README.md

File metadata and controls

40 lines (27 loc) · 1.3 KB
Raw

ci-pipeline-client

Cross-Cloud CI client for interacting with the build, provision and app deploy CI pipeline

Setup

Create .env

Add gitlab API tokens

Choose the running environment for the Cross-Cloud CI system: eg. development, staging, production. Example

  • export CROSS_CLOUD_CI_ENV="development"

which will instruct the the trigger client to load settings for that environment such as the GitLab API endpoint URL

Running the trigger client

TBD

See usage from IRB

From cron

Create a crontab entry like so:

SHELL=/bin/bash
CROSS_CLOUD_CI_ENV="staging"
#CROSS_CLOUD_CI_ENV="staging"
# CROSS_CLOUD_CI_ENV="production"
CROSSCLOUDCI_TRIGGER_WORKDIR="/home/pair/src/wolfpack/cncf/crosscloudci-trigger"
# Using RVM: run rvm alias create crosscloudci_trigger ruby-2.1.7
## TESTING
#TRIGGER_CMD="test:dataload"
## 3am build and deploy all
TRIGGER_CMD="build_and_deploy"

0 3 * * * source $HOME/.rvm/environments/crosscloudci_trigger && $CROSSCLOUDCI_TRIGGER_WORKDIR/bin/crontrigger "$TRIGGER_CMD" > "$CROSSCLOUDCI_TRIGGER_WORKDIR/logs/crosscloudci_trigger-`date +\%Y\%m\%d-\%H:\%M:\%S\%z`.log" 2>&1

To just test cron functionality with out running a full build and deploy use the "test:dataload" command for crosscloudci_trigger/crontrigger instead of build_and_deploy