---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-geoip
    workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-geoip
    display-name: "elastic / elasticsearch # %BRANCH% - third party tests geoip"
    description: "Testing of the Elasticsearch %BRANCH% third party tests against GeoIP database service\n"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'

        val triggerName = this.triggerName

        params {
            text(
                "branch.qualifier",
                "%dep.${RelativeId("Check_Stage_${triggerName}_Trigger")}.teamcity.build.branch%",
                label = "Branch qualifier for the published distribution version",

---
- job:
    name: elastic+elasticsearch+%BRANCH%+periodic+packaging-tests
    display-name: "elastic / elasticsearch # %BRANCH% - packaging tests"
    description: "Testing of the Elasticsearch %BRANCH% branch packaging tests.\n"
    project-type: multijob
    node: master
    vault: []
    scm:
      - git:
          wipe-workspace: false
    builders:
      - multijob:
          name: Packaging tests
          projects:

based on a specific branch. Currently, we have two pipelines: `master` and `release`, but you can easily create
and test another isolated pipeline from any branch. 

We'll explain everything via an example. Let's say you make some changes on your branch `myTestBranch`
(we highly recommend to name this branch without prefix and hyphen (`-`) because it's used to generate build type ID) and want to

---
- job:
    name: elastic+elasticsearch+%BRANCH%+intake+multijob+update-last-good-commit
    display-name: "elastic / elasticsearch # %BRANCH% - update last good commit"
    description: Elasticsearch %BRANCH% branch update last good commit in build-stats.
    node: light
    properties: []
    builders:
      - shell: |
          #!/usr/local/bin/runbld --job-name elastic+elasticsearch+%BRANCH%+git+push

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-gcs
    workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-gcs
    display-name: "elastic / elasticsearch # %BRANCH% - third party tests gcs"
    description: "Testing of the Elasticsearch %BRANCH% third party tests against GCS\n"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'
          properties-content: |

    triggerRules = "+:root=${branch.vcsRootId()}:."
    branchFilter = "+:<default>"
}

class PublishNightlySnapshot(
    branch: VersionedSettingsBranch,
) : PublishGradleDistributionFullBuild(
        promotedBranch = branch.branchName,
        prepTask = branch.prepNightlyTaskName(),
        promoteTask = branch.promoteNightlyTaskName(),
        triggerName = "ReadyforNightly",
    ) {

  - package-ecosystem: "maven"
    directory: "/"
    schedule:
      interval: "daily"
    target-branch: "maven-4.0.x"
    labels:
      - "mvn40"
      - "dependencies"

  - package-ecosystem: "maven"
    directory: "/"
    schedule:
      interval: "daily"
    target-branch: "maven-3.9.x"
    labels:
      - "mvn3"
      - "dependencies"

  - package-ecosystem: "maven"
    directory: "/"

---
jjbb-template: generic-gradle-unix.yml
vars:
  - job-name: elastic+elasticsearch+%BRANCH%+intake+multijob+sanity-check
  - job-display-name: "elastic / elasticsearch # %BRANCH% - intake sanity check"
  - job-description: Elasticsearch %BRANCH% branch intake sanity check.

# computes a hash of a remote repo's tag state.
# Tag definitions can come from the .hgtags file stored in
# any head of any branch, and the server protocol does not
# expose the tags directly. However, the protocol does expose
# the hashes of all the branch heads, so we can use a hash of
# all those branch names and heads as a conservative snapshot
# of the entire remote repo state, and use that as the tag sum.