When the Azure Artifact Manager plugin is used to archive artifacts into an Azure Storage Account, those artifacts available through Jenkins from the Azure Storage Account are only available through the Azure Storage Account blob URL.
Because those artifacts are only available through the Azure Storage Account blob URL, the user clicking the link is downloading the artifact from the region that the Azure Storage Account is located in. Therefore, if those users are geographically distributed, they will potentially be downloading artifacts from a region far from their own and will have slower download speeds.
To mitigate this issue, the Azure Artifact Manager plugin can be updated to optionally support an Azure Content Delivery Network (CDN) URL in place of the Azure Storage Account blob URL. This will allow the Jenkins maintainer to optionally setup an Azure CDN endpoint URL so that when a user downloads an artifact from Jenkins, it will use the CDN URL instead which will pull the artifact from a region closer to the user, instead of from the region that the Azure Storage Account is located in.
Upstream changes
Because the Azure Artifact Manager plugin is dependent on the Azure Storage plugin and a different CDN can be setup for every Azure Storage Account, the Azure Storage plugin will need to be updated to support linking an Azure CDN endpoint URL for a specific Azure Storage Account.
Are you interested in contributing this feature?
Yes, I am actively working on implementing this feature across the Azure Storage plugin and the Azure Artifact Manager plugin.
What feature do you want to see added?
When the Azure Artifact Manager plugin is used to archive artifacts into an Azure Storage Account, those artifacts available through Jenkins from the Azure Storage Account are only available through the Azure Storage Account blob URL.
Because those artifacts are only available through the Azure Storage Account blob URL, the user clicking the link is downloading the artifact from the region that the Azure Storage Account is located in. Therefore, if those users are geographically distributed, they will potentially be downloading artifacts from a region far from their own and will have slower download speeds.
To mitigate this issue, the Azure Artifact Manager plugin can be updated to optionally support an Azure Content Delivery Network (CDN) URL in place of the Azure Storage Account blob URL. This will allow the Jenkins maintainer to optionally setup an Azure CDN endpoint URL so that when a user downloads an artifact from Jenkins, it will use the CDN URL instead which will pull the artifact from a region closer to the user, instead of from the region that the Azure Storage Account is located in.
Upstream changes
Because the Azure Artifact Manager plugin is dependent on the Azure Storage plugin and a different CDN can be setup for every Azure Storage Account, the Azure Storage plugin will need to be updated to support linking an Azure CDN endpoint URL for a specific Azure Storage Account.
Are you interested in contributing this feature?
Yes, I am actively working on implementing this feature across the Azure Storage plugin and the Azure Artifact Manager plugin.