Installation Issues on Agent Version about aws-toolkit-azure-devops

[stevejroberts]

That's extremely useful information, thanks for digging in and letting us know!

Another user also reported that after install the S3 Upload task was awol and only the CLI task was visible but we hadn't yet come up with a cause or a resolution. We've been waiting on an email thread with Microsoft to see what diagnostics or logging might be available within VSTS/TFS to try to get further information, but haven't had a response so far. So far as install goes, it appears extension authors have no control or diagnostic available that we can turn on to help resolve issues.

Our investigation into the missing S3 task had also turned up the different agent for this PowerShell-related task, although it didn't occur to us to try removing that task since, well, it's a valid task we want to keep! The task code was originally sourced from the vsts-tasks repo and then modified, but we kept the agent version. It might be that we can downgrade the agent version and still have it work across all the environments - I'll start testing on that now. If that doesn't work, I guess we could always restructure the extension so that tasks requiring higher minimum agent versions are listed at the end and hopefully that would work around the subsequent tasks simply disappearing.

I'll also follow up on our email thread with Microsoft that the apparent cause has been found and suggest an enhancement that allows installation to skip over tasks that have higher agent versions that available (and report that they have done so) rather than drop the task and all subsequent ones on the floor.

[jdrharding]

Hi Steve,

Happy to help! This extension is proving very useful in automating our organization's CI/CD, a big thanks to you and your team for providing the community with these tools.

I was unsure if the higher minimumAgentVersion was there for a reason or not, so rather than tamper with it, I simply removed reference to the PS module script when packaging the VSIX and everything was fine from that point onward (other than the task in question being unavailable, of course). If you need any other information, please let me know; I'm willing to help in any way I can.

[stevejroberts]

Drilling further, the agent requirement for v2.115.0 was to support use of the agent.tempDirectory variable. If we can fall back to some other temp location, we should be able to drop the minimum agent requirement safely.

Turns out some of our other tasks are affected in reverse - the Beanstalk and CodeDeploy tasks both use the same variable to get the temp folder and are therefore open to failing in the older TFS environments even though they declare a lower agent version.

[stevejroberts]

v1.0.8 has now been released, which downgrades the minimum agent version for the PowerShell task to match the others, and adapts to the presence of the Agent.TempDirectory variable based on the installed agent version. This resolves the missing tasks issue so far as we can tell from our TFS2015 install setup.

Resolving issue; feel free to reopen if you still encounter issues.