- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for days (0.3 sec)
-
.github/workflows/team-triage-stale.yml
days-before-issue-stale: 14 stale-issue-label: to-triage stale-issue-message: "" days-before-issue-close: -1 only-pr-labels: 'from:contributor' exempt-all-pr-milestones: true days-before-pr-stale: 14 stale-pr-label: to-triage stale-pr-message: ""
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 835 bytes - Viewed (0) -
.teamcity/src/main/kotlin/common/extensions.kt
/** * Define clean up rules for the project. * See https://www.jetbrains.com/help/teamcity/teamcity-data-clean-up.html#Clean-up+Rules * * @param historyDays days number of days to store build history . * @param artifactsDays number of days to store artifacts. In the stored history, artifacts older than this number will be cleaned up.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 10:49:15 GMT 2024 - 13K bytes - Viewed (0) -
.github/workflows/stale-pr.yml
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 1.7K bytes - Viewed (0) -
.teamcity/src/main/kotlin/model/CIBuildModel.kt
READY_FOR_NIGHTLY("Ready for Nightly", "Rerun tests in different environments / 3rd party components", "ReadyforNightly"), READY_FOR_RELEASE("Ready for Release", "Once a day: Rerun tests in more environments", "ReadyforRelease"), HISTORICAL_PERFORMANCE("Historical Performance", "Once a week: Run performance tests for multiple Gradle versions", "HistoricalPerformance"),
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 23 01:54:48 GMT 2024 - 20.9K bytes - Viewed (0) -
.teamcity/README.md
- At the popup window, click `Import Settings from VCS`. Wait a few seconds. - If the error says "Context Parameter 'Branch' missing", it's ok. Click into the error and add a context parameter `Branch` with value `myTestBranch`. Go back and it automatically reloads. - If there are any errors, read the error and fix your code.
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) -
.teamcity/performance-tests-ci.json
"coverage" : { "per_day" : [ "linux" ] } }, { "testProject" : "bigCppMulti", "coverage" : { "per_day" : [ "linux" ] } }, { "testProject" : "bigNative", "coverage" : { "per_day" : [ "linux" ] } }, { "testProject" : "mediumCppApp", "coverage" : { "per_day" : [ "linux" ] }
Json - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon May 06 09:01:23 GMT 2024 - 35.5K bytes - Viewed (0) -
CONTRIBUTING.md
* Keep commits self-contained. Avoid spreading a single change across multiple commits. A single commit should make sense in isolation. ### Testing changes After making changes, you can test your code in 2 ways: 1. Run tests. - Run `./gradlew :<subproject>:quickTest` where `<subproject>` is the name of the subproject you've changed. - For example: `./gradlew :launcher:quickTest`.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat May 04 07:43:02 GMT 2024 - 15.6K bytes - Viewed (0) -
.teamcity/src/main/kotlin/model/PerformanceTestBucketProvider.kt
val performanceTestTypes = if (performanceTestSpec.performanceTestType in setOf(PerformanceTestType.historical, PerformanceTestType.flakinessDetection)) { listOf(PerformanceTestType.per_commit, PerformanceTestType.per_day) } else { listOf(performanceTestSpec.performanceTestType) } return performanceTestConfigurations.flatMap { configuration -> configuration.groups .filter { group ->
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Feb 19 11:22:56 GMT 2024 - 15.3K bytes - Viewed (0)