sudo useradd vagrant

set -e

. .ci/java-versions.properties
RUNTIME_JAVA_HOME=$HOME/.java/$ES_RUNTIME_JAVA
BUILD_JAVA_HOME=$HOME/.java/$ES_BUILD_JAVA

rm -Rfv $HOME/.gradle/init.d/ && mkdir -p $HOME/.gradle/init.d
cp -v .ci/init.gradle $HOME/.gradle/init.d

unset JAVA_HOME

if [ -f "/etc/os-release" ] ; then
    cat /etc/os-release
    . /etc/os-release
    if [[ "$ID" == "debian" || "$ID_LIKE" == "debian" ]] ; then

import org.codelibs.fess.entity.SearchRequestParams;
import org.codelibs.fess.mylasta.action.FessUserBean;
import org.codelibs.fess.rank.fusion.SearchResult.SearchResultBuilder;
import org.codelibs.fess.unit.UnitFessTestCase;
import org.codelibs.fess.util.QueryResponseList;
import org.dbflute.optional.OptionalThing;
import org.junit.jupiter.api.Test;

public class RankFusionProcessorTest extends UnitFessTestCase {

            JAVA15_HOME=$USERPROFILE\\.java\\openjdk15
            GRADLE_TASK=checkPart2
      - batch: |
          del /f /s /q %USERPROFILE%\.gradle\init.d\*.*
          mkdir %USERPROFILE%\.gradle\init.d
          copy .ci\init.gradle %USERPROFILE%\.gradle\init.d\
          (
            echo call %GRADLEW_BAT% --max-workers=4 -Dbwc.checkout.align=true %GRADLE_TASK% ^|^| exit /b 1

	baseTestCases := []TestSuiteCommon{
		// Init and run test on ErasureSD backend with signature v4.
		{serverType: "ErasureSD", signer: signerV4},
		// Init and run test on ErasureSD backend, with tls enabled.
		{serverType: "ErasureSD", signer: signerV4, secure: true},
		// Init and run test on Erasure backend.
		{serverType: "Erasure", signer: signerV4},
		// Init and run test on ErasureSet backend.

$env:JAVA_TOOL_OPTIONS=''

$ErrorActionPreference="Stop"
$gradleInit = "C:\Users\$env:username\.gradle\init.d\"
echo "Remove $gradleInit"
Remove-Item -Recurse -Force $gradleInit -ErrorAction Ignore
New-Item -ItemType directory -Path $gradleInit
echo "Copy .ci/init.gradle to $gradleInit"
Copy-Item .ci/init.gradle -Destination $gradleInit

[Environment]::SetEnvironmentVariable("JAVA_HOME", $null, "Machine")

            RUNTIME_JAVA_HOME=$USERPROFILE\\.java\\$ES_RUNTIME_JAVA
      - batch: |
          del /f /s /q %USERPROFILE%\.gradle\init.d\*.*
          mkdir %USERPROFILE%\.gradle\init.d
          copy .ci\init.gradle %USERPROFILE%\.gradle\init.d\
          (
             echo powershell.exe .\.ci\scripts\packaging-test.ps1 -GradleTasks destructiveDistroTest.%PACKAGING_TASK%   ^|^| exit /b 1

        // Initialize QueryFieldConfig
        QueryFieldConfig queryFieldConfig = new QueryFieldConfig();
        queryFieldConfig.init();
        ComponentUtil.register(queryFieldConfig, "queryFieldConfig");

        // Initialize QueryParser
        QueryParser queryParser = new QueryParser();
        queryParser.init();
        ComponentUtil.register(queryParser, "queryParser");

        // Initialize QueryProcessor

            RUNTIME_JAVA_HOME=$USERPROFILE\\.java\\$ES_RUNTIME_JAVA
      - batch: |
          del /f /s /q %USERPROFILE%\.gradle\init.d\*.*
          mkdir %USERPROFILE%\.gradle\init.d
          copy .ci\init.gradle %USERPROFILE%\.gradle\init.d\
          (
             echo powershell.exe .\.ci\scripts\packaging-test.ps1 -GradleTasks destructiveDistroTest.%PACKAGING_TASK%   ^|^| exit /b 1

- Fixed a bug where init containers may fail to start due to a temporary container runtime failure. ([#127212](https://github.com/kubernetes/kubernetes/pull/127212), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Node]

這種情況下，你就不用為此費心了。🤷

///

### 前置步驟策略範例 { #examples-of-previous-steps-strategies }

這會「高度取決於」你「部署系統」的方式，而且很可能與你如何啟動程式、處理重新啟動等有關。

以下是一些可能的做法：

- 在 Kubernetes 中使用一個「Init Container」，它會在你的應用容器之前先執行
- 一個 bash 腳本先跑前置步驟，然後再啟動你的應用
    - 你仍然需要有機制來啟動／重新啟動「那個」bash 腳本、偵測錯誤等

/// tip

我會在未來關於容器的章節提供更具體的範例：[容器中的 FastAPI - Docker](docker.md)。

///