Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 25 for Want (0.13 sec)

  1. .teamcity/src/main/kotlin/projects/CheckProject.kt

                description = "The extra gradle parameters you want to pass to this build, e.g. `-PrerunAllTests` or `--no-build-cache`"
            )
            text(
                "reverse.dep.*.additional.gradle.parameters",
                "",
                display = ParameterDisplay.NORMAL,
                allowEmpty = true,
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 03:34:53 GMT 2024
    - 3.1K bytes
    - Viewed (0)
  2. .cm/add_usual_expert.cm

    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.4K bytes
    - Viewed (0)
  3. .cm/complex_changes.cm

    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  4. .cm/lacks_tests.cm

    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    # Each automation is independent of the others.  Every time one of the `on` conditions match for
    # this PR, this automations will have its `if` checked to run.  In a way, the `on` conditions
    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)
  5. .github/workflows/contributor-pr.yml

    name: Contributor CI Build
    
    on:
      push:
        branches:
          - master
      pull_request:
        branches:
          - master
    
    concurrency:
      # On master/release, we don't want any jobs cancelled so the sha is used to name the group
      # On PR branches, we cancel the job if new commits are pushed
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 09:13:16 GMT 2024
    - 3.9K bytes
    - Viewed (0)
  6. .teamcity/src/main/kotlin/util/RerunFlakyTest.kt

            text(
                testTaskParameterName,
                ":core:embeddedIntegTest",
                display = ParameterDisplay.PROMPT,
                allowEmpty = false,
                description = "The test task you want to run"
            )
            text(
                testNameParameterName,
                """org.gradle.api.tasks.CachedTaskExecutionIntegrationTest.outputs*are*correctly*loaded*from*cache""",
    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)
  7. .teamcity/README.md

    We'll explain everything via an example. Let's say you make some changes on your branch `myTestBranch`
    (we highly recommend to name this branch without prefix and hyphen (`-`) because it's used to generate build type ID) and want to
    test these changes without affecting `master`/`release` pipeline. Here are the instructions.
    
    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)
  8. build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleUserManualPlugin.java

                task.attributes(attributes);
            });
    
            // Avoid overlapping outputs by copying exactly what we want from other intermediate tasks
            TaskProvider<Sync> userguide = tasks.register("userguide", Sync.class, task -> {
                task.setGroup("documentation");
    Java
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Fri Mar 01 05:46:51 GMT 2024
    - 17.7K bytes
    - Viewed (0)
  9. .teamcity/src/main/kotlin/configurations/PerformanceTest.kt

                    "performance.baselines",
                    type.defaultBaselines,
                    display = ParameterDisplay.PROMPT,
                    allowEmpty = true,
                    description = "The baselines you want to run performance tests against. Empty means default baseline."
                )
                param("performance.channel", performanceTestBuildSpec.channel())
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 08:17:56 GMT 2024
    - 5.3K bytes
    - Viewed (0)
  10. architecture/standards/0001-use-architectural-decision-records.md

    ## Decision
    
    The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.
    
    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.
    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)
Back to top