[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.4724125.svg)](https://doi.org/10.5281/zenodo.4724125)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/1486/badge)](https://bestpractices.coreinfrastructure.org/projects/1486)
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/tensorflow/tensorflow/badge)](https://securityscorecards.dev/viewer/?uri=github.com/tensorflow/tensorflow)

Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions.
We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://go.dev/s/proposal-process).

For asking questions, see:

* [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts)

* [The Go Forum](https://forum.golangbridge.org/), a web-based forum

package projects

import configurations.PerformanceTest
import jetbrains.buildServer.configs.kotlin.Project
import model.CIBuildModel
import model.PerformanceTestBucketProvider
import model.PerformanceTestCoverage
import model.PerformanceTestProjectSpec
import model.Stage

abstract class PerformanceTestProject(
    model: CIBuildModel,
    val spec: PerformanceTestProjectSpec,
    val performanceTests: List<PerformanceTest>,
) : Project({

# with IDEs such as IntelliJ.


# Format snapshot / restore directories in server
1afe4b914301a23fa37c41c78185b7575a431cc4

# Format more snapshot / restore relate projects
559c4e6ef4f9173bbb59043bacd0ac36c7281040

# Format aggregations and related code (server and x-pack)

    description: "Testing of the Elasticsearch %BRANCH% branch platform support tests.\n"
    project-type: multijob
    node: master
    vault: []
    scm:
      - git:
          wipe-workspace: false
    builders:
      - multijob:
          name: Packaging tests
          projects:
            - name: elastic+elasticsearch+%BRANCH%+multijob+platform-support-darwin
              kill-phase-on: NEVER

    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:
            - name: elastic+elasticsearch+%BRANCH%+multijob+packaging-tests-unix
              kill-phase-on: NEVER

public class RepositoriesSetupPlugin implements Plugin<Project> {

    private static final Pattern LUCENE_SNAPSHOT_REGEX = Pattern.compile("\\w+-snapshot-([a-z0-9]+)");

    @Override
    public void apply(Project project) {
        configureRepositories(project);
    }

    /**
     * Adds repositories used by ES projects and dependencies
     */
    public static void configureRepositories(Project project) {

        setupRestResources([apiCore1, apiCore2, apiXpack], [coreTest], [xpackTest])
        // intentionally not adding tests to project, they will be copied over via the plugin
        // this tests that the test copy happens before the api copy since the api copy will only trigger if there are tests in the project

        when:
        def result = gradleRunner("copyRestApiSpecsTask").build()

        then:

package projects

import common.uuidPrefix
import configurations.OsAwareBaseGradleBuildType
import jetbrains.buildServer.configs.kotlin.DslContext
import jetbrains.buildServer.configs.kotlin.Project
import model.CIBuildModel
import model.SpecificBuild
import model.Stage

/**
 * Subproject under [StageProject] that groups smoke test build configurations.
 */
class SmokeTestProject(
    model: CIBuildModel,
    stage: Stage,

   questions. Those who are asked should be responsive and helpful.

 * **Step down considerately**: Members of every project come and go. When somebody leaves or
   disengages from the project, they should make it known and take the proper steps to ensure that
   others can pick up where they left off.