Kusuma04-dev opened a new pull request, #4085:
URL: https://github.com/apache/incubator-kie-tools/pull/4085
Context
Follow-up to #4019 (release jobs as local scripts invoked in Apache
Jenkins). While running the 10.3.0 RC flow I found three gaps.
Changes
1. Source release now covers both repositories
* create-source-tarball.sh previously ran git archive on this repo only.
* It now builds apache-kie-<version>-incubating-sources.zip containing:
* incubator-kie/ and incubator-kie-tools/ (git archive)
* BUILD (build instructions, tool versions read from this repo)
* DISCLAIMER-WIP
* a merged LICENSE and NOTICE (incubator-kie's file plus the
third-party sections and paragraphs of incubator-kie-tools; paths prefixed per
repository)
* New options: --kie-git-ref and --kie-repo. Both default to this repo's
ref and the apache/incubator-kie repository.
* The script checks that the zip root contains exactly BUILD
DISCLAIMER-WIP LICENSE NOTICE incubator-kie incubator-kie-tools.
* release-all.sh release_source_tarball now delegates to this script
instead of duplicating the logic.
* README.md is updated accordingly.
2. Nexus staging repositories for the RC build
* Upstream 10.3+ artifacts (e.g. kogito-apps-bom) exist only in Apache
Nexus staging until they are promoted.
* New add-staging-repositories.js adds one or more repositories (and
plugin repositories) to a Maven settings file as an always-active profile. It
is idempotent, validates URLs (https only), and creates the file if it is
missing.
* New STAGING_REPOSITORIES parameter in
Jenkinsfile.103xplus.release-candidate, defaulting to the staging group.
buildUtils.groovy setupPnpm writes a separate settings file and passes it
through MAVEN_ARGS as --global-settings.
* A separate file is used because Maven honors only the first
--settings, and pnpm bootstrap already sets one. Putting the path in
.mvn/maven.config would break container image builds, because that file is
copied into the images.
3. Cross-filesystem Maven repository fix (release-all.sh)
* Container image packages build dist/tmp-m2 from the Maven local
repository with hard links (cp -al).
* When ~/.m2 is on a different filesystem from the workspace (as in CI),
this fails with Invalid cross-device link.
* New ensure_m2_on_workspace_filesystem (with same_filesystem) detects
this case. It seeds a repository in node_modules/.cache/m2-repository and
points Maven to it via MAVEN_OPTS. It runs before the container image step.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]