# policy, and support documentation.

name: Scorecard supply-chain security
on:
  # For Branch-Protection check. Only the default branch is supported. See
  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
  branch_protection_rule:
  # To guarantee Maintained check is occasionally updated. See
  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained

import jetbrains.buildServer.configs.kotlin.triggers.schedule
import vcsroots.gradlePromotionBranches

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

for publication.

This document outlines getting in new features after a new branch has been cut and the process for getting a PR
merged in before and after the first public release.

# Feature Freeze

One week before a release, the release branch goes into a state of code freeze. At this point only critical release

import jetbrains.buildServer.configs.kotlin.triggers.schedule
import model.StageName
import vcsroots.gradlePromotionBranches

class PublishNightlyDocumentation(branch: VersionedSettingsBranch) : PublishGradleDistributionFullBuild(
    promotedBranch = branch.branchName,
    promoteTask = "publishBranchDocs",
    triggerName = StageName.PULL_REQUEST_FEEDBACK.uuid,
    vcsRootId = gradlePromotionBranches
) {
    init {

import common.VersionedSettingsBranch
import vcsroots.gradlePromotionBranches

class PublishNightlySnapshotFromQuickFeedback(branch: VersionedSettingsBranch) : PublishGradleDistributionFullBuild(
    promotedBranch = branch.branchName,
    prepTask = branch.prepNightlyTaskName(),
    promoteTask = branch.promoteNightlyTaskName(),
    triggerName = "QuickFeedback",
    vcsRootId = gradlePromotionBranches
) {
    init {

                                def ITS_BRANCH = env.CHANGE_BRANCH != null ? env.CHANGE_BRANCH :  env.BRANCH_NAME;
                                try {
                                  echo "Checkout ITs from branch: ${ITS_BRANCH}"
                                  checkout([$class: 'GitSCM',
                                          branches: [[name: ITS_BRANCH]],

        }

        cleanup {
            history(days = 180)
        }

        this.init()
    }
}

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

 *
 * When merging `releaseX` branch into `master`, we should only use the release note from the `master` branch,
 * but sometimes changes on release notes.md was brought to master and merged unnoticed,
 * e.g https://github.com/gradle/gradle/pull/25825
 *
 * This script is to check if there is any merge commit that brings changes from release branch to master.
 * Usage: groovy CheckBadMerge.groovy <commit1> <commit2> ...

    if [[ "$(git rev-parse --abbrev-ref HEAD)" == "pull_branch" ]]; then
        # TF's CI runs 'git fetch origin "pull/PR#/merge:pull_branch"'
        # To get the as-merged branch during the CI tests
        git diff --diff-filter ACMRT --name-only pull_branch^ pull_branch > $BATS_FILE_TMPDIR/changed_files
    else
        # If the branch is not present, then diff against origin/master

                        def WORK_DIR=pwd()
                        def ITS_BRANCH = env.CHANGE_BRANCH != null ? env.CHANGE_BRANCH :  env.BRANCH_NAME;
                        try {
                          echo "Checkout ITs from branch: ${ITS_BRANCH}"
                          checkout([$class: 'GitSCM',
                                  branches: [[name: ITS_BRANCH]],