Skip to content

Harden OpenSSL source fetch in Docker build to avoid 3.5.8 release-asset 404 failures - #32

Draft
keithboone with Copilot wants to merge 3 commits into
mainfrom
copilot/fix-failing-github-actions-job
Draft

Harden OpenSSL source fetch in Docker build to avoid 3.5.8 release-asset 404 failures#32
keithboone with Copilot wants to merge 3 commits into
mainfrom
copilot/fix-failing-github-actions-job

Conversation

Copilot AI commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

The build workflow failed while building the OpenSSL stage because OPENSSL_VERSION=3.5.8 resolved to a GitHub release-asset URL that returns 404. This PR makes OpenSSL source retrieval resilient to distribution-path differences across upstream hosts.

  • Build reliability: OpenSSL download fallback chain

    • Replaced single-source wget with ordered fallback URLs for the same tarball:
      • GitHub release asset
      • GitHub tag archive
      • www.openssl.org current + old/3.5
      • source.openssl.org current + old/3.5
    • Build now errors only after all known sources fail.
  • Behavioral scope

    • No change to version selection logic (OPENSSL_VERSION resolution remains unchanged).
    • No change to OpenSSL build/configure/install flow after tarball retrieval.
OPENSSL_TARBALL="openssl-${OPENSSL_VERSION}.tar.gz"
OPENSSL_URLS="...release... ...archive... ...openssl.org... ...source.openssl.org..."
DOWNLOAD_OK=0
for URL in ${OPENSSL_URLS}; do
  if wget -O "${OPENSSL_TARBALL}" "${URL}"; then
    DOWNLOAD_OK=1
    break
  fi
done
[ "${DOWNLOAD_OK}" -eq 1 ] || { echo "ERROR: Failed to download OpenSSL ${OPENSSL_VERSION} from all known sources"; exit 1; }

Co-authored-by: keithboone <36998841+keithboone@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix failing GitHub Actions job 'build' Harden OpenSSL source fetch in Docker build to avoid 3.5.8 release-asset 404 failures Aug 17, 2026
Copilot AI requested a review from keithboone August 17, 2026 14:04
Co-authored-by: keithboone <36998841+keithboone@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants