Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downloading Jenkins Artifacts Requires Authentik Authentication #558

Open
Kaympe20 opened this issue Jan 13, 2025 · 16 comments
Open

Downloading Jenkins Artifacts Requires Authentik Authentication #558

Kaympe20 opened this issue Jan 13, 2025 · 16 comments
Labels
bug Something isn't working

Comments

@Kaympe20
Copy link

Describe the Issue
The README instructs you to use Jenkins to get specific versions of ChroMapper. Upon loading the job URL, there is no obvious place to download a build. When trying to download the build by adding /artifact to the job URL, you are redirected to an Authentik login.

Provide Screenshots or Videos
https://github.com/user-attachments/assets/0f5f9ee1-e1e5-4c65-b7b5-1e2474ffb7ad

@Kaympe20 Kaympe20 added the bug Something isn't working label Jan 13, 2025
@Top-Cat
Copy link
Contributor

Top-Cat commented Jan 13, 2025

Working as intended.
If you want to run a version of CM other than stable or dev build it from source.

@Kaympe20
Copy link
Author

@Top-Cat
Copy link
Contributor

Top-Cat commented Jan 13, 2025

Yes, and?

@Kaympe20
Copy link
Author

@Top-Cat I am trying to download the latest stable release. Given that you are directed to go to Jenkins to grab builds, why do artifacts require authentication?

@Caeden117
Copy link
Owner

The Launcher not only downloads the latest stable, but also keeps yourself updated when new stable builds release.

We locked Jenkins artifacts behind authentication because people used them to downgrade ChroMapper and it became a hassle trying to support dozens of users who all use differing versions. At the very least, using the Launcher allows us to ensure that users are all on known versions of ChroMapper, which makes things a lot simpler from a support and debugging perspective.

@Kaympe20
Copy link
Author

Currently, I am trying to package it. Repackaging a downloader is much more difficult in comparison to being able to use the actual binaries.

@Caeden117
Copy link
Owner

Out of curiosity, whats the use case for packaging ChroMapper?

@Kaympe20
Copy link
Author

Almost every distro's app store supports flatpak. Being able to search in the usual app store is much more user friendly.

@Top-Cat
Copy link
Contributor

Top-Cat commented Jan 13, 2025

That introduces the need for people to manually update though.
If packaging is a good idea you're probably better off giving us instructions on how to do it for whatever distro you care about or building from source yourself

@Caeden117
Copy link
Owner

^^ We can consider official flatpak support if packaging ChroMapper will be a significant quality of life increase over our current solution

@Kaympe20
Copy link
Author

If you want to flatpak it, go for it!

3rd party repackaging efforts are, by their nature, an insurmountable ask on a project maintainer. Providing builds would make these tasks possible by those who ordinarily create packages for their format of choice.

@Kaympe20
Copy link
Author

Any update on creating a flatpak and/or opening the builds?

@Top-Cat
Copy link
Contributor

Top-Cat commented Jan 16, 2025

We're waiting for you

@Kaympe20
Copy link
Author

Waiting for me to do what?

@Top-Cat
Copy link
Contributor

Top-Cat commented Jan 16, 2025

If packaging is a good idea you're probably better off giving us instructions on how to do it for whatever distro you care about or building from source yourself

@Kaympe20
Copy link
Author

Flatpak is a universal packaging format that runs each app in a container. It is super popular and is included in most distros. Packaging instructions can be found here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants