Fix issue when deploying to the :rw Management Server about vsts-release-aas HOT 8 CLOSED

I just uploaded v1.3.2 which contains your PR. If you can validate if it is working as expected.

from vsts-release-aas.

@liprec I can see that the extension has been updated:

However, the agents still seem to use to old version:

Any idea how to force update this? I'm using Azure Pipelines hosted agents (vs2017-win2016).

from vsts-release-aas.

What helped for my, but cannot validate if it is true, is to alter the pipeline and save a new version: add a space to a filled input field as those are trimmed before being saved, but it enabled the save button.

from vsts-release-aas.

Tried that + a completely new pipeline. No success so far... maybe it just takes some time...

from vsts-release-aas.

Must say that I do not have no experience with self-hosted agents (if I recall it correctly).
So probably patience is the best solution 😉

from vsts-release-aas.

I've just created a new Azure Subscription and a new Azure DevOps organization for the sole pupose testing this. I'm still only seeing the 1.3.1 version being used in this completely new environment.

Would it have to do with the fact that this file should be updated to for a new release? https://github.com/liprec/vsts-release-aas/blob/master/vss-extension.json

I'm not familiar with releasing these extensions so my apologies if this does not make sense whatsoever.

from vsts-release-aas.

Unfortunately that is not the case as the entry in the Azure DevOps martketplace is disconnected from the code in GitHub.
But you triggered me and I found that the individual tasks didn't had a new version number and waas still showing the 1.3.1 version.
Now I have fixed this and updated the task to 1.3.3.

from vsts-release-aas.

Went on holiday so I was not able to test it until today. I hereby confirm that the extensions is now updated and it now successfully deploys to the :rw server!

Thanks for your effort!

from vsts-release-aas.