Help validate Linux installer publishing

[derberg]

Reason/Context

This PR introduced automation for publishing of MacOS pkg file. It was also designed in the way that it should be easy to plug in generation of installer files for Windows and Linux.

This issue is for folks that work on Linux machine and can do some local testing to check if all works as expected

Description

• First make sure installer generation works:
  • run npm run pack:linux
  • installer should be produced in dist directory. Try to install CLI using it
• Then open a PR with the following changes
  • Uncomment this part in the artifact publishing job: https://github.com/asyncapi/cli/blob/master/.github/workflows/upload-release-assets.yml#L18-L21 and modify as much as needed
  • I don't know what will be the name of the generated installer, so you will probably have to refactor existing script for MacOS installer renaming -> https://github.com/asyncapi/cli/blob/master/scripts/macosPackRename.js
  • Update Readme instructions on how to quickly install CLI with new installer -> https://github.com/asyncapi/cli#installation

[derberg]

/gfi ci-cd

[aayushmau5]

Hey! I use linux. I'll try this out.

[aayushmau5]

Though, I'm not sure whether we should really use .deb extension. We should use both ig, since .deb will only support debian based distros. Maybe we can publish .deb installer, and provide installation instructions for other distros.

[aayushmau5]

Got this error(truncated).

[derberg]

@aayushmau5 thanks a bunch for looking into this 🙏🏼

yeah .deb is just there in a comment but doesn't have to end up like this. I do not even know what they generate really. IT can be tarball if this is ok, as long as there are good instructions on how to use it on linux

in regards to the error - seem to me like some local permissions issue no?

[aayushmau5]

in regards to the error - seem to me like some local permissions issue no?

Maybe. I'll look into this, and let you know whether it's an error on my end or not.

[derberg]

@aayushmau5 hey, any luck?

[aayushmau5]

@derberg Not really. I was able to bypass the previous permission error by using a docker to build the package inside a container. But I got another error.

I'm not sure if it's a due to the container I'm using. I'll try again.

Edit: Most likely docker container. I'll try with another container.

[aayushmau5]

@derberg Ok, I was able to get the package. Had to install some additional packages related to apt package manager.

The pack:linux command outputs the following file:

Ran dpkg -i asyncapi_0.21.2.515e58d-1_amd64.deb to install the deb file. And, we got asyncapi command now :D

[derberg]

yes yes yes 🚀

THANKS!!!

you ok to take it forward and extend release pipeline as I described in the PR? Existing "renaming" script will for sure have to be extended with rename of the .deb file.

[aayushmau5]

you ok to take it forward and extend release pipeline as I described in the PR?

Sure. :rocket: