test-patch has the ability to support multiple build tools and personalities. Build tool and personality plug-ins have some extra hooks to do source and object maintenance at key points. Every build tool plug-in must have one line in order to be recognized:
add_build_tool <pluginname>
This variable determines where the build tool's command (as returned by pluginname_executor) should actually execute. It should be one of three values:
If pluginname_modules_worker is given a test type that is not supported by the build system, set UNSUPPORTED_TEST=true. If it is supported, set UNSUPPORTED_TEST=false.
For example, the gradle build tool does not have a standard way to execute checkstyle. So when checkstyle is requested, gradle_modules_worker sets UNSUPPORTED_TEST to true and returns out of the routine.
Note: In a personality, pluginname can be arbitrary.
This should be an echo of the file that controls the build system. This is used for module determination. If the build system wishes to disable module determination, it should echo with no args.
This should be an echo of how to run the build tool, any extra arguments, etc.
Input is the branch and the test being run. This should call modules_workers with the generic parts to run that test on the build system. For example, if it is convention to use 'test' to trigger 'unit' tests, then modules_workers should be called with 'test' appended onto its normal parameters.
Default method to determine how to enqueue modules for processing. Note that personalities may override this function. Requires two arguments: repo status and test desired. For example, in a maven build, values may be 'branch' and 'mvninstall'.
Default method to determine which tests to trigger. Note that personalities may override this function. Requires a single argument: the file in which the tests exist.
Executed prior to any other above functions except for pluginname_usage. This is useful for parsing the arguments passed from the user and setting up the execution environment.
After argument parsing and prior to any other work, the initialize step allows a plug-in to do any precursor work, set internal defaults, etc.
This functions allows the plugin to (re-)order the modules (e.g. based on the output of the maven dependency plugin). When called CHANGED_MODULES[@] already contains all changed modules. It must be altered to have an effect.
This functions should filter all lines relevant to this test from the logfile. It is called in preparation for the calcdiffs function. The test plug-in name should be in the (test) part of the function name.
Some build tools (e.g., maven) use custom output for certain types of compilations (e.g., java). This allows for custom log file difference calculation used to determine the before and after views.
To affect the various docker command lines, one can use helper functions:
docker build command line:
docker run command line:
If the build tool requires extra settings on the docker run command line (more than environment variables) those options should be added into an array called ${DOCKER_EXTRAARGS[@]}. This is particularly useful for things like mounting volumes for repository caches.
**WARNING**: Be aware that directories that do not exist MAY be created by root by Docker itself under certain conditions. It is HIGHLY recommend that [`pluginname_initialize`](#pluginname\_initialize) be used to create the necessary directories prior to use in the `docker run` command.
test-patch always passes -noinput to Ant. This forces ant to be non-interactive.
In Docker mode, the ${HOME}/.ivy2 directory is shared amongst all invocations.
autoconf requires make to be enabled. autoreconf is always used to rebuild the configure script.
autoconf will always run configure with prefix set to a directory in the patch processing directory. To configure other flags, set the AUTCONF_CONF_FLAGS environment variable.
By default, cmake will create a 'build' directory and perform all work there. This may be changed either on the command line or via a personality setting. cmake requires make to be enabled.
The gradle plug-in always rebuilds the gradlew file and uses gradlew as the method to execute commands.
In Docker mode, the ${HOME}/.gradle directory is shared amongst all invocations.
No notes.
test-patch always passes –batch-mode to maven to force it into non-interactive mode. Additionally, some tests will also force -fae in order to get all of messages/errors during that mode. Some tests are executed with -DskipTests. Additional arguments should be handled via the personality.
Under many common configurations, maven (as of 3.3.3 and lower) may not properly handle being executed by multiple processes simultaneously, especially given that some tests require the mvn install command to be used.
To assist, test-patch supports a --mvn-custom-repos option to set the -Dmaven.repo.local value to a per-instance repository directory keyed to the project and branch being used for the test. If the --jenkins flag is also passed, the instance will be tied to the Jenkins ${EXECUTOR_NUMBER} value. Otherwise, the instance value will be randomly generated via ${RANDOM}. If the repository has not been used in 30 days, it will be automatically deleted when any test run for that project (regardless of branch!).
By default, test-patch uses ${HOME}/yetus-m2 as the base directory to store these custom maven repositories. That location may be changed via the --mvn-custom-repos-dir option.
The location of the settings.xml may be changed via the --mvn-settings option.
In Docker mode, ${HOME}/.m2 is shared amongst all invocations. If --mvn-custom-repos is used, all of --mvn-custom-repos-dir is shared with all invocations. The per-instance directory will be calculated and configured after Docker has launched.
By default, test-patch will pass -Ptest-patch to Maven. This will allow you to configure special actions that should only happen when running underneath test-patch.
Maven will test eclipse and site if maven is being used as the build tool and appropriate files trigger them.
Maven will trigger add a maven install test when the maven_add_install function has been used and the related tests are required. Plug-ins that need to run maven before MUST call it as part of their respective initialize functions, otherwise maven may fail unexpectedly. All Apache Yetus provided plug-ins that require maven will trigger the maven install functionality.