- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for globals (0.14 sec)
-
architecture/build-state-model.md
build_tree --> build2 project3["root project"] build2 --> project3 project4["project"] build2 --> project4 ``` ### Build process state The "build process state" holds the global state of the build process and manages all the other state. The build process state also includes state that is tied to a particular Gradle user home directory.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun May 05 22:45:11 GMT 2024 - 3.4K bytes - Viewed (0) -
.teamcity/src/main/kotlin/promotion/SanityCheck.kt
steps { gradleWrapper { tasks = "tasks" gradleParams = "" param("org.jfrog.artifactory.selectedDeployableServer.defaultModuleVersionConfiguration", "GLOBAL") } } triggers { vcs { branchFilter = "" enabled = VersionedSettingsBranch.fromDslContext().enableVcsTriggers } } requirements {
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 977 bytes - Viewed (0) -
.teamcity/src/main/kotlin/promotion/StartReleaseCycle.kt
param("org.jfrog.artifactory.selectedDeployableServer.defaultModuleVersionConfiguration", "GLOBAL") } } dependencies { snapshot(RelativeId("Check_Stage_ReadyforNightly_Trigger")) { } } }
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 2.4K bytes - Viewed (1) -
architecture/standards/README.md
**Experimental!** We'd like to capture our architectural decisions about the build tool as [Architectural Decision Records (ADRs)](https://adr.github.io/). For now we just have this global repository of ADRs. If we see fit, we can break these out to per-platform ones, or keep a hybrid approach to having global and platform-specific ADSs. Our aim is to keep the process lightweight and approachable.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Feb 21 06:30:44 GMT 2024 - 546 bytes - Viewed (0)