
Each CNF project now has a jarvis.yaml defining credentials for harbor and docker, kubeconfig, and certs. The existing ldap users are used in the jarvis.yaml for both the staging and non-staging phases of the CI. The kubeconfig and harbor-ca entries of the jarvis.yaml are populated during the 800 script and adds those entries as base64 encoded data so that the required format (indentations and spacing) is maintained. The Task-createProjectAccess then decodes the kubeconfig and harbor-ca and creates the secrets for them in the correct namespace. Secret creation all takes place in the Task-createProjectAccess. Change-Id: If0c243416323e36a6f7797d8d378961552193c0d
9 lines
236 B
Bash
Executable File
9 lines
236 B
Bash
Executable File
#!/bin/bash
|
|
set -ex
|
|
|
|
# development-pipeline namespace is needed by the mongodb bitnami helm release
|
|
kubectl create ns development-pipeline || true
|
|
|
|
cd ./tools/gate/jarvis/standard-container
|
|
sudo docker build -t standard-container:1.0 .
|