Search Options

Results per page
Sort
Preferred Languages
Advance

Results 21 - 30 of 65 for We (0.14 sec)

  1. build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/BuildScanInfoCollectingServices.kt

     */
    fun <T : AbstractBuildScanInfoCollectingService> Project.registerBuildScanInfoCollectingService(
        /* the implementation class to collect information from task execution result */
        klass: Class<T>,
        /* which tasks we need to monitor? For example, cache-miss-monitor monitors `AbstractCompile` tasks */
        taskFilter: (Task) -> Boolean,
        /* pass the collected information in build-logic and main build to build scan */
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 03:34:53 GMT 2024
    - 3.2K bytes
    - Viewed (0)
  2. .cm/lacks_tests.cm

    # function as an implicit first `if` for every automation in the file.
    
    # You can define multiple automations in a .cm file, but each automation name should be unique
    # within the file.  We keep each automation (or very closely related group of automations) in
    # its own file.
    
    on:
      - pr_created
      - commit
      - comment_added
    
    automations:
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2.4K bytes
    - Viewed (0)
  3. build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/testcleanup/TestFilesCleanupService.kt

            if (isAnyTestTaskFailed(projectPath.get())) {
                prepareReportForCiPublishing(tmpTestFiles + reports)
            } else {
                prepareReportForCiPublishing(reports)
            }
        }
    
        // We count the test task containing flaky result as failed
        private
        fun containsFailedTest(testBinaryResultsDir: File): Boolean {
            var containingFailures = false
    
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Fri Jul 28 16:19:47 GMT 2023
    - 12.5K bytes
    - Viewed (0)
  4. build-logic/integration-testing/src/main/kotlin/gradlebuild/integrationtests/ide/AndroidStudioProvisioningPlugin.kt

                                else -> zipTree(singleFile)
                            }
                        }
                    ) {
                        eachFile {
                            // Remove top folder when unzipping, that way we get rid of Android Studio.app folder that can cause issues on Mac
                            // where MacOS would kill the Android Studio process right after start, issue: https://github.com/gradle/gradle-profiler/issues/469
    Plain Text
    - Registered: Wed Mar 27 11:36:08 GMT 2024
    - Last Modified: Fri Dec 22 13:46:27 GMT 2023
    - 5.4K bytes
    - Viewed (0)
  5. build-logic/build-update-utils/src/main/kotlin/gradlebuild/buildutils/tasks/AbstractCheckOrUpdateContributorsInReleaseNotes.kt

            val releaseNotesLines: List<String> = releaseNotes.asFile.get().readLines()
            val contributorSectionBeginIndex = releaseNotesLines.indexOfFirst { it.startsWith("We would like to thank the following community members for their contributions to this release of Gradle:") } + 1
    
            if (contributorSectionBeginIndex == 0) {
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Mon May 16 05:03:11 GMT 2022
    - 5.7K bytes
    - Viewed (0)
  6. build-logic/binary-compatibility/src/test/kotlin/gradlebuild/binarycompatibility/AbstractBinaryCompatibilityTest.kt

                            newClasspath.from(v2.configurations.named("runtimeClasspath"), v2Jar)
    
                            onlyModified.set(false)
                            failOnModification.set(false) // we rely on the rich report to fail
    
                            txtOutputFile.set(file("build/japi-report.txt"))
    
                            richReport {
    
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Mon Sep 25 13:49:37 GMT 2023
    - 16.4K bytes
    - Viewed (0)
  7. .teamcity/src/test/kotlin/PromotionProjectTests.kt

            assertEquals(expectedGradleParams, upload.gradleParams)
        }
    
        private fun setupModelFor(branchName: String): PromotionProject {
            // Set the project id here, so we can use methods on the DslContext
            DslContext.projectId = AbsoluteId("Gradle_${branchName.toCapitalized()}")
            DslContext.addParameters("Branch" to branchName)
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Tue Feb 13 14:18:23 GMT 2024
    - 13.4K bytes
    - Viewed (0)
  8. architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md

    - **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages.
    
    ## 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
    
    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)
  9. architecture/standards/0001-use-architectural-decision-records.md

    ## Consequences
    
    * X
    * Y
    * Z
    ```
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    * We start to use Architectural Decision Records
    * We use the proposed template from this ADR
    * We locate `.md` files in the folder `/architecture-standards`
    * We highly encourage usage of ADR to communicate decisions
    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)
  10. architecture/standards/0002-avoid-using-java-serialization.md

    ## Decision
    
    We do not use Java serialization.
    Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized.
    
    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
    
    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)
Back to top