GITBOOK-102: No subject

Author: Sofie Toft Kristensen

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md

@@ -13,10 +13,14 @@ Before setting up the pipeline in Azure DevOps, make sure that the following ste
 
 Next, you will need to define your pipeline in YAML and use it to interact with the Umbraco Cloud API.
 
+{% hint style="info" %}
+Are you using version 1? Follow the [guide for Azure DevOps v1 instead](azure-devops-v1.md).
+{% endhint %}
+
 {% hint style="info" %}
 The Umbraco CI/CD Team has created a sample pipeline for Azure DevOps.
 
-The Scripts are provided as is. This means that the scripts will do the bare minimum for a pipeline that is utilizing the CI/CD flow. 
+The Scripts are provided as is. This means that the scripts will do the bare minimum for a pipeline that is utilizing the CI/CD flow.
 
 You'll need to adapt and integrate the script into your own pipelines to gain the ability to do deployments to your Umbraco Cloud projects.
 
@@ -174,7 +178,7 @@ It is recommended to handle the `API Key` as a secret. This can be done by ticki
 You can customize the names for the variables as you like, however, you then need to rename the affected variables in `azure-release-pipeline.yaml`.
 
 Check the references to the variables in the yaml files match the variable syntaxes in the created variable. Example: `umbracoCloudApiKey` = `UMBRACOCLOUDAPIKEY`.
-{% endhint %} 
+{% endhint %}
 
 When you click on "Save and Run" your first deployment will be triggered. Which means that Azure DevOps is set up with all the needed information to be able to deploy your Cloud project back to Umbraco Cloud.
 
@@ -191,7 +195,7 @@ While working on your project locally, add a new Document type.
 
 ## High level overview of the pipeline components
 
-The mentioned scripts are provided as a starting point. 
+The mentioned scripts are provided as a starting point.\
 It is recommended that you familiarize yourself with the scripts and with documentation related to how to use Azure DevOps.
 
 The scripts demonstrates the following:
@@ -206,7 +210,7 @@ The `azure-release-pipeline.yaml` is the main pipeline, and is the one that will
 
 You can add your Build and Test stage between the `cloudSyncStage` and `cloudPrepareArtifact` stages. Keep in mind that you do not need to retain the dotnet build artifact for upload later. The `cloudPrepareArtifact` job will take care of packaging all your source code and upload to Umbraco Cloud.
 
-Make sure that you checkout the potentially updated code if you add Build and Test steps. 
+Make sure that you checkout the potentially updated code if you add Build and Test steps.
 
 ### Cloud-sync
 
@@ -216,7 +220,7 @@ If you don't want the pipeline to commit back to the triggering branch, this is
 
 ### Cloud-artifact
 
-The `cloud-artifact.yml` shows how you can prepare and package an artifact and finally upload it to Umbraco Cloud. 
+The `cloud-artifact.yml` shows how you can prepare and package an artifact and finally upload it to Umbraco Cloud.
 
 There are a couple of things here to be aware of:
 

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/github-actions.md

@@ -13,10 +13,14 @@ Before setting up the pipeline in GitHub, make sure that the following steps fro
 
 Next, you will need to define your pipeline in YAML and use it to interact with the Umbraco Cloud API.
 
+{% hint style="info" %}
+Are you using version 1? Follow the [guide for GitHub Actions version 1](github-actions-v1.md).
+{% endhint %}
+
 {% hint style="info" %}
 The Umbraco CI/CD Team has created a sample pipeline for GitHub Actions.
 
-The Scripts are provided as is. This means that the scripts will do the bare minimum for a pipeline that is utilizing the CI/CD flow. 
+The Scripts are provided as is. This means that the scripts will do the bare minimum for a pipeline that is utilizing the CI/CD flow.
 
 You'll need to adapt and integrate the script into your own pipelines to gain the ability to do deployments to your Umbraco Cloud projects.
 
@@ -75,6 +79,7 @@ You will also need the alias of the environment you want to target. [This articl
 * Create another `repository secret` with the name `PROJECT_ID` and the `Project ID` value from the Umbraco Portal.
 
 Now go to the **Variables** tab
+
 * Create a `repository variable` called `TARGET_ENVIRONMENT_ALIAS` and enter the environment alias you selected earlier.
 
 {% hint style="info" %}
@@ -104,7 +109,7 @@ jobs:
       umbracoCloudApiKey: ${{ secrets.UMBRACO_CLOUD_API_KEY }} # change the part inside the curly braces
     with:
       targetEnvironmentAlias: ${{ vars.TARGET_ENVIRONMENT_ALIAS }} # change the part inside the curly braces
-``` 
+```
 {% endhint %}
 
 Now GitHub is set up with the needed information to be able to run a deployment back to Umbraco Cloud.
@@ -220,7 +225,7 @@ While working on your project locally, add a new Document type.
 
 ## High level overview of the pipeline components
 
-The mentioned scripts are provided as a starting point. 
+The mentioned scripts are provided as a starting point.\
 It is recommended that you familiarize yourself with the scripts and with documentation related to how to use GitHub Actions.
 
 The scripts demonstrates the following:
@@ -235,7 +240,7 @@ The `main.yml` is the main pipeline, and is the one that will be triggered on a
 
 You can add your Build and Test jobs between the `cloud-sync` and `cloud-artifact` jobs. Keep in mind that you do not need to retain the dotnet build artifact for upload later. The `cloud-artifact` job will take care of packaging all your source code and upload to Umbraco Cloud.
 
-Make sure that you checkout the potentially updated code if you add Build and Test steps. 
+Make sure that you checkout the potentially updated code if you add Build and Test steps.
 
 ### Cloud-sync
 
@@ -245,7 +250,7 @@ If you don't want the pipeline to commit back to the triggering branch, this is
 
 ### Cloud-artifact
 
-The `cloud-artifact.yml` shows how you can prepare and package an artifact and finally upload it to Umbraco Cloud. 
+The `cloud-artifact.yml` shows how you can prepare and package an artifact and finally upload it to Umbraco Cloud.
 
 There are a couple of things here to be aware of: