Name: azure-concourse
Owner: Pivotal Cloud Foundry
Description: Azure CI/CD pipelines
Created: 2016-11-04 14:26:38.0
Updated: 2017-11-08 19:57:49.0
Pushed: 2017-07-18 19:45:51.0
Homepage: null
Size: 207
Language: HCL
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Create an Azure AD Service Principal for your subscription with “Contributor” Role on the target Azure Project
azure ad app create --name "My SVC Acct" \
--password 'P1v0t4l!P1v0t4l!' --home-page "http://MyBOSHAzureCPI" \
--identifier-uris "http://MyBOSHAzureCPI"
azure ad sp create --applicationId *!!![YOUR AD APP ID CREATED FROM PREVIOUS STEP]!!!*
azure role assignment create --spn "http://MyBOSHAzureCPI" \
--roleName "Contributor" --subscription *!!![YOUR SUBSCRIPTION ID]!!!*
git clone
this repo
EDIT!!! ci/c0-azure-concourse-poc-params.yml
and replace all variables/parameters you will want for your concourse individual pipeline run
an_major_minor_version: '1\.9\..*'
major_minor_version: '1\.9\..*'
AFTER!!! Completing Step 3 above … log into concourse & create the pipeline.
y -t <Target> login
y -t <Target> set-pipeline -p <Pipeline-Name> -c ci/c0-azure-concourse-poc.yml -l ci/c0-azure-concourse-poc-params.yml
Un-pause the pipeline
Run the init-env
job manually, you will need to review the output and record it for the DNS records that must then be made resolvable BEFORE!!! continuing to the next step:
Example:
==========================================================================================
azure_pcf_terraform_template has an 'Init' set of terraform that has pre-created IPs...
==========================================================================================
: Executing command login
o: Added subscription CF-Customer 0
: Setting subscription "CF-Customer 0" as default
: login command OK
have now deployed Public IPs to azure that must be resolvable to:
------------------------------------------------------------------------------------------
s.azure.customer0.net == 137.117.56.166
apps.azure.customer0.net == 137.117.56.166
sys.azure.customer0.net == 137.117.56.166
ler.sys.azure.customer0.net == 137.117.56.166
regator.sys.azure.customer0.net == 137.117.56.166
azure.customer0.net == 40.112.56.99
an.azure.customer0.net == 137.117.57.112
------------------------------------------------------------------------------------------
ot Start the 'deploy-iaas' Concourse Job of this Pipeline until you have confirmed that DNS is reolving correctly. Failure to do so will result in a FAIL!!!!
[DEPLOY]. AFTER!!! Completing Step 6 above … Run the deploy-iaas
job manually, if valid values were passed, a successful ERT deployment on Azure will be the result.