Skip to content

NGSOK-1746 PySpark sdist without hadoop-cloud, and a correct CI guard - #62

Merged
giggsoff merged 2 commits into
develop/4.4.0/4.2.0.2from
feature/NGSOK-1746-followup
Sep 4, 2026
Merged

giggsoff merged 2 commits into
develop/4.4.0/4.2.0.2from
feature/NGSOK-1746-followup

Conversation

@giggsoff

@giggsoff giggsoff commented Sep 3, 2026 •

Copy link
Copy Markdown
Collaborator

Two follow-ups to #43. The Maven deploy moves from the release event to the tag push, because packages published by a release-triggered run are linked to that release and listed among its assets — 32 org.apache.spark.spark-*_2.13 (maven) lines on 4.2.0.2-4.4.0-0, where arenadata/kyuubi, which deploys from a tag-push workflow, has none. The PySpark sdist moves to the plain hadoop3 leg so it stops shipping the AWS SDK bundle, and the CI guard that reported a still-running run as missing is fixed here, since it landed on the branch after #43 merged.

Also attaches the CycloneDX SBOM and its grype vulnerability report to the release, in a job of its own.

@giggsoff
giggsoff marked this pull request as draft September 3, 2026 06:43
@giggsoff giggsoff self-assigned this Sep 3, 2026
@giggsoff
giggsoff force-pushed the feature/NGSOK-1746-followup branch 2 times, most recently from 99662e4 to 19f2d3d Compare September 3, 2026 07:09
@giggsoff
giggsoff requested review from Asmoday and werzerbb September 4, 2026 09:00
@giggsoff
giggsoff marked this pull request as ready for review September 4, 2026 09:00
…-cloud

Packages published by a release-triggered run are linked to that release and
listed among its assets, so the Maven deploy moves to the tag push and the
release event keeps only the tarballs. The PySpark sdist moves to the plain
hadoop3 leg, since it packages the assembly jars and was shipping the AWS SDK
bundle, and the CI guard now reports a still-running run as running rather
than as missing. A new job attaches the CycloneDX SBOM and its grype
vulnerability report, as the kyuubi release workflow does.
The install lifecycle passes through pre-integration-test, so setup-integration-test-env.sh ran with the default image tag N/A and rebuilt the images through minikube's Docker daemon, which is containerd-backed and fails to boot buildkit. Point that step at the images already built and loaded so the script skips the rebuild.
@giggsoff
giggsoff force-pushed the feature/NGSOK-1746-followup branch from 945649f to b5ea645 Compare September 4, 2026 09:04
@giggsoff
giggsoff merged commit 1684ae3 into develop/4.4.0/4.2.0.2 Sep 4, 2026
22 checks passed
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