fix Cannot find module 'argparse' issue

[flomader]

Resolves #1610

[arturcic]

LGTM!!

Unfortunately we cannot publish the pre-release versions as of now via CI, as we don't have valid token for publishing.
@JakeGinnivan we need valid token for marketplace publishing.

I'll merge the PR, thank you for your contribution!

[asbjornu]

@arturcic, I know @JakeGinnivan has too many GitHub notifications to follow them, so please try to reach out to him in other channels.

[jaq316]

Any luck on reaching @JakeGinnivan ?

[gep13]

@arturcic @asbjornu what exactly is required here?

[arturcic]

@gep13 we need a valid PAT (personal access token) on marketplace. I am a member on marketplace, but the PAT I generate is not valid, last time @JakeGinnivan has generated one. I talked to Jake few weeks ago when this issue first time appeared. I did not have time to ping him again.

[arturcic]

Would be great if I can generate myself a valid PAT

[asbjornu]

What would be required for you to generate a valid PAT, @arturcic?

[arturcic]

That's only an assumption, to have a valid PAT you need to have owner permissions, currently I have only contributor, Jake and Pascal have owner. Still I am able to manually publish the artifacts on marketsplace, but not from command line in a CI scenario

[gep13]

@arturcic ok, this is something we need to get sorted out. Are there any other permissions that are needed?

[gep13]

@asbjornu I reached out to @JakeGinnivan and he has issued @arturcic with a PAT that will get him started. He mentioned that you are an Administrator of the VSTS Project. Are you in a position to add @arturcic as an administrator as well (as well as everyone else on the team)?

[arturcic]

I got the new PAT from @JakeGinnivan, but it seems it's not valid :(

[gep13]

@arturcic doh! :-( @asbjornu would you be able to have a look at this, to see if you can create a PAT, or ideally, add @arturcic to the package as well?

[kicybot]

Looking forward to this release in Azure DevOps :)

[asbjornu]

In the settings for GitVersion on Azure DevOps, @arturcic is listed as an administrator already.

[arturcic]

That is right, but I need to be here https://marketplace.visualstudio.com/manage/publishers/gittools

[arturcic]

[gep13]

Perhaps @pascalberger can help in this regard as well?

[asbjornu]

Aha. I have no access there at all:

Can @pascalberger please make @arturcic an owner then?

[gep13]

Sounds like it would be good to get yourself @asbjornu added in there as well 😄 Is there anyone else that should be added? Is there a document that lists all the places that contributors to GitVersion need to be given access? I think that this would be a good thing to have, as a reference for bringing on new people. Perhaps this is something that @arturcic could compile, since he has gone through it most recently?

[arturcic]

Sure

[asbjornu]

Yep, I wouldn't mind having access, @gep13. Just need to get @pascalberger's attention. 😄

[pascalberger]

Where do I need to give you permissions? In the Azure DevOps organization you seem to be already an collection administrator @asbjornu. I failed to find where to set permissions for marketplace when I looked quickly. Do you know how to get there?

I'll be occupied with meetings the whole day, but try to have another look as soon as I find a few minutes.

[asbjornu]

@pascalberger, it's in here as @arturcic wrote in #1631 (comment).

[pascalberger]

@asbjornu Mmh, I also get a 403 while accessing this site...

[gep13]

@pascalberger @asbjornu @arturcic I have reached out to @JakeGinnivan to see if he can offer any help here.

[JakeGinnivan]

Finally got the right permissions page thanks to the link @asbjornu posted the other day. I was in a totally different area trying to grant permissions..

@arturcic you are owner, I can't add @gep13 or @asbjornu because apparently .co.uk and .no are both not valid domains :P

[gep13]

@asbjornu my suspicion is that it is complaining because mine is an MSA with custom domain. I have passed on another email address to @JakeGinnivan

[asbjornu]

My Gmail address might be considered valid, perhaps. I’ll DM it to you, @JakeGinnivan.

[mvrmoreira]

Nice!

[ahmadakhmiev]

Any progress on this one guys?

[arturcic]

I'll try to generate a new token and try to upload a vsix from command line to see if it works, I hope I can find some time today

[jaq316]

Any progress here?

[arturcic]

Unfortunately none, busy with other stuff for now, hopefully will have time to have a look. Sorry, doing only when I have some free time left, it's not my day by day job

[jaq316]

Ofcourse. Thank you. Wish I could contribute in solving this.

[jaq316]

Is there anything I can do to help this along?

[xzuttz]

This is ridiculous

[gep13]

@xzuttz said...
This is ridiculous

This is open source. There are no guarantees when, or if, things well get done. All time given to this repository and its tools is volunteer, and I would ask you to consider that when posting things like this.

[cyan198]

I tried today and I'm also having this issue in linux agent. I guess it hasn't released to marketplace?

Thanks.

[kmiterror]

Since it takes long to update the Azure DevOps task I have made a workaround.
Install .net core git version cli
Add ".NET Core" task to your build
Set Command to "Custom"
Set Custom Command to "tool"
Set Arguments to "install -g GitVersion.Tool --version 5.0.0 --ignore-failed-sources"

Use gitversion tool
Add ".NET Core" task to your build
Set Command to "Custom"
Set Custom Command to "gitversion"
Set Arguments to "/output buildserver /nofetch"

In fact -g option in first step should not be used because it install gitversion globally.
It might be a good enough workaround for most Azure DevOps users.

[arturcic]

@kmiterror I wonder why don't you use the latest task? https://marketplace.visualstudio.com/items?itemName=gittools.gitversion. You will have to unistall and then install back to the organization. Otherwise it's using the older cached version

[arturcic]

@cyan198 , it was already released

[kmiterror]

Ahh, I missed that one, I assumed that since the issue is not closed then it's not released yet.
If that's the case my workaround is no longer needed.