# https://github.com/tensorflow/tensorflow/actions/workflows/release-branch-cherrypick.yml
# and click "Run Workflow." Leave "Use Workflow From" set to "master", then
# input the branch name and paste the cherry-pick commit and click Run. A PR
# will be created.

name: Release Branch Cherrypick
on:
  workflow_dispatch:
    inputs:
      # We use this instead of the "run on branch" argument because GitHub looks

        buildType(PublishNightlySnapshotFromQuickFeedbackStepPromote(branch))
        buildType(PublishBranchSnapshotFromQuickFeedback)
        buildType(PublishMilestone(branch))

        if (branch.isMaster) {
            buildType(StartReleaseCycle)
            buildType(StartReleaseCycleTest)
        } else {
            buildType(PublishReleaseCandidate(branch))

        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",

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

name: Set nightly branch to master HEAD

permissions: {}

jobs:
  master-to-nightly:
    if: github.repository == 'tensorflow/tensorflow' # Don't do this in forks
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
    - uses: zofrex/mirror-branch@0be56f4c8077a288a635a491b306ba0bb1c810e6 # v1.0.4
      name: Set nightly branch to master HEAD
      with:

    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: "/"

import util.UtilPerformanceProject
import util.UtilProject
import java.io.File

class GradleBuildToolRootProject(
    branch: VersionedSettingsBranch,
) : Project({
        val model =
            CIBuildModel(
                projectId = "Check",
                branch = branch,
                buildScanTags = listOf("Check"),
                subprojects = JsonBasedGradleSubprojectProvider(File("./subprojects.json")),

# 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.

[gh-build]: https://github.com/apache/maven/actions/workflows/maven.yml?query=branch%3Amaster
[gh-build-4.0]: https://github.com/apache/maven/actions/workflows/maven.yml?query=branch%3Amaven-4.0.x
[gh-build-3.10]: https://github.com/apache/maven/actions/workflows/maven.yml?query=branch%3Amaven-3.10.x
[gh-build-3.9]: https://github.com/apache/maven/actions/workflows/maven.yml?query=branch%3Amaven-3.9.x
[maven-home]: https://maven.apache.org/