Any of those help Based on [agent folder]\bin\Add-JavaCapabilities.ps1, there are JDK 6,7,8, no JDK 9, so it can’t recognize JDK 9. I submit a user voice here: VSTS build agent capabilities for JAVA 9, you can vote it. You can try to add capability manually:
fixed the issue. Will look into that further When an exception occurs in a .NET assembly that has debugging information, the paths in the pdb files will be the paths of the source file where the assembly was compiled. In this case, that is c:\BuildAgent\work\92648d34566a49aa....
VSTS BuildAgent can not find the installed certificate
around this issue just in case, if it helps someone, The problem was that the VSO Agent(xxxx) Windows Service was running as ‘Local Service’ logon account, I had to change that to build Agent user, now the build task is able to find the certificate.
Building on a Self-hosted VSTS-BuildAgent for VS 2017 fails with error "The TransformWebConfig task could not be lo
I wish this helpful for you We have support for these features in the CI/CD tasks for extensions. These build tasks also offer the option of bumping the version of the extension and the build tasks included in the extension. You can standardize the build process using a Task Group if you want to. Or use Release Management to promote the vsix from dev to prod. These tasks will actually override the publisher-id. You will also have to override the extension-id and make it private. Only one public prod extension can be made public and extension-ids are globally unique. The alternative is to build the dev and the release vsix at the same time to ensure they're matching. Then don't use the release package until you need it.