- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for Days (0.13 sec)
-
.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) -
.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/src/main/kotlin/promotion/PublishRelease.kt
display = ParameterDisplay.PROMPT, allowEmpty = true ) } cleanup { history(days = 180) } this.init() } } class PublishFinalRelease(branch: VersionedSettingsBranch) : PublishRelease( promotedBranch = branch.branchName, prepTask = "prepFinalRelease",
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 3.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)