- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 270 for Builds (0.1 sec)
-
platforms/documentation/docs/src/docs/userguide/authoring-builds/tutorial/partr3_multi_project_builds.adoc
Composite builds allow you to: - Extract your build logic from your project build (and re-use it among subprojects) - Combine builds that are usually developed independently (such as a plugin and an application) - Decompose a large build into smaller, more isolated chunks == Step 4. Add build to the Build Let's add a plugin to our build. First, create a new directory called `license-plugin` in the `gradle` directory:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 17:16:27 UTC 2024 - 13.9K bytes - Viewed (0) -
platforms/core-configuration/configuration-cache/src/integTest/groovy/org/gradle/internal/cc/impl/ConfigurationCacheBuildTreeStructureIntegrationTest.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Jun 08 11:29:25 UTC 2024 - 13.6K bytes - Viewed (0) -
platforms/documentation/docs/src/main/resources/header.html
</ul> </li> <li><a class="nav-dropdown" data-toggle="collapse" href="#authoring-multi-project-builds" aria-expanded="false" aria-controls="authoring-multi-project-builds">Structuring Builds</a> <ul id="authoring-multi-project-builds"> <li><a href="../userguide/multi_project_builds.html">Structuring Projects with Gradle</a></li>
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat May 25 05:15:02 UTC 2024 - 35.6K bytes - Viewed (0) -
subprojects/composite-builds/src/integTest/groovy/org/gradle/integtests/composite/CompositeBuildPluginDevelopmentIntegrationTest.groovy
when: execute(buildA, "tasks", ["--include-build", "../pluginBuild"]) then: executed ":pluginBuild:jar" outputContains("taskFromPluginBuild") } def "does not substitute plugin from same build into root build"() { disableProblemsApiCheck() buildA.settingsFile << """ include "a", "b" """
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Mar 26 13:37:31 UTC 2024 - 23.1K bytes - Viewed (0) -
Makefile
@echo "Verify resolving inconsistent versions build with race" @(env bash $(PWD)/buildscripts/resolve-right-versions.sh) build-debugging: @(env bash $(PWD)/docs/debugging/build.sh) build: checks build-debugging ## builds minio to $(PWD) @echo "Building minio binary to './minio'" @CGO_ENABLED=0 go build -tags kqueue -trimpath --ldflags "$(LDFLAGS)" -o $(PWD)/minio 1>/dev/null hotfix-vars:
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Mon Jun 10 17:41:02 UTC 2024 - 10.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/other/test_kit.adoc
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 05:36:09 UTC 2024 - 15.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/gradle_daemon.adoc
TIP: To understand the Daemon's impact on your builds, you can profile your build with `--profile`. In between builds, the Daemon waits idly for the next build. As a result, your machine only loads Gradle into memory once for multiple builds instead of once per build. This is a significant performance optimization. === Runtime Code Optimizations
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Jun 07 12:43:14 UTC 2024 - 13.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/build-cache/build_cache.adoc
[[sec:build_cache_enable]] == Enable the Build Cache By default, the build cache is not enabled. You can enable the build cache in a couple of ways: Run with `--build-cache` on the command-line:: Gradle will use the build cache for this build only. Put `org.gradle.caching=true` in your `gradle.properties`:: Gradle will try to reuse outputs from previous builds for all builds, unless explicitly disabled with `--no-build-cache`.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed May 15 11:30:10 UTC 2024 - 26.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/performance.adoc
Shared build caches can decrease build times for both CI and developer builds. For more information about the build cache, check out the <<build_cache_use_cases.adoc#use_cases_cache,build cache documentation>>. === Visualize the build cache with build scans Build scans can help you investigate build cache effectiveness. In the performance screen, the _"Build cache"_ tab shows you statistics about:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Feb 23 03:39:56 UTC 2024 - 33.4K bytes - Viewed (0) -
subprojects/diagnostics/src/integTest/groovy/org/gradle/api/tasks/diagnostics/ProjectReportTaskIntegrationTest.groovy
when: run ":projects" then: outputContains """ Root project 'my-root-project' No sub-projects Included builds: +--- Included build ':another' \\--- Included build ':third'""" } def "included builds are only shown in the context of the root project"() { given: createDirs("p1", "p1/p11", "another")
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Jun 03 16:02:32 UTC 2024 - 10K bytes - Viewed (0)