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
Azure Shared Image Galleries went GA in June 2019, and it seems like a natural extension of the cloud profile functionality to allow them to be used as the source of a cloud profile image in the "Image Type" dropdown:
The configuration fields would need to include the Gallery Name, Image Definition name and Image Version, although it would be useful to be able to specify something like "latest" for the Image Version to avoid needing to keep modifying it when publishing a new version of an image definition.
As a workaround we've had to write some scripts to spin up our own long-lived virtual machines in Azure from the image gallery images every time we publish new image versions (which is quite frequently), and automate adding them as regular agents in a separate agent pool, but we'd much rather use cloud profiles to build ephemeral agents on demand.
Environment
TeamCity version: 2020.2.2
Azure plugin version: SNAPSHOT-20210708115943
The text was updated successfully, but these errors were encountered:
Cross-posted to JetBrains YouTrack... https://youtrack.jetbrains.com/issue/TW-73152
Description
Feature Request:
Azure Shared Image Galleries went GA in June 2019, and it seems like a natural extension of the cloud profile functionality to allow them to be used as the source of a cloud profile image in the "Image Type" dropdown:
The configuration fields would need to include the Gallery Name, Image Definition name and Image Version, although it would be useful to be able to specify something like "latest" for the Image Version to avoid needing to keep modifying it when publishing a new version of an image definition.
As a workaround we've had to write some scripts to spin up our own long-lived virtual machines in Azure from the image gallery images every time we publish new image versions (which is quite frequently), and automate adding them as regular agents in a separate agent pool, but we'd much rather use cloud profiles to build ephemeral agents on demand.
Environment
The text was updated successfully, but these errors were encountered: