Add Cobalt Azure Linux 3 CI runs #2094
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Added Cobalt Azure Linux 3 CI runs. This includes adding the cobalt-cloud-lin-al3 azure profile for running the jobs, creating a new yml for a new pipeline for the cobalt network job queue, and moving the previously added cobalt jobs to the new pipeline. Also made a minor update to the core counts for the profiles to match the actual available cores on the cobalt VMs.
The reason for the addition of a new Azure CI pipeline is that the Cobalt machines were made in Azure East US 2 while the other azure machines were in a different region and VNet. As such, the service bus queue management machines are not able to send jobs between the two networks. The two options to work around this I came up with were to either have a new pipeline for each network we need to send runs to (which I don't think we will have many of) o,r update the liquid templates queue selection setup to include different queue lists per network and specifying the network on a per job level. I think adding the pipeline is the cleaner of these two options, at least at this moment, and keeps wider updates from being necessary.