Re: [PR] kie-issues#2405: 10.3.x+ stream: Re-write kie-tools release jobs to be local scripts invoked in Apache Jenkins and remove old ones. [incubator-kie-tools]

["Kusuma04-dev (via GitHub)" <gi...@apache.org>]

Kusuma04-dev commented on PR #4019:
URL: https://github.com/apache/incubator-kie-tools/pull/4019#issuecomment-5728809679

   Thanks @jomarko ,
   
   You don't need to run a full build. Complete build logs and testable artifacts are already available in the [kie-release-10.3/evidence](https://github.com/Kusuma04-dev/kie-release-10.3/tree/main/artifacts_kie_tools) repository for verification.
   
   Authorized users: Anyone can run local builds or dry-runs. Official releases are executed through Jenkins.
   
   Credentials: No credentials are needed for local RC builds or testing. Publishing credentials (NPM, VSCE, GPG, etc.) are pre-configured in Jenkins and used only for official releases.
   
   Output and upload location: For a local dry-run, the scripts generate artifacts under release-artifacts (in kie-tools) and the local .m2 repository (in kie). If the release is run through Jenkins, the generated artifacts are uploaded to Apache SVN dev and Nexus Staging for voting, and are published to public registries after approval.
   
   CI vs local execution: Official releases run on Jenkins, but the release scripts can also be executed locally.
   Dry-run commands:
   
   incubator-kie:
   
   ./script/release/release-all.sh --version 10.3.0 --tag 10.3.0-rc1 --skip-tests --dry-run
   
   incubator-kie-tools:
   ./scripts/release/release-all.sh 10.3.0 --rc --skip-build
   
   Repository isolation: Yes. The release scripts are self-contained within their respective repositories (incubator-kie and incubator-kie-tools).
   Build scope: Yes. Each script performs a clean production build of all modules in its repository for the specified release version and commit.


-- 
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: commits-unsubscribe@kie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org