- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 24 for have (0.16 sec)
-
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods. - **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL. - **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages. ## Decision
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2K bytes - Viewed (0) -
.cm/platform_labels.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Apr 22 15:32:31 GMT 2024 - 2.5K bytes - Viewed (0) -
.cm/misc_labels.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3K bytes - Viewed (0) -
.teamcity/src/main/kotlin/configurations/PerformanceTest.kt
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 08:17:56 GMT 2024 - 5.3K bytes - Viewed (0) -
.cm/summary_table_platforms.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
.cm/includes_todos.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.9K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy
On `master` branch, these two files are usually reset (cleaned up), unless you have special reasons not to do so. </div> </div> </p> """.stripIndent() ) return violation }
Groovy - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 10.4K bytes - Viewed (0) -
.teamcity/performance-tests-ci.json
"groups" : [ { "testProject" : "largeJavaMultiProject", "comment" : "We only test the multi-project here since for the monolithic project we would have no cache hits. This would mean we actually would test incremental compilation.", "coverage" : { "per_commit" : [ "linux" ] } } ] }, {
Json - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon May 06 09:01:23 GMT 2024 - 35.5K bytes - Viewed (0) -
architecture/standards/README.md
## Architecture Standards **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)