Anis Elleuch <******@****.***> 1676280398 +0100

name: "Stale"
on:
  schedule:
  - cron: "0 2 * * *"

permissions:
  contents: read

jobs:
  stale:
    permissions:
      issues: write  # for actions/stale to close stale issues
      pull-requests: write  # for actions/stale to close stale PRs
    runs-on: ubuntu-latest
    env:
      ACTIONS_STEP_DEBUG: true
    steps:
    - name: Close Stale Issues
      uses: actions/stale@v9
      with:

    functionalTestBucketProvider: FunctionalTestBucketProvider,
    val testCoverage: TestCoverage,
    val stage: Stage,
) : Project({
        this.id(testCoverage.asId(model))
        this.name = testCoverage.asName()
    }) {
    val functionalTests: List<BaseGradleBuildType> = functionalTestBucketProvider.createFunctionalTestsFor(stage, testCoverage)

    init {
        functionalTests.forEach(this::buildType)
    }

MinIO is built ground up on the cloud-native premise. With features like erasure-coding, distributed and shared setup, it focuses only on storage and does it very well. While, it can be scaled by just replicating MinIO instances per tenant via an orchestration platform.

> In a cloud-native environment, scalability is not a function of the application but the orchestration platform.

        model: CIBuildModel,
        stage: Stage,
        testCoverage: TestCoverage,
        bucketIndex: Int,
    ): FunctionalTest =
        FunctionalTest(
            model,
            testCoverage.getBucketUuid(model, bucketIndex),
            getName(testCoverage),
            getDescription(testCoverage),
            testCoverage,
            stage,
            parallelizationMethod,

          # This workflow should touch no issues, so times are set to -1
          # (see actions/stale documentation for the behavior)
          days-before-issue-stale: -1
          stale-issue-label: stale
          stale-issue-message: >
            **BUG!** This issue should not be marked stale by the "stale" workflow.
            Please report it to @gradle/bt-support team
          days-before-issue-close: -1

package configurations

import common.Os
import common.buildScanTagParam
import common.getBuildScanCustomValueParam
import model.CIBuildModel
import model.Stage

class SanityCheck(
    model: CIBuildModel,
    stage: Stage,
) : OsAwareBaseGradleBuildType(os = Os.LINUX, stage = stage, init = {
        id(buildTypeId(model))
        name = "Sanity Check"
        description = "Static code analysis, checkstyle, release notes verification, etc."

Shared scheme

```
org.gradle[.<qualifier>].<feature-name>.<detail>
```

The optional qualifier defines the secondary aspects, if any.

For better ergonomics on the CLI, some properties can have supplementary command-line build option(s).
The name of the feature in the build option SHOULD be the same as in the property name.

Shared scheme for long-form build options:

```

import common.buildScanTagParam
import common.getBuildScanCustomValueParam
import common.setArtifactRules
import model.CIBuildModel
import model.Stage

class BuildDistributions(
    model: CIBuildModel,
    stage: Stage,
) : OsAwareBaseGradleBuildType(os = LINUX, stage = stage, init = {
        id("${model.projectId}_BuildDistributions")
        name = "Build Distributions"

import common.toCapitalized
import model.CIBuildModel
import model.Stage

class SmokeTests(
    model: CIBuildModel,
    stage: Stage,
    testJava: JvmCategory,
    id: String,
    task: String = "smokeTest",
    splitNumber: Int = 1,
    flakyTestStrategy: FlakyTestStrategy,
) : OsAwareBaseGradleBuildType(os = Os.LINUX, stage = stage, init = {