Started by timer1822d462c094d75d9989051b2a6cbc5c03ee89d04315d462c094d75d9989051b2a6cbc5c03ee89d04315refs/remotes/origin/maind462c094d75d9989051b2a6cbc5c03ee89d04315d462c094d75d9989051b2a6cbc5c03ee89d04315refs/remotes/origin/maind462c094d75d9989051b2a6cbc5c03ee89d04315d462c094d75d9989051b2a6cbc5c03ee89d04315refs/remotes/origin/mainhttps://gitbox.apache.org/repos/asf/lucene.git067217828testReportfalseJava: 64bit/hotspot/jdk-27-ea+32 -XX:-UseCompressedOops -XX:+UseSerialGC#182221993882265843Lucene-nightly-main-Linux #18221822falsefalse1822225954SUCCESS1785485702214https://jenkins.thetaphi.de/view/Lucene/job/Lucene-nightly-main-Linux/1822/- dev-tools/scripts/releaseWizard.yamld462c094d75d9989051b2a6cbc5c03ee89d043151785485400000https://jenkins.thetaphi.de/user/noreplynoreplynoreply@github.comEnsure that lucene docs are published after bulk upload (#16437)
The apache websites use svnpubsub to publish documentation loaded
to the central svn server. We've occasionally seen new lucene
documentation fail to be published due to the size of the change.
This adds a new step to the release wizard to make a trivial
change to Changes.html and add it as an svn change to force
publishing.
2026-07-31 09:10:00 +0100d462c094d75d9989051b2a6cbc5c03ee89d04315Ensure that lucene docs are published after bulk upload (#16437)editdev-tools/scripts/releaseWizard.yaml
githttps://jenkins.thetaphi.de/user/noreplynoreply