i really like the VSTS Power DevOps Tools and ran into a very concerning issue.
The import Solution Task deploys into a wrong environment.
How it happened:
I created a Release pipeline and tested against a backup environment (BAK). The target environment was determined in the connection string, using O365 authentication, passed in 3 variables, an authmethod, environment and user variable. When everything worked well, i cloned the stage and changed the variables to point to our integration test environment (INT).
The pipeline ran through, but deployed to the BAK environment. The log shows (in the INPUT_CRMCONNECTIONSTRING line, and later in the "crmConnectionString =" line) that the environment variable is correct, but the connection and deployment are being done to BAK (first visible in the "Connected to Org Url:" line).
Did a Microsoft ticket, even did a completely new stage in the same release pipeline with MS support, and used new variables. But the issue continued. Microsoft closed the case as unresolved and said it is the issue of the extension provider, therefore this issue.
Tasks are Power DevOps Tool Installer 12. and Import Solution 12..
Installed version is 9.17.4.
Hi,
i really like the VSTS Power DevOps Tools and ran into a very concerning issue. The import Solution Task deploys into a wrong environment.
How it happened: I created a Release pipeline and tested against a backup environment (BAK). The target environment was determined in the connection string, using O365 authentication, passed in 3 variables, an authmethod, environment and user variable. When everything worked well, i cloned the stage and changed the variables to point to our integration test environment (INT).
The pipeline ran through, but deployed to the BAK environment. The log shows (in the INPUT_CRMCONNECTIONSTRING line, and later in the "crmConnectionString =" line) that the environment variable is correct, but the connection and deployment are being done to BAK (first visible in the "Connected to Org Url:" line).
Did a Microsoft ticket, even did a completely new stage in the same release pipeline with MS support, and used new variables. But the issue continued. Microsoft closed the case as unresolved and said it is the issue of the extension provider, therefore this issue.
Tasks are Power DevOps Tool Installer 12. and Import Solution 12.. Installed version is 9.17.4.