- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 11 for Team (0.17 sec)
-
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.ci-reporting.gradle.kts
* failing tasks only, to not use up unnecessary disk space on Team City. This also improves the performance of * artifact publishing by reducing the artifacts and packaging reports that consist of multiple files. * * Reducing the number of reports also makes it easier to find the important ones when analysing a failed build in * Team City. */
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Jul 11 06:57:51 UTC 2023 - 2K 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.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sun Feb 25 22:19:29 UTC 2024 - 4.5K bytes - Viewed (0) -
platforms/core-configuration/kotlin-dsl/doc/c4/lib/C4_Container.puml
' Primary elements: Containers within the software system in scope. ' Supporting elements: People and software systems directly connected to the containers. ' Intended audience: Technical people inside and outside of the software development team; including software architects, developers and operations/support staff. ' Colors ' ################################## !define CONTAINER_BG_COLOR #438DD5 ' Styling ' ##################################
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Aug 02 08:06:49 UTC 2023 - 1.5K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
* Review in Google Docs is not as simple as a PR code review in GitHub ## 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.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Mar 02 21:54:40 UTC 2024 - 2.8K bytes - Viewed (0) -
.github/PULL_REQUEST_TEMPLATE.md
- [ ] Check ["Allow edit from maintainers" option](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) in pull request so that additional changes can be pushed by Gradle team. - [ ] Provide integration tests (under `<subproject>/src/integTest`) to verify changes from a user perspective. - [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Feb 13 22:36:19 UTC 2024 - 1.7K bytes - Viewed (0) -
.github/CODEOWNERS
platforms/enterprise/ @gradle/bt-build-scan @gradle/dv-build-insights-team platforms/enterprise/enterprise/ @gradle/bt-build-scan @gradle/dv-testing-team @gradle/dv-build-insights-team @ldaley platforms/enterprise/enterprise-logging/ @gradle/bt-build-scan @gradle/dv-build-insights-team @gradle/dv-testing-team platforms/enterprise/enterprise-operations/ @gradle/bt-build-scan
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Jun 11 09:44:59 UTC 2024 - 10.1K bytes - Viewed (0) -
platforms/core-configuration/kotlin-dsl/doc/c4/lib/C4_Context.puml
' Supporting elements: People and software systems directly connected to the software system in scope. ' Intended audience: Everybody, both technical and non-technical people, inside and outside of the software development team. ' Colors ' ################################## !define PERSON_BG_COLOR #08427B !define EXTERNAL_PERSON_BG_COLOR #686868 !define SYSTEM_BG_COLOR #1168BD !define EXTERNAL_SYSTEM_BG_COLOR #999999 ' Styling
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Aug 02 08:06:49 UTC 2023 - 2.5K bytes - Viewed (0) -
architecture/README.md
This directory contains documentation that describes Gradle's architecture and how the various pieces fit together and work. ## Architecture decision records (ADRs) The Gradle team uses ADRs to record architectural decisions that the team has made. See [Architecture decisions records](standards) for the list of ADRs.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 02 06:42:46 UTC 2024 - 2.4K bytes - Viewed (0) -
build-logic/publishing/src/main/kotlin/gradlebuild.publish-defaults.gradle.kts
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Jun 06 11:35:58 UTC 2024 - 3.3K bytes - Viewed (0) -
build-logic-commons/basics/src/main/kotlin/gradlebuild/basics/BuildEnvironment.kt
val isCodeQl: Boolean by lazy { // This logic is kept here instead of `codeql-analysis.init.gradle` because that file will hopefully be removed in the future. // Removing that file is waiting on the GitHub team fixing an issue in Autobuilder logic. CODEQL_ENVIRONMENT_VARIABLES.any { it in System.getenv() } } val jvm = org.gradle.internal.jvm.Jvm.current() val javaVersion = JavaVersion.current()
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri May 17 16:58:31 UTC 2024 - 4.8K bytes - Viewed (0)