How to upload to Artifactory for use by code-server

[Jose-Matsuda]

I don't think there's documentation for this but for reference I'm in a locked-down k8s cluster serving jupyter notebooks with code-server pointing to a running code-marketplace pod for extensions. Just so users could install extensions asap, we baked in some default extensions into the built code-marketplace image but are now looking to not have to do that. We do have Jfrog Artifactory running and pushing extensions to a local artifactory repo would be much easier.

I know @janLo was able to do this, if you could share what you did with your artifactory that would be amazing :)

[code-asher]

Back when I was last testing, I would use code-marketplace add for this. So:

export ARTIFACTORY_TOKEN="my-token"
./code-marketplace add --artifactory http://artifactory.server/artifactory --repo extensions [extension to add]

Or, if you want to take the existing extensions you had in the image, you can just copy them exactly as they are into the Artifactory repo.

[Jose-Matsuda]

Back when I was last testing, I would use code-marketplace add for this. So:

export ARTIFACTORY_TOKEN="my-token"
./code-marketplace add --artifactory http://artifactory.server/artifactory --repo extensions [extension to add]

Or, if you want to take the existing extensions you had in the image, you can just copy them exactly as they are into the Artifactory repo.

Would that just be putting the .vsix files at any level in say a generic local repository?

[code-asher]

Sorry for the delay. Yup it should work in a generic repository, I think this is what I used back when I last tested.

[code-asher]

I think also any level will work, just need to make sure you put the base path in the flag, so --repo foo/bar/extensions or whatever it is. I think this should work, but I also think I only tested them at the root of the repository, so I cannot be sure.

[code-asher]

Ah wait one more thing, it is not just putting the .vsix files in a repository. The marketplace requires that the extension be extracted and put in a specific directory structure, and that the .vsix file also exist (this is for performance reasons). That is why I recommend using the add command since it does that for you, but you could manually create the expected directory structure and extract the .vsix.

[Jose-Matsuda]

Ah I see, yeah trying something that I thought would be ok from looking here

does at least produce an error message for me

The file structure must be off, could you let me know what it should look like? I was trying to gather the relevant info from the open-vsx page but I'm not too sure what it should be

[code-asher]

We used to document the structure but removed the documentation because it was much easier to use add.

But you have the right directory structure, you just need to also extract the .vsix into that directory. Here is an example of what it should look like (the structure is the same for a local dir and Artifactory):

λ ./code-marketplace --extensions-dir ./extensions add https://open-vsx.org/api/eamodio/gitlens/2024.11.2511/file/eamodio.gitlens-2024.11.2511.vsix
Unpacked eamodio.gitlens@2024.11.2511 to /home/coder/src/marketplace/extensions/eamodio/gitlens/2024.11.2511
  - eamodio.gitlens@2024.11.2511 has 0 dependencies
  - eamodio.gitlens@2024.11.2511 is not in a pack
λ tree ./extensions -L 4
./extensions # this will be vscode-extensions-local in your case
└── eamodio
    └── gitlens
        └── 2024.11.2511
            ├── [Content_Types].xml
            ├── eamodio.gitlens-2024.11.2511.vsix
            ├── extension
            └── extension.vsixmanifest

Hope that helps!

[Jose-Matsuda]

Thanks! Having it explicitly set out like this helped as I know you mentioned extracting the .vsix package but didnt know you meant like that