Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for Times (0.41 sec)

  1. architecture/build-state-model.md

    ### Build session state
    
    A "build session" represents a single invocation of Gradle, for example when you run `gradlew build`.
    A session runs the build one or more times.
    For example, when continuous build is enabled, the session may run the build many times, but when it is disabled, the session will run the build once only.
    
    The build session state is managed by the `BuildSessionState` class.
    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)
  2. .teamcity/src/main/kotlin/util/RerunFlakyTest.kt

        val id = "Util_RerunFlakyTest${os.asName()}${arch.asName()}"
        name = "Rerun Flaky Test - ${os.asName()} ${arch.asName()}"
        description = "Allows you to rerun a selected flaky test 10 times"
        id(id)
        val testJvmVendorParameter = "testJavaVendor"
        val testJvmVersionParameter = "testJavaVersion"
        val testTaskParameterName = "testTask"
        val testNameParameterName = "testName"
    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)
  3. .teamcity/src/main/kotlin/model/FunctionalTestBucketGenerator.kt

            // splitIntoBuckets() method expects us to split large element into N elements,
            // but we want to have a single bucket with N batches.
            // As a workaround, we repeat the bucket N times, and deduplicate the result at the end
            val resultIncludingDuplicates = splitIntoBuckets(
                LinkedList(subProjectTestClassTimes),
                SubprojectTestClassTime::totalTime,
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu Feb 15 17:04:41 GMT 2024
    - 8.5K bytes
    - Viewed (0)
  4. architecture/standards/0001-use-architectural-decision-records.md

    The main logic with ADRs is to describe (architectural) decisions made:
    
    * To provide best practices and solutions we (as the *build tool* team) want to promote.
    * To avoid asking the same thing multiple times during code review.
    * To explain *rejected solutions*, for now, and future development, in case they are proposed again.
    
    ADRs can be written by any team.
    Like code, they should be reviewed by any other relevant teams.
    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)
  5. .teamcity/src/main/kotlin/configurations/FlakyTestQuarantine.kt

        id("${model.projectId}_FlakyQuarantine_${os.asName()}_${arch.asName()}")
        name = "Flaky Test Quarantine - ${os.asName()} ${arch.asName()}"
        description = "Run all flaky tests skipped multiple times"
    
        applyDefaultSettings(os = os, arch = arch, buildJvm = BuildToolBuildJvm, timeout = 180)
    
        val testsWithOs = model.stages.filter {
            it.stageName in listOf(
                StageName.QUICK_FEEDBACK_LINUX_ONLY,
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 08:17:56 GMT 2024
    - 3.4K bytes
    - Viewed (0)
Back to top