* </dl>
 *
 * <ul>
 * <li>the unreleased <b>major</b>, M+1.0.0 on the `master` branch</li>
 * <li>the unreleased <b>minor</b>,  M.N.0 on the `M.x` (x is literal) branch</li>
 * <li>the unreleased <b>bugfix</b>, M.N.c (c &gt; 0) on the `M.N` branch</li>
 * <li>the unreleased <b>maintenance</b>, M-1.d.e ( d &gt; 0, e &gt; 0) on the `(M-1).d` branch</li>
 * </ul>

        cleanup {
            history(days = 180)
        }

        this.init()
    }
}

class PublishFinalRelease(
    branch: VersionedSettingsBranch,
) : PublishRelease(
        promotedBranch = branch.branchName,
        prepTask = "prepFinalRelease",
        promoteTask = branch.promoteFinalReleaseTaskName(),
        requiredConfirmationCode = "final",
        init = {
            id(FINAL_RELEASE_BUILD_CONFIGURATION_ID)

    logrotate:
      daysToKeep: 30
      numToKeep: 500
      artifactDaysToKeep: 7
    parameters:
      - string:
          name: branch_specifier
          default: "refs/heads/%BRANCH%"
          description: "the Git branch specifier to build (<branchName>, <tagName>, <commitId>, etc.)\n"
    scm:
      - git:
          name: origin
          # master node jenkins user ~/.ssh

tag-template: maven-$RESOLVED_VERSION

# Override replacers to strip backport branch prefixes and handle JIRA links
replacers:
  # Strip backport branch prefixes like [maven-4.0.x], [maven-3.x], etc.
  - search: '/^\[maven-[\d\.x-]+\]\s*-?\s*/g'
    replace: ''
  # Convert JIRA ticket references to links (but not maven branch prefixes)
  - search: '/\[([A-Z]+)-(\d+)\]\s*-?\s*/g'

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+platform-support-windows
    display-name: "elastic / elasticsearch # %BRANCH% - windows compatibility"
    description: "Elasticsearch %BRANCH% Windows compatibility testing.\n"
    project-type: matrix
    node: master
    # Use a hard-coded workspace directory to avoid hitting file path limits with auto-generated workspace path

                    If change was made on the `release` branch but hasn't yet been published to the baseline version, update the baseline version:
                    <span class="btn btn-info" role="button">Update baseline</span>
                  </summary>
                  <div class="well">
                    Sometimes, the change was made on the `release` branch but hasn't yet been published to the baseline version.

      - uses: actions/checkout@v5
        name: Checkout PR for own repo
        if: env.HAS_SECRETS == 'true'
        with:
          # To be able to commit it needs to fetch the head of the branch, not the
          # merge commit
          ref: ${{ github.head_ref }}
          # And it needs the full history to be able to compute diffs
          fetch-depth: 0

```sh
$ cd minio
$ git remote add upstream https://github.com/minio/minio
$ git fetch upstream
$ git merge upstream/master
...
```

### Create your feature branch

Before making code changes, make sure you create a separate branch for these changes

```
git checkout -b my-new-feature
```

### Test MinIO server changes

After your code changes, make sure

---
jjbb-template: periodic-trigger-lgc.yml
vars:
  - periodic-job: elastic+elasticsearch+%BRANCH%+periodic+platform-support
  - lgc-job: elastic+elasticsearch+%BRANCH%+intake

- view:
    name: "Elasticsearch %BRANCH%"
    view-type: list
    regex: '^elastic[-+]elasticsearch\+%BRANCH%\+((?!multijob).)*$'
- view:
    name: "Elasticsearch Pull Requests"
    view-type: list