Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for Status (0.23 sec)

  1. architecture/standards/0005-introduce-core-ui-architecture-module.md

    This ADR does not specify the owner of this new architecture module. However, as a separate module, it can be assigned ownership independently of the other core services.
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    - Introduce the module and move the services and their implementations.
    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)
  2. architecture/standards/0001-use-architectural-decision-records.md

    occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
    
    ## Status
    
    [PROPOSED, ACCEPTED, REJECTED, DEPRECATED, REPLACED]
    
    ## Consequences
    
    * X
    * Y
    * Z
    ```
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    * We start to use Architectural Decision Records
    * We use the proposed template from this ADR
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sat Mar 02 21:54:40 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  3. build-logic-commons/module-identity/src/main/kotlin/gradlebuild/identity/tasks/BuildReceipt.kt

                    " snapshot: ${snapshot.get()})"
            )
            if (BuildEnvironment.isCiServer) {
                lifecycle(
                    "##teamcity[buildStatus text='{build.status.text}, Promoted version ${version.get()}']"
                )
            }
        }
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Sat Sep 30 16:17:28 GMT 2023
    - 4.2K bytes
    - Viewed (0)
  4. architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md

    ## Decision
    
    We do not introduce new public API methods that include Groovy types in their signatures.
    Existing Groovy methods will not be removed immediately.
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    * If we would have used `Closure`, we must instead use `Action<T>`, `Spec<T>`, `Callable<T>`, or `Transformer<OUT, IN>`.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sun Mar 10 20:38:06 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  5. .teamcity/pluginData/Check/plugin-settings.xml

            <state type="buildUnpinned" enabled="false" />
          </states>
          <build-types enabled-for-all="false" enabled-for-subprojects="false">
            <build-type id="bt270451" />
          </build-types>
        </webhook>
        <webhook url="https://gradle-bot.grdev.net/teamcity" enabled="true" template="legacy-tailored-json">
          <states>
            <state type="buildAddedToQueue" enabled="false" />
    XML
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Tue May 18 02:15:16 GMT 2021
    - 2.2K bytes
    - Viewed (0)
  6. architecture/standards/0002-avoid-using-java-serialization.md

    For internal purposes, we use binary formats for their brevity.
    We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
    
    When sharing data with external tools, we use JSON.
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    * The configuration cache serialization infrastructure should be used for all serialization.
    * Existing usages of Serializer outside of this infrastructure should be migrated to use it.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu Feb 29 22:32:18 GMT 2024
    - 2.3K bytes
    - Viewed (0)
  7. architecture/standards/0004-use-a-platform-architecture.md

    #### Documentation
    
    Provides cross-cutting Gradle documentation and samples, along with the infrastructure to write, test, publish and host the documentation.
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    - Assign ownership of each architecture module to one team.
    - Assign each source file to one architecture module.
    - Align the source tree layout with this architecture.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sun Feb 25 22:19:29 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  8. build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/testcleanup/extension/TestFilesCleanupProjectState.kt

    import org.gradle.api.file.DirectoryProperty
    import org.gradle.api.provider.Property
    
    
    /**
     * Works with {@see TestFilesCleanupService} and {@see TestFilesCleanupServiceRootExtension}.
     * It collects states to be used in the build service for each project.
     */
    interface TestFilesCleanupProjectState : TestFileCleanUpExtension {
        val projectPath: Property<String>
        val projectBuildDir: DirectoryProperty
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Fri Mar 18 02:11:12 GMT 2022
    - 1K bytes
    - Viewed (0)
Back to top