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

 */

package promotion

import common.VersionedSettingsBranch

class PublishNightlySnapshotFromQuickFeedbackStepUpload(
    branch: VersionedSettingsBranch,
) : BasePublishGradleDistribution(
        promotedBranch = branch.branchName,
        prepTask = branch.prepNightlyTaskName(),
        triggerName = "QuickFeedback",
    ) {
    init {
        id("Promotion_SnapshotFromQuickFeedbackStepUpload")

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

	<property name="mydbflute.dir" value="${basedir}/mydbflute" />
	<property name="target.dir" value="${basedir}/target" />
	<property name="branch.name" value="fess-15.4" />
	<property name="mydbflute.url" value="https://github.com/lastaflute/lastaflute-example-waterfront/archive/${branch.name}.zip" />

	<target name="mydbflute.check">
		<condition property="mydbflute.exists">
			<available file="${mydbflute.dir}" type="dir" />

 */

package promotion

import common.VersionedSettingsBranch

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

        }

        if (generateTriggers) {
            val enableTriggers = model.branch.isMainBranch || model.branch.isLegacyRelease
            if (stage.trigger == Trigger.EACH_COMMIT) {
                val effectiveTriggerBranches = mutableListOf(model.branch.branchName)

                if (model.branch.isMaster) {
                    effectiveTriggerBranches.add(PROVIDER_API_MIGRATION_BRANCH)

        private const val RELEASE_BRANCH = "release"

        private const val EXPERIMENTAL_BRANCH = "xperimental"

        // master branch of gradle/gradle-promote
        private const val GRADLE_PROMOTE_MASTER_VCS_ROOT_ID = "Gradle_GradlePromoteMaster"

        // experimental branch of gradle/gradle-promote
        private const val GRADLE_PROMOTE_EXPERIMENTAL_VCS_ROOT_ID = "Gradle_GradlePromoteExperimental"

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

          add-paths: .teamcity/jdks.yaml
          title: "Update jdks.yaml"
          body: "This PR updates JDK to the latest versions available in `.teamcity/jdks.yaml`."
          delete-branch: true
          branch: "devprod/update-jdks"
          branch-suffix: timestamp
          labels: |
            in:building-gradle
            @dev-productivity
      - name: Trigger a build
        uses: peter-evans/create-or-update-comment@v5

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