"Rerun tests in different environments / 3rd party components",
        "ReadyforNightly",
    ),
    READY_FOR_RELEASE("Ready for Release", "Once a day: Rerun tests in more environments", "ReadyforRelease"),
    WEEKLY_VALIDATION(
        "Weekly Validation",
        "Once a week: Run tests in even more environments but less often",
        "WeeklyValidation",
    ),
    HISTORICAL_PERFORMANCE(
        "Historical Performance",

        requirements {
            requiresNotSharedHost()
        }

    /*
     To avoid unnecessary rerun, what we do here is a bit complicated:

     1. Build a Gradle distribution with a fixed timestamp and hash it, but never use this distribution.

### Setup for OpenSearch Plugins

Run antrun:run to download plugins into the plugins directory:

    $ mvn antrun:run

### Run Fess

Run or debug org.codelibs.fess.FessBoot on your IDE, and then access http://localhost:8080/

### Build Package

Run the `package` goal and then the release file will be created in target/releases.

    $ mvn package

### Testing changes

After making changes, you can test your code in 2 ways:

#### Run tests

- Run `./gradlew :<subproject>:quickTest` where `<subproject>` is the name of the subproject you've changed. 
- For example: `./gradlew :launcher:quickTest`.

#### Install Gradle locally

 * in the Gradle build.
 *
 * Each project may require a set of "target runtimes" that it must be able to run on.
 * Each target runtime reflects a runtime environment where code is executed. For one
 * project to be able to run in a given runtime, all of its dependencies must also
 * support running in that runtime.
 *

        val result = run(":flaky-test-without-leftover:test").build()
        assertEquals(TaskOutcome.SUCCESS, result.task(":flaky-test-without-leftover:test")!!.outcome)

        assertArchivedFilesSeen("report-flaky-test-without-leftover-test.zip")
    }

    @Test
    fun `leftover files are archived when test fails`() {
        val result = run(
            ":failed-report-with-leftover:test",

* The [Gradle Tooling API client](https://docs.gradle.org/8.8/userguide/third_party_integration.html#embedding)
  * This requires a Java application, and thus runtime, to run the tooling API client

As indicated, each of those components require a Java runtime to run.

The recommended way of invoking Gradle is to use the Gradle Wrapper.

    - name: Install fess-parent
      run: |
        cd fess-parent
        mvn install -Dgpg.skip=true
    - name: Download Plugins with Maven
      run: mvn -B antrun:run --file pom.xml
    - name: Build with Maven
      run: mvn -B source:jar javadoc:jar package --file pom.xml -Dparallel=classes -DthreadCount=4 -DforkCount=1C -DreuseForks=true
    - name: Run Fess
      run: bash src/test/resources/before_script.sh

mvn rpm:rpm             # Build .rpm package
mvn jdeb:jdeb           # Build .deb package
```

### Testing
```bash
mvn test                                    # Run unit tests (*Test.java)
mvn test -Dtest=ClassName                   # Run single unit test

# To install fess jar for plugin dependency resolution:
# Change pom.xml <packaging>war</packaging> to <packaging>jar</packaging> first

                .map(String::trim)
                .filter(s -> !s.isEmpty())
                .collect(Collectors.toList());
        }

        for (String commit : commits) {
            run("git", "checkout", commit, "--quiet", "--detach");
            String wrapperVersion = readWrapperVersion();
            System.out.println("Commit " + commit + " wrapper: " + wrapperVersion);