github-hooks: true
          status-context: elasticsearch-ci/packaging-tests-windows-sample
          cancel-builds-on-update: true
          # We've removed the no-jdk distribution on master as well
          black-list-target-branches:
            - master
            - 6.8
          excluded-regions:
            - ^docs/.*
          black-list-labels:
            - '>test-mute'
            - ':Delivery/Packaging'
    axes:

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
test these changes without affecting `master`/`release` pipeline. Here are the instructions.

# their dependencies. It's a rewritten version of the "smoke test", an older
# Python script that was very difficult to understand. See
# https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/pip_package/pip_smoke_test.py
@test "Pip package includes all required //tensorflow dependencies" {
  # grep patterns for packages whose dependencies can be ignored

                    If change was made on the `release` branch but hasn't yet been merged to `master`, merge `release` to `master`:
                    <span class="btn btn-info" role="button">Merge release to master</span>
                  </summary>
                  <div class="well">

          github-hooks: true
          status-context: elasticsearch-ci/packaging-tests-windows
          cancel-builds-on-update: true
          # We've removed the no-jdk distribution on master as well
          black-list-target-branches:
            - master
            - 6.8
          excluded-regions:
            - ^docs/.*
          white-list-labels:
            - ':Delivery/Packaging'
          black-list-labels:

# fips140.sum.

default:
	@echo nothing to make

# make v1.2.3.zip builds a v1.2.3.zip file
# from the current origin/master.
# copy and edit the 'go run' command by hand to use a different branch.
v%.zip:
	git fetch origin master
	go run ../../src/cmd/go/internal/fips140/mkzip.go v$*

# normally mkzip refuses to overwrite an existing zip file.
# make v1.2.3.rm removes the zip file and unpacked

            // Host is empty -> triggers master browser path
            URL anyUrlWithEmptyHost = new URL("file:/");
            when(locator.getURL()).thenReturn(anyUrlWithEmptyHost);
            // Simulate failure to find master browser (UnknownHost wrapped in CIFSException)
            when(locator.getAddress()).thenThrow(new CIFSException("no master", new UnknownHostException("MB")));

See here [1] on how to compile for your platform and here [2] how libraries
follow JLine's directory and filename conventions.

[1] https://github.com/jline/jline3/tree/master/native

- Liveness probe available at `/minio/health/live`
- Cluster probe available at `/minio/health/cluster`

Read more on how to use these endpoints in [MinIO healthcheck guide](https://github.com/minio/minio/blob/master/docs/metrics/healthcheck/README.md).

## Prometheus Probe

 * we run each branch on different hours.
 * master - 0:00
 * release - 1:00
 * release6x - 2:00
 * release7x - 3:00
 * ...
 * releaseNx - (N-4):00
 */
fun VersionedSettingsBranch.determineNightlyPromotionTriggerHour(): Int? {
    val oldReleasePattern = "release(\\d+)x".toRegex()
    return when (branchName) {
        "master" -> 0
        "release" -> 1
        else -> {