Reenable smoke tester in Jenkins [LUCENE-10462]

[asfimport]

While preparing the 9.1 release, we found that the smoke tester failed because of some build changes (#11495). It would be great to catch these failures earlier, when the changes are actually made.

Apparently we used to have a smoke test check in Jenkins, but it was disabled when we moved to gradle. It would be great to update the script and reenable it.

As part of this we'd need to update the smoke tester for 'main', where there are still some failures.

---

Migrated from LUCENE-10462 by Julie Tibshirani (@jtibshirani), updated Mar 13 2022

[asfimport]

Uwe Schindler (@uschindler) (migrated from JIRA)

I can take care of this.

As I am not up to date with the release process in Gradle: what Gradle command should be executed before smoke tester is started?

If you give me few lines I will adapt them to Jenkins and it's env variables to invoke python and setting up workspace.

Uwe

[asfimport]

Uwe Schindler (@uschindler) (migrated from JIRA)

It would also be good to know if smoke tester can execute both 11 and 17 jdk versions, like the 8.x one with 8 and 11.

[asfimport]

Tomoko Uchida (@mocobeta) (migrated from JIRA)

Hi @uschindler, I believe the smoke tester script has not been so much changed from 8.x in terms of its interface (command-line arguments), although it now uses Gradle internally. There are lots of arguments; what preparation was done and what command was passed to them when we ran on 8.x? I think we can reenable it again on Jenkins by making small adjustments to the old commands.

As for java version, it takes --test-java17 option to run on the specified java 17 home. It runs on java 11 by default (we should change this on the main branch: #11499).

 

[asfimport]

Uwe Schindler (@uschindler) (migrated from JIRA)

In branch 8x, Jenkins starts an Ant target. It would be good to have an approved sequence of commands to build a release and invoke smoke tester on it. Unfortunately I don't know what exact Gradle task needs to be executed to build a release and where the target dir is located.

[asfimport]

Uwe Schindler (@uschindler) (migrated from JIRA)

BTW, sorry for being ignorant here. I have not followed the release process recently, so I have really no idea how to execute Gradle and smoke tester on 9.x branch.

For Lucene main branch I won't enable smoke tester on jenkins anyways, as there's no releases planned.

[asfimport]

Tomoko Uchida (@mocobeta) (migrated from JIRA)

In branch 8x, Jenkins starts an Ant target. It would be good to have an approved sequence of commands to build a release and invoke smoke tester on it. Unfortunately I don't know what exact Gradle task needs to be executed to build a release and where the target dir is located.

Sorry, I understand. I think it can be possible to identify the exact Gradle command sequence, but there is also a python script to assemble RC and GA releases.

Does it make sense to invoke dev-tools/scripts/buildAndPushRelease.py on Jenkins to prepare src/binary distributions, instead of executing manually configured Gradle commands? It cleans up the local cache and composes the correct Gradle command to assemble release modules.

To build unsigned releases and save them to the local filesystem, this command works for me.

RELEASES_PATH=/tmp/lucene-releases
sudo rm -rf $RELEASES_PATH
python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local $RELEASES_PATH --dev-mode

Then the smoketester can be started on the $RELEASES_PATH/lucene-x.x-x...

python3 -u dev-tools/scripts/smokeTestRelease.py --tmp-dir $TMP_WORKING_DIR --not-signed "file://${RELEASES_PATH}/`ls ${RELEASES_PATH} | head -1`"

To run on java 17, this should work.

python3 -u dev-tools/scripts/smokeTestRelease.py --tmp-dir $TMP_WORKING_DIR  --not-signed --test-java17  $JAVA17_HOME  "file://${RELEASES_PATH}/`ls ${RELEASES_PATH} | head -1`"

If signed releases are needed the options should be changed, however, I myself haven't tried to create signed releases.

[asfimport]

Uwe Schindler (@uschindler) (migrated from JIRA)

Ok, I will check this out later on rather evening. That's was really helpful.

This also helps to test the release script.

Jenkins can't easily sign releases, so we can't check this

[asfimport]

Uwe Schindler (@uschindler) (migrated from JIRA)

Sorry I was not able to take care on this on weekend. I will investiage maybe tomorrow!