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.
Comments
It's exactly what most need to automate the full process. Of course, having the chance of driving it by at least some parameters or, even better, by defining a more complete logic flow integrated with VSTS Release Management so that one may schedule releases for specific sandboxes.
Category: Lifecycle Services
Very much needed and soon from what I hear in the channel
Category: Lifecycle Services
I would further prefer a tighter integratioon with VSTS Release Management and NOT build management. Release functionality in VSTS is mature, supports approvals, scheduling, etc.
Let's add VSTS Steps / Tasks that support pushing to LCS environments. Worst case, if a Release is created it should add the artifact to LCS.
Category: Lifecycle Services
+1 adding to Timothy and Martin's ideas. It would nice to have LCS APIs that support the following:
- uploading deployable packages from build server to LCS "Asset Library/Software deployable package" as part of the build script, as a build parameter. Right now this is a manual process after a successful build when moving changes from Dev to Standard acceptance testing environment.
- initiating DP installs for sandbox environments as part of a successful build which would enable automated continuous integration. I would also see this as a build parameter. Right now this is a manual process after a successful build when moving changes from Dev to Standard acceptance testing environment via "Maintain > apply updates" for sandboxes.
Category: Lifecycle Services
It would also be good to give the VSTS release process the ability to send build artifacts to LCS and then have the ability to trigger automatic deployment through LCS for test environments.
I do like Martin's idea though.
Category: Lifecycle Services
I wouldn't like to see every build there (we may have many builds every day), so this could either be a parameter of the build template, or maybe it shouldn't push builds automatically to LCS, but instead give us an option to select a particular build from inside LCS. The LCS project is already associated with the VSTS project, so sending such a query (and then obtaining build output) wouldn't be a problem.
Category: Lifecycle Services
Administrator on 5/9/2019 4:41:51 PM
https://community.dynamics.com/365/financeandoperations/b/newdynamicsax/archive/2019/04/30/azure-devops-task-to-deploy-code
This has been released.