- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 22 for Down (0.16 sec)
-
.cm/summary_table.cm
# You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit automations: summary_table: if: - {{ is.requested or not pr.author_is_org_member }} - {{ author.using_gitstream or not pr.author_is_org_member }}
Plain Text - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 6.5K bytes - Viewed (0) -
.teamcity/src/test/kotlin/CIConfigIntegrationTests.kt
File(it, "src/integTest").exists() && it.name != "distributions-integ-tests" && // distributions:integTest is part of Build Distributions it.name != "soak" // soak tests have their own test category } assertFalse(projectFoldersWithFunctionalTests.isEmpty()) projectFoldersWithFunctionalTests.forEach {
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Jan 02 10:00:06 GMT 2024 - 13.3K bytes - Viewed (0) -
.cm/summary_table_platforms.cm
# You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit - comment_added automations: summary_table_platforms: if: - {{ ('summary_table_platforms' | isEnabledAutomation(pr)) }} run:
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
# You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit - comment_added automations: # If someone adds a TODO, remind them about it by requesting removal includes_todos: if:
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) -
architecture/standards/0001-use-architectural-decision-records.md
* To explain *rejected solutions*, for now, and future development, in case they are proposed again. ADRs can be written by any team. Like code, they should be reviewed by any other relevant teams. The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together. ### Format The format for ADR should follow this template: ```markdown # ADR-000X - Title ## Date 20YY-MM-DD
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) -
architecture/standards/0004-use-a-platform-architecture.md
An architecture module is responsible for providing a coherent set of features and: - Provides a set of APIs and services for use from outside the module. - Has a private implementation. - Is owned by a single team. A team may own multiple architecture modules. The modules are arranged into several different "Gradle platforms". A Gradle platform is a logical distribution that provides support for a specific kind of automation.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Feb 25 22:19:29 GMT 2024 - 4.5K bytes - Viewed (0) -
architecture/platforms.md
### Documentation Provides cross-cutting Gradle documentation and samples, along with the infrastructure to write, test, publish and host the documentation. ## Structure Each platform and module has its own source directory under [platforms/](../platforms). In these source directories, you will find the Gradle projects that make up the platform or module.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 5.4K bytes - Viewed (0) -
.cm/code_experts.cm
# You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit - comment_added automations: # Also post a comment that lists the best experts for the files that were modified. comment_experts: if:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.3K bytes - Viewed (0) -
.cm/javadoc_on_new_files.cm
# You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit - comment_added automations: javadoc_on_new_files: # Triggered for new Java files that lack Javadoc content. if:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.8K bytes - Viewed (0) -
architecture/runtimes.md
Not every module contributes to every runtime. The core-runtime module defines each runtime: - The target JVM for the runtime. Each runtime has its own JVM compatibility constraints. - Some base services that are available to code hosted by the runtime. This varies by runtime.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.3K bytes - Viewed (0)