You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
6. Make the Service Principal a Storage Blob Data Contributor on the subscription
57
-
```
58
-
New-AzRoleAssignment -RoleDefinitionName "Storage Blob Data Contributor" -ServicePrincipalName $sp.ApplicationId
59
-
```
60
51
61
52
### Azure Virtual Machine Scale Set
62
53
To use an Azure Virtual Machine Scale Set as an Azure DevOps Scale Set Agent it has to adhere to a certain set of requirements. [The documentation](https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/scale-set-agents?view=azure-devops&WT.mc_id=M365-MVP-5003400#create-the-scale-set) contains all the required information, but at the time of writing the following things were important:
@@ -77,8 +68,7 @@ Create a Variable Group in the Azure DevOps project running the pipeline, and gi
77
68
|---|---|
78
69
| AZURE_AGENTS_RESOURCE_GROUP | Resource Group that contains the Virtual Machine Scale Sets to be used as Scale Set Agents in Azure DevOps |
79
70
| AZURE_LOCATION | Azure location where Packer will create the temporary resources |
80
-
| AZURE_RESOURCE_GROUP | Resource group containing the Azure Storage Account that will be used by Packer. The resulting Azure Managed Image will also be put in this Resource Group |
81
-
| AZURE_STORAGE_ACCOUNT | Storage Account that Packer will use to store the temporary OSDisk and the resulting sysprepped .vhd |
71
+
| AZURE_RESOURCE_GROUP | Resource group that will be used by Packer to put the resulting Azure Managed Image. |
82
72
| AZURE_SUBSCRIPTION | Subscription ID of the Azure Subscription that is used to host the temporary resources. |
83
73
| BUILD_AGENT_VNET_NAME | Name of the existing VNet to use for the VM created by Packer, put $null if you want packer to create a new one |
84
74
| BUILD_AGENT_VNET_RESOURCE_GROUP | Name of the resource group containing the existing VNet to use for the VM created by Packer, put $null if you don't have this |
@@ -158,7 +148,7 @@ When calling a template, you must provide certain parameters. For reference, ple
158
148
There is one important element you must be aware of:
159
149
160
150
- repository_base_path
161
-
- This variable dictactes how the agent should resolve the assets within this repository. When used, two things will happen:
151
+
- This variable dictates how the agent should resolve the assets within this repository. When used, two things will happen:
162
152
- First, it will clone the repository resource specified within your YML file, which represents _this_ repository
163
153
- It will also use it to properly resolve the path where this repository resides on your pipeline agent
164
154
- When a remote template is referenced within an Azure Pipeline YML file, it doesn't clone the repository. Providing this parameter will make sure these templates understands they need to clone it before being able to run any of the scripts.
Write-Host"##[section]Removing image version for image definition '$imageDefinition': $($imageToRemove.Name) with $($imageToRemove.PublishingProfile.PublishedDate)"
Write-Host"##[section]The number of images for image definition '$imageDefinition' has no more than $GalleryImagesToKeep images. No images will be removed."
0 commit comments