- Jenkinsfile: guez-only release pipeline; the prebuilt build image is
built from the in-tree Dockerfile (via new_docker_build.sh
--build-prebuilt-image) instead of a pre-pulled harbor image; the
builder runs inside the container with the workspace mounted at
/workspace; the post-publish cleanup stage was dropped so the DEBs
stay under ${WORKSPACE}/rpms/... (the documented output location)
- jenkins_builder_ubuntu26.sh: uses the in-tree rpmbuild/
make_rpm_ubuntu26.py instead of the outer-repo copy; same-file guard
on the packages-out copy (host output dir == make_rpm output dir)
- jenkins_publisher_ubuntu26.sh: uploads rpms/${PROJECT}/${OS_VERSION}/
directly - make_rpm_ubuntu26.py writes the DEBs there without a TDS
subfolder
- release-16-10-2026.sh: local driver adapted to the current
new_docker_build.sh interface (drops the no-longer-existing
--use-prebuilt-image option, builds the image on demand, outputs to
${WORKSPACE}/rpms/${PROJECT}/${OS_VERSION}/)
- make_rpm_ubuntu26.py: stage the new jenkins-ci-rme/ files (Jenkinsfile,
builder, publisher) into the build-pipeline DEB (release-16-10-2026.sh
was already listed)
Not copied (superseded): openSUSE builder/publisher, the old Dockerfile
recipes (replaced by the in-tree Dockerfile), Bitbucket notification
(jenkins_notifier.sh is not part of this project)
2.7 KiB
2.7 KiB
jenkins-ci-rme — release pipeline for the Qt6 validation-scope branch
In-tree copy of the Jenkins CI flow, adapted so the release pipeline depends only on files inside this source tree:
| File | Purpose |
|---|---|
Jenkinsfile |
Jenkins pipeline: prepare the prebuilt image (in-tree Dockerfile), run the builder inside the container, publish the DEBs to the artifact repo |
jenkins_builder_ubuntu26.sh |
Runs inside the build container: stages the workspace, runs the in-tree rpmbuild/make_rpm_ubuntu26.py, copies the DEBs to the packages-out mount |
jenkins_publisher_ubuntu26.sh |
Runs on the Jenkins agent: uploads the DEBs from ${WORKSPACE}/rpms/${PROJECT}/${OS_VERSION}/ to the internal artifact repository |
release-16-10-2026.sh |
Local driver: the same flow without Jenkins, through the in-tree new_docker_build.sh |
Not included (superseded)
jenkins_builder.sh/jenkins_publisher.sh— openSUSE/RPM flow, not used by this branch (DEB/Ubuntu 26.04 only)Dockerfile-15.1/Dockerfile-ubuntu26.04/Dockerfile-ubuntu26-qt6— old image recipes; the prebuilt build image is built from the in-treeDockerfile(one level up)jenkins_notifier.sh— Bitbucket build-status notification, not part of this project
Adaptations vs. the outer-repo copy
- Packaging uses the in-tree
rpmbuild/make_rpm_ubuntu26.py(was${WORKSPACE}/rpmbuildfrom the outer repo) - The prebuilt build image is built from the in-tree
Dockerfilevianew_docker_build.sh --build-prebuilt-image(was a pre-pulled harbor image) — build args stay innew_docker_build.sh(single source of truth) MIGRATE_PIPELINE_ROOTis no longer needed:new_docker_build.shderives it from its own location- DEB output path:
${WORKSPACE}/rpms/${PROJECT}/${OS_VERSION}/(Jenkins convention); the packages-out copy is skipped when that directory is the make_rpm output dir (same device:inode guard as innew_docker_build.sh) - Publisher uploads
${WORKSPACE}/rpms/${PROJECT}/${OS_VERSION}/directly —make_rpm_ubuntu26.pywrites the DEBs there without a TDS subfolder - The post-publish Cleanup stage was dropped: the DEBs are kept under
${WORKSPACE}/rpms/...(the documented output location)
Local run
cd qt6-migrated-legatus
bash ./jenkins-ci-rme/release-16-10-2026.sh
# DEBs: <pipeline-root>/rpms/guez/26.04/
Jenkins setup
The job SCM must be the outer pipeline repository (the Jenkinsfile lives in
the qt-migration-legatus submodule; point the job's script path at
qt-migration-legatus/qt6-after/qt6-migrated-legatus/jenkins-ci-rme/Jenkinsfile).
Required Jenkins credential: internal-repo-uploader (username/password for
the artifact repository).