- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for esbuild (0.16 sec)
-
architecture/build-state-model.md
### Build tree state "Build tree" is another name for the build definition. The "build tree state" holds the state for the entire build definition for a single build execution within a session. The build tree state is managed by the `BuildTreeState` class. An instance is created at the start of a build execution and discarded at the end of the execution. ### Build 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) -
architecture/README.md
See [Gradle runtimes](runtimes.md) for a list of these runtimes and more details. ## Build state model As Gradle executes, it acts on various pieces of the build definition, such as each project in the build. Gradle tracks the state of each piece and transitions each piece through its lifecycle as the build runs.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.4K bytes - Viewed (0) -
.github/workflows/contributor-pr.yml
cancel-in-progress: true env: # Set the DEVELOCITY_ACCESS_KEY so that Gradle Build Scans are generated DEVELOCITY_ACCESS_KEY: ${{ secrets.GRADLE_ENTERPRISE_ACCESS_KEY }} # Enable debug for the `gradle-build-action` cache operations GRADLE_BUILD_ACTION_CACHE_DEBUG_ENABLED: true permissions: {} jobs: build: name: "Compile All" permissions: contents: read runs-on: ubuntu-latest
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 3.9K bytes - Viewed (0) -
.github/workflows/codeql-analysis.yml
- name: Compile with Gradle with Build Scan if: ${{ matrix.language == 'java' && github.repository_owner == 'gradle' }} run: ./gradlew --no-configuration-cache --init-script .github/workflows/codeql-analysis.init.gradle -DcacheNode=us -S testClasses -Dhttp.keepAlive=false env: # Set the DEVELOCITY_ACCESS_KEY so that Gradle Build Scans are generated
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 4K bytes - Viewed (0) -
architecture/platforms.md
### Enterprise integration Provides cross-cutting integration with Gradle's commercial product. ### IDE integration Provides cross-cutting integration with IDEs and other tooling. ### Build infrastructure Provides build logic, libraries, test suites and infrastructure to support developing and releasing Gradle. ### Documentation
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) -
build-logic/cleanup/build.gradle.kts
plugins { id("gradlebuild.build-logic.kotlin-dsl-gradle-plugin") id("gradlebuild.build-logic.groovy-dsl-gradle-plugin") } description = "Provides a plugin that cleans up after executing tests" errorprone { disabledChecks.addAll( "CatchAndPrintStackTrace", // 1 occurrences "DefaultCharset", // 3 occurrences "JavaTimeDefaultTimeZone", // 1 occurrences "StringCaseLocaleUsage", // 2 occurrences ) }
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 26 09:46:00 GMT 2024 - 557 bytes - Viewed (0) -
architecture/runtimes.md
# Gradle runtimes Gradle is made up of the following processes that work together to "run the build": - Gradle daemon. This is the process that actually runs the build. It hosts build logic and coordinates the lifecycle of the build. It is a long-running daemon process. - CLI client. This is the `gradle` or `gradlew` command, and is responsible for locating, starting and interacting with the Gradle daemon, potentially downloading the Gradle distribution.
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)