- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 16 for correctly (0.26 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/src/main/kotlin/common/VersionedSettingsBranch.kt
* should be enabled, i.e. when new commits are pushed to this branch, should a ReadyForNightly job * be triggered automatically? * * Currently, we only enable VCS trigger for `master`/`release`/`releaseNx` branches. */ val enableVcsTriggers: Boolean = nightlyPromotionTriggerHour != null companion object { private
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 3.4K bytes - Viewed (0) -
architecture/build-state-model.md
The build state is managed by the `BuildState` class. An instance is created for each build in the build definition, once per build execution and is discarded at the end of the execution. The build state also includes what is currently called the "Gradle state". The Gradle state is being merged into the build state and is mostly empty. ### Project state
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/README.md
## How the configuration works We use Kotlin portable DSL to store TeamCity configuration, which means you can easily create a new pipeline based on a specific branch. Currently, we have two pipelines: `master` and `release`, but you can easily create and test another isolated pipeline from any branch. We'll explain everything via an example. Let's say you make some changes on your branch `myTestBranch`
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/buildquality/src/main/kotlin/gradlebuild.verify-build-environment.gradle.kts
tasks.register("verifyIsProductionBuildEnvironment") { doLast { val systemCharset = Charset.defaultCharset().name() assert(systemCharset == "UTF-8") { "Platform encoding must be UTF-8. Is currently $systemCharset. Set -Dfile.encoding=UTF-8" } }
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Feb 01 09:48:30 GMT 2021 - 941 bytes - Viewed (0) -
Development.md
2. That should be it. The suggestion will be displayed in the "Try" section. ### Remove generic suggestions For some scenarios, it doesn't make sense to display all the generic suggestions we currently have. E.g. `--stacktrace` for a compilation error is not helpful. To influence the generic suggestions Gradle displays, the NonGradleCause interface was introduced.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 06 22:54:40 GMT 2024 - 1.8K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/AbstractBuildScanInfoCollectingService.kt
import org.gradle.tooling.events.task.TaskOperationResult import java.io.Serializable /** * A BuildService which monitors a few tasks (in both build-logic and main build) and collects information for build scan. * It's currently implemented by two use cases: * 1. Collect cache misses for compilation tasks and publish a `CACHE_MISS` tag for build scan.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Aug 11 07:01:27 GMT 2022 - 2.3K bytes - Viewed (0) -
.github/CODEOWNERS
.cm/ @tresat .github/workflows/gitstream.yml @tresat # IDE Experience team platforms/ide/ @gradle/bt-ide-experience # Eventually be moved to the core platform. # Currently heavily developed by the bt-ide-experience team. platforms/ide/problems/ @gradle/bt-ide-experience platforms/ide/ide-native/ @gradle/bt-ide-experience @gradle/bt-native-maintainers # Documentation
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 15:52:09 GMT 2024 - 9.8K bytes - Viewed (0) -
architecture/standards/0005-introduce-core-ui-architecture-module.md
The Gradle core platform provides many services to the Gradle platforms and builds logic. One such group of services allows logic to interact with the build user, to provide diagnostics, progress information, prompt for questions, and so on. Currently, these services are part of the core platform runtime architecture module. A downside of this structure is that it is difficult to do focused work on the Gradle UI. ## Decision
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Mar 04 23:19:15 GMT 2024 - 1.3K bytes - Viewed (0) -
build-logic/build-update-utils/src/main/kotlin/gradlebuild/buildutils/tasks/CheckContributorsInReleaseNotes.kt
You can run `GITHUB_TOKEN=<YourGitHubToken> ./gradlew docs:updateContributorsInReleaseNotes --milestone <milestone>` to update the release notes with correct contributors automatically. """.trimIndent() ) } }
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon May 16 05:03:11 GMT 2022 - 1.9K bytes - Viewed (0)