I created a Pipeline on gitlab.com for my .NET project with Shared runners and a build step in which I create a .msi installer for the (Windows) users.
The artifact I created in the build step comes in an archive. Zipping a .msi file seems useless to me, since it is already an archive.
But in the release step I managed to expose the .msi to the public by creating a link to
on the release page.
I made my project public, so my users can see my release page with the .msi-link and download the software.
It all works… but only when I am logged in. When I log out and click on the link, I get a 404 error. And I don’t want every user to create a gitlab account just to download the software!
I read this article:
but I don’t know how this approach can be useful to me. The link in this format does not seem to work for me. Am I wrong?
Actually what I want, is when I create a new tag (with
only: - tags?) that my audience can download a new version of my application within minutes. Is the approach I did the best approach? If so, how can the link be publicly available?