When the full build completes through VSTS the package should get uploaded to the shared asset library of LCS for the subscription . So that deployment can happen to multiple environment at the same time on a click.
When the VM in a cloud-hosted environment is stopped or started in Azure (e.g. via Azure automation run books), the status of the environment is not reflected in LCS. This is causing confusion on the part of users who navigate to these environments via LCS.
Our customer is using the automation run books to manage their Azure VMs in order to optimize their Azure run costs. The Azure management portal shows the correct status of the VMs in these environments.
Be able to schedule a time for deployment of a selected Deplyable Package for Sandbox Environments and Demo environments rather than it´s being applied immediately.
Time saving for "off hours" when its usually deployed, since you got the status emails for the environments to check up on the progress.
Azure DevTest labs (https://azure.microsoft.com/en-us/services/devtest-lab/) are intended for exactly this purpose; they simplify management of Dev/Test VMs, allow stopping and starting VMs on schedule (without writing any code) and so on.
Once an asset has been deployed in an environment, it is no more possible to delete it. Even there is a new "version" (i.e. ISV package or ISV license codes), it is not possible to delete the "old" one.
Being able to delete assets even if have been deployed will allow to keep a clear view of the assets.
The new IP access restrictions are very cumbersome and hard to maintain. It takes over a minute for each IP address range to be entered and we have to enter an average of 3 ranges for about 3 environments per client and about 50 clients. That's nearly a full day of time for just data entry.
This could be greatly simplified by:
1. Making it possible to set the restrictions at the LCS project level instead of the environment level.
2. When saving an IP address range, do not take 35 seconds to save (presumably you are directly updating the firewall and getting an acknowledgement back). Instead just save the data and asynchronously change the firewall. In the 0.01% of the cases where setting the firewall rules is a problem, alert people via e-mail.
The current integration of Work item types (and maybe other things) between LCS and VSTS is hardcoded, which means that you cannot link LCS to a customized VSTS Template (it is possible, but you're informed that i "May cause errors").
Since the way of using VSTS is very much dependent on how the partner works with implementations and product development (probably different from partner to partner), it should be possible to setup the mapping yourself.
So, the proposed idea is to allow for setting up the mapping instead of it being hardcoded.
The LCS version capability for the asset library is a step in the right direction, but it has limitations. Some useful additions would be:
- Ability to add/edit version description
- Release notes can only be added when the file is added, you need to be able to provide the ability to add/update release notes, even after the file has been uploaded
- Ability to be able to delete a version (in case the file was initially incorrectly selected to begin with).
Further to this, the ability to delete assets which are no longer in use is a requirement, otherwise your asset library simply continues to build up with irrelevant assets. If I have an asset for 7.1, then load a new asset for 7.2, the old asset is no longer relevant when all environments are at 7.2, and as such, it should be able to be deleted.
Another example - I deploy an asset to a PAYG environment (to test/demo), then delete the PAYG environment, the asset can't be deleted, even though it's no longer relevant. Irrelevant items in LCS asset library gets confusing. Basic cleanup functions of LCS need to be allowed by those administrating the library.
At the moment LCS does not have a fixed duration for deploying new Operations environment virtual machines, aka. we don't exactly know how long it takes. An option in the deployment settings to enable shutting down the machine(s) when they are deployed would be beneficial cost wise.