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

Publish Fat JAR #334

Closed
vorburger opened this issue Nov 3, 2023 · 3 comments · Fixed by #393
Closed

Publish Fat JAR #334

vorburger opened this issue Nov 3, 2023 · 3 comments · Fixed by #393
Labels
build Build, CI, etc. (w.o. #testing) distro Distribution related

Comments

@vorburger
Copy link
Member

The CI build should publish enola as a "fat JAR" to a HTTP location.

Probably into a new repo like https://github.com/enola-dev/distro? (With versions like latest and folders like jar etc.)

https://docs.enola.dev/use/ can then be updated to say "DL that JAR, and run java -jar enola.jar.

This is likely step #1 of more distro Distribution related work (or maybe Container #181 first?).

@vorburger vorburger added build Build, CI, etc. (w.o. #testing) distro Distribution related labels Nov 3, 2023
@vorburger
Copy link
Member Author

b build //cli:enola_deploy.jar builds bazel-bin/cli/enola_deploy.jar, which (today) is ~34 MB.

Probably into a new repo like https://github.com/enola-dev/distro? (With versions like latest and folders like jar etc.)

Or just copy it e.g. into site/latest/ ? (And may create a DNS alias for dl.enola.dev just because that's "nicer" than docs.)

@vorburger
Copy link
Member Author

vorburger commented Dec 30, 2023

https://github.com/bazeltools/bazel_jar_jar (found from this discussion) probably isn't useful / required (because from a brief manual inspection of the JAR, I don't see any duplicate classpath entries; at least nothing too immediately obvious).

@vorburger
Copy link
Member Author

(And may create a DNS alias for dl.enola.dev just because that's "nicer" than docs.enola.dev.)

Serving the same GitHub pages from 2 different DNS names is not possible (and probably confusing); so forget that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Build, CI, etc. (w.o. #testing) distro Distribution related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant