We are experiencing some deployment weirdness, where on some occasions a deployment process is failing on a particular step (a step template), and on other it’s working, but after a change to some other part of the deployment process.
For example, we have a failing deployment that states the following error. This deployment fails on step 1 (Check Variables 2) -
System.ArgumentNullException: Value cannot be null.
Parameter name: key
Now after deleting all subsequent steps (leaving only step 1, Check Variables 2) and creating a new release, the deployment is succeeding.
To the layman, it seems as though the failure is happening before the PowerShell script of the step Check Variables 2 (which is a step template) is run, but the error is not particularly human friendly. This theory is supported by the fact that there is no use of a parameter ‘key’ anywhere in the PowerShell script of the step.
How can we further debug what is going wrong here?
We’re happy to provide any further logs or information that you may require.