- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 210 for branch (0.17 sec)
-
.teamcity/src/main/kotlin/promotion/PublishNightlySnapshot.kt
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 {
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 2.6K bytes - Viewed (1) -
.teamcity/src/main/kotlin/promotion/PublishRelease.kt
} 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")
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 3.5K bytes - Viewed (0) -
.github/workflows/CheckBadMerge.groovy
* * 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> ...
Groovy - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 19 10:35:44 GMT 2023 - 6.5K bytes - Viewed (0) -
ci/official/utilities/code_check_changed_files.bats
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
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Jan 10 19:39:41 GMT 2024 - 4K bytes - Viewed (0) -
docs/hotfixes.md
``` λ git checkout RELEASE.2021-04-22T15-44-28Z ``` Create a branch and proceed to push the branch **upstream** > (upstream here points to ******@****.***:minio/minio.git) ``` λ git branch -m RELEASE.2021-04-22T15-44-28Z.hotfix λ git push -u upstream RELEASE.2021-04-22T15-44-28Z.hotfix ``` Pick the relevant commit-id say for example commit-id from the master branch ``` commit 4f3317effea38c203c358af9cb5ce3c0e4173976
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 21:36:02 GMT 2024 - 5K bytes - Viewed (0) -
.teamcity/README.md
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
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Mar 06 23:02:25 GMT 2024 - 4K bytes - Viewed (0) -
.teamcity/src/main/kotlin/promotion/PromotionProject.kt
buildType(PublishNightlySnapshotFromQuickFeedbackStepPromote(branch)) buildType(PublishBranchSnapshotFromQuickFeedback) buildType(PublishMilestone(branch)) if (branch.isMaster) { buildType(StartReleaseCycle) buildType(StartReleaseCycleTest) } else { buildType(PublishReleaseCandidate(branch)) buildType(PublishFinalRelease(branch)) }
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Feb 29 04:36:37 GMT 2024 - 2.2K bytes - Viewed (0) -
.teamcity/src/main/kotlin/promotion/PublishNightlySnapshotFromQuickFeedbackStepCheckReady.kt
package promotion import common.VersionedSettingsBranch import vcsroots.gradlePromotionBranches class PublishNightlySnapshotFromQuickFeedbackStepCheckReady(branch: VersionedSettingsBranch) : BasePublishGradleDistribution( promotedBranch = branch.branchName, prepTask = branch.prepNightlyTaskName(), triggerName = "QuickFeedback", vcsRootId = gradlePromotionBranches, cleanCheckout = false ) { init {
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Jul 25 21:00:40 GMT 2022 - 1.2K bytes - Viewed (0) -
.teamcity/src/main/kotlin/promotion/PublishBranchSnapshotFromQuickFeedback.kt
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 1.9K bytes - Viewed (0) -
dbflute.xml
<property name="mydbflute.dir" value="${basedir}/mydbflute" /> <property name="target.dir" value="${basedir}/target" /> <property name="branch.name" value="fess-14.13" /> <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" />
XML - Registered: Mon May 06 08:04:11 GMT 2024 - Last Modified: Thu Apr 04 02:03:51 GMT 2024 - 1000 bytes - Viewed (0)