Trafficserver Alpine container workflow fixes #7994
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
download.apache.org only contains currently-supported releases.
zrhoffman
added
Traffic Server
4 tasks
zrhoffman
force-pushed
the
alpine-ats-fixes
branch
2 times, most recently
from
b3620bc
to
3733493
Compare
Alpine versions above 3.16 do not contain package libexecinfo-dev, which ATS needs. Alpine 3.19 still fails for unknown reasons, but Alpine 3.18 builds with this fix.
zrhoffman
force-pushed
the
alpine-ats-fixes
branch
from
3733493
to
206802f
Compare
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 PR makes the GHA workflow that builds
ghcr.io/apache/trafficcontrol/ci/trafficserver-alpinepass again by${{ github.repository }}does not work in the workflow namelibexecinfo-devAlpine package from the 3.16 main repo, since Alpine versions over 3.16 do not includelibexecinfo-dev.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Check if the tests pass
PR submission checklist