While investigating in preparation for this meeting, I did talk with one of the other ADO teams and found there was an issue that could have been causing this for some customers up until yesterday. It should be fixed now.
That’s not quite what the situation was. The problem was not with our artifact but with the ADO distribution of it. It was not the update itself that broke anything, it was the fact that our update prompted people to download a new copy and ADO munged the distribution.
They say they’ve fixed it. We’ve been waiting for someone to contradict that, and so far no one has.
This may be pure coincedence, but we encountered a similar experience with the Bicep extension for VSCode. Again, it looks like a CDN issue with a download that’s maintained by a Marketplace team from a Microsoft product. Maybe all Microsoft-owned Marketplaces use a shared CDN infrastructure? This is tracked in this thread on Github.
(as a side-note, glad I am finally able to post this reply. I’ve been trying for a week, but couldn’t post it as my account was limited to three replies per topic…)
Yes, I understand that it was a distribution issue, and that the update didn’t deliver correctly.
Was I was getting at, was that reinstalling fixed it for some people, and then you said that you released 8.2.2, and it still broke it again for some people.
What I was hoping for was that we could see an update get pushed since they say they fixed it, and not have any errors in that delivery for people. I’m currently seeing 8.2.1 as the latest version on our installed extension, so no update has been delivered since the original push of 8.2.1 that broke things for us. Unless for some reason we are just stuck at 8.2.1.
We don’t have any new functionality to deliver. The only point of an update would be to change the number so that people would (re)install. But we don’t need to increment the number for you to do that. The functionality in 8.2.1 is good. Just reinstall it.
Hi there, i’m a little bit confused here, what did you guys solved with reinstalling the extension, get the task running again or also get rid of the pinned version in your pipeline? i’m reading other comments that say that they solved the issue with reinstalling the extension but still not clear to me if the issue was not being able to download/run the task or focussed on the pinned version. If my task is running but sonar is complaining about pinned version for SonarQubePrepare@8, re-installing the extension will make sonar get rid of that complain and let me use the major version without any issue?
The problem was that the ADO delivery of our (perfectly fine) extension was munging the artifact. Unintstall/reinstall sometimes delivered a fresh, clean copy of the artifact.
