Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for silent (0.2 sec)

  1. build-logic/documentation/src/main/groovy/gradlebuild/docs/ReleaseNotesTransformer.java

        private void addTOC(Document document) {
            Element tocSection = document.body().select("section.topic").first().before("<section class='table-of-contents'/>").previousElementSibling();
            tocSection.append("<h2>Table Of Contents</h2>");
            Element toc = tocSection.append("<ul class='toc'/>").children().last();
    
            Elements h23elements = document.select("h2,h3");
            for (Element h23element: h23elements) {
    Java
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Thu Apr 25 04:49:56 GMT 2024
    - 7.7K bytes
    - Viewed (0)
  2. .teamcity/README.md

    # CI Pipeline Configuration
    
    ## Open & import the project
    
    In your IDEA, `File` - `Open`, select `.teamcity/pom.xml`, `import as project`, and you'll have a Maven project.
    
    ## Project structure
    
    Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project.
    
    There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.
    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)
  3. .teamcity/src/main/kotlin/util/RerunFlakyTest.kt

                JvmVersion.java11.major.toString(),
                display = ParameterDisplay.PROMPT,
                allowEmpty = false,
                description = "Java version to run the test with"
            )
            select(
                testJvmVendorParameter,
                JvmVendor.openjdk.name,
                display = ParameterDisplay.PROMPT,
                description = "Java vendor to run the test with",
    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)
  4. .github/workflows/gitstream.yml

    name: gitStream workflow automation
    run-name: |
      /:\ gitStream: PR #${{ fromJSON(fromJSON(github.event.inputs.client_payload)).pullRequestNumber }} from ${{ github.event.inputs.full_repository }}
    
    on:
      workflow_dispatch:
        inputs:
          client_payload:
            description: The Client payload
            required: true
          full_repository:
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 19 12:22:37 GMT 2024
    - 1.6K bytes
    - Viewed (0)
  5. architecture/platforms.md

    It is made up of 3 architecture modules:
    
    - **core-runtime**: Provides the runtimes or "containers" in which code runs. These runtimes include the Gradle client, the daemon and the worker processes. This is the base module on which all other architecture modules depend.
    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)
  6. architecture/runtimes.md

    - 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. 
    - Tooling API client. This a library that is embedded into applications, such as IDEs or CI agents, that allows them to act as a Gradle client.
    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)
Back to top