Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for command (6.07 sec)

  1. architecture/README.md

    ## Gradle runtimes
    
    Gradle is also made up of several different processes that work together to "run the build", such as the Gradle daemon and the `gradlew` command.
    
    Each process, or "runtime", applies different constraints to the code that runs in that process.
    For example, each process has different supported JVMs and a different set of services available for dependency injection.
    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)
  2. .github/workflows/codeql-analysis.yml

        - name: Cleanup Gradle Daemons
          run: ./gradlew --stop
          if: ${{ matrix.language == 'java' }}
    
        # ℹī¸ Command-line programs to run using the OS shell.
        # 📚 https://git.io/JvXDl
    
        # ✏ī¸ If the Autobuild fails above, remove it and uncomment the following three lines
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 09:13:16 GMT 2024
    - 4K bytes
    - Viewed (0)
  3. architecture/runtimes.md

    - 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)
  4. CONTRIBUTING.md

    This may help you better understand and contribute to Gradle.
    
    ### Debugging Gradle
    
    You can debug Gradle by adding `-Dorg.gradle.debug=true` to the command-line. Gradle will wait for you to attach a debugger at `localhost:5005` by default.
    
    If you made changes to build logic in the `build-logic` included build, you can run its tests by executing `./gradlew :build-logic:check`.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sat May 04 07:43:02 GMT 2024
    - 15.6K bytes
    - Viewed (0)
  5. .github/workflows/check-bad-merge.yml

            run: |
              cat output.txt
              OUTPUT=$(cat output.txt)
              echo "OUTPUT<<EOF" >> $GITHUB_ENV
              echo "$OUTPUT" >> $GITHUB_ENV
              echo "EOF" >> $GITHUB_ENV
          - name: Comment on PR if check failed
            if: ${{ failure() }}
            uses: actions/github-script@v7
            with:
              github-token: ${{ secrets.GITHUB_TOKEN }}
              script: |
                const output = `
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 09:13:16 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  6. .teamcity/performance-tests-ci.json

        "testId" : "org.gradle.performance.regression.buildcache.TaskOutputCachingJavaPerformanceTest.clean assemble for abi change with local cache",
        "groups" : [ {
          "testProject" : "largeJavaMultiProject",
          "comment" : "We only test the multi-project here since for the monolithic project we would have no cache hits. This would mean we actually would test incremental compilation.",
          "coverage" : {
            "per_commit" : [ "linux" ]
    Json
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Mon May 06 09:01:23 GMT 2024
    - 35.5K bytes
    - Viewed (0)
Back to top