Name		Name	Last commit message	Last commit date
parent directory ..
.mvn/wrapper		.mvn/wrapper
Gradle_Check		Gradle_Check
Gradle_Check_Stage_QuickFeedback/pluginData		Gradle_Check_Stage_QuickFeedback/pluginData
Gradle_Check_Stage_QuickFeedbackLinuxOnly/pluginData		Gradle_Check_Stage_QuickFeedbackLinuxOnly/pluginData
Gradle_Check_Stage_ReadyforMerge/pluginData		Gradle_Check_Stage_ReadyforMerge/pluginData
Gradle_Check_Stage_ReadyforNightly/pluginData		Gradle_Check_Stage_ReadyforNightly/pluginData
Gradle_Check_Stage_ReadyforRelease/pluginData		Gradle_Check_Stage_ReadyforRelease/pluginData
Gradle_Promotion		Gradle_Promotion
Gradle_Util		Gradle_Util
Gradle_Util_Performance		Gradle_Util_Performance
common		common
README.md		README.md
mvnw		mvnw
mvnw.cmd		mvnw.cmd
pom.xml		pom.xml
subprojects.json		subprojects.json
test-class-data.json		test-class-data.json

README.md

CI Pipeline Configuration

Currently there are three subprojects in the Gradle TeamCity project which are configured here
- Check - Main build pipeline (Configured with TeamCity's Kotlin DSL)
- Promotion - Jobs to publish Gradle versions (Configured directly in the TeamCity UI and stored in XML)
- Util - Manually triggered utility jobs (Configured directly in the TeamCity UI and stored in XML)
To configure/modify the Check pipeline
- The configurations are stored in the .teamcity folder and tests in the .teamcityTest folder
- Open the .teamcity folder in IDEA
- Revert the changes made by IDEA to Gradle_Check_dsl.iml
- The main pipeline configuration can be found and modified in CIBuildModel.kt
- After modifying, make sure that the configuration can be processed by running CIConfigIntegrationTests and mvn verify
- If you have ktlint errors, you can automatically fix them by running mvn com.github.gantsign.maven:ktlint-maven-plugin:1.1.1:format
- Commit and push the changes