- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 42 for Want (0.29 sec)
-
.teamcity/src/main/kotlin/util/RerunFlakyTest.kt
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 08:17:56 GMT 2024 - 4.6K bytes - Viewed (0) -
.teamcity/README.md
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 test these changes without affecting `master`/`release` pipeline. Here are the instructions.
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) -
build-logic/integration-testing/src/main/kotlin/gradlebuild/integrationtests/shared-configuration.kt
} internal fun Project.configureIde(testType: TestType) { val prefix = testType.prefix val sourceSet = the<SourceSetContainer>().getByName("${prefix}Test") // We apply lazy as we don't want to depend on the order plugins.withType<IdeaPlugin> { with(model) { module { testSources.from(sourceSet.java.srcDirs, sourceSet.the<GroovySourceDirectorySet>().srcDirs)
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Mon Feb 12 13:19:06 GMT 2024 - 11.7K bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleUserManualPlugin.java
task.attributes(attributes); }); // Avoid overlapping outputs by copying exactly what we want from other intermediate tasks TaskProvider<Sync> userguide = tasks.register("userguide", Sync.class, task -> { task.setGroup("documentation");
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Mar 01 05:46:51 GMT 2024 - 17.7K 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) -
architecture/standards/0001-use-architectural-decision-records.md
## Decision The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as the *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K 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) -
.cm/estimated_time_to_review.cm
# for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # 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
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/summary_table_platforms.cm
# for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # 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
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/platform_labels.cm
# for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # 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
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)