Static build #14
Merged
Static build #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ericonr
force-pushed
the
static-build
branch
2 times, most recently
from
f3818f0
to
e61be3d
Compare
|
This depends on cnpem/epics-in-docker#75 |
ericonr
force-pushed
the
static-build
branch
3 times, most recently
from
d3478d2
to
f709574
Compare
This was referenced Sep 4, 2024
henriquesimoes
requested changes
Sep 5, 2024
ericonr
force-pushed
the
static-build
branch
from
da25fab
to
70716be
Compare
henriquesimoes
approved these changes
Sep 9, 2024
| source: ./ | ||
| target: /opt/rffe-epics-ioc | ||
| working_dir: /opt/rffe-epics-ioc | ||
| command: lnls-build-static-ioc rffe-epics-ioc |
There was a problem hiding this comment.
If we don't change this lnls-build-static-ioc arguments interface, this PR is good to be merge, IMO.
ericonr
force-pushed
the
static-build
branch
2 times, most recently
from
990dbe8
to
a4f477b
Compare
We are no longer going to use containers for this application, because we are interested in moving away from Docker, and launching Podman from udev rules, as our design requires, no longer works on modern distros [1]. Launching a service to monitor podman would work, but requires complicated integration (the native systemd-podman integration isn't available in Debian 12), so we decided to move to the same setup as afc-epics-ioc, with static binaries. The container creation scheme is also removed. [1] https://www.marcusfolkesson.se/blog/systemd-udev/
musl allows us to produce a fully static binary, which can be deployed on almost any machine. The intended deployment directory is /opt/rffe-epics-ioc, so that's where we build the IOC, to guarantee that envPaths has the correct definitions. Add the resulting tarball to .gitignore as well.
The CI workflow will test that building the IOC is always working. The resulting tarball for tags will also be published in the project's release page. We used the softprops/action-gh-release action because it was recommended by the now unmantained official action, actions/upload-release-asset [1]. [1] https://github.com/actions/upload-release-asset
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is in progress
Depends on a few changes which are going to be applied to epics-in-docker as well.