Google Git
Sign in
chromium / external / github.com / gradle / gradle / 9de6baccce98692141dfb45047831805bb932cc9 / . / .teamcity
tree: 88dd1f35d7ccb093e7bc2dcd3ee7bfb642715f67 [path history] [tgz]
  1. .mvn/
  2. common/
  3. Gradle_Check/
  4. Gradle_Check_Stage_QuickFeedback/
  5. Gradle_Check_Stage_QuickFeedbackLinuxOnly/
  6. Gradle_Check_Stage_ReadyforMerge/
  7. Gradle_Check_Stage_ReadyforNightly/
  8. Gradle_Check_Stage_ReadyforRelease/
  9. Gradle_Promotion/
  10. Gradle_Util/
  11. Gradle_Util_Performance/
  12. mvnw
  13. mvnw.cmd
  14. pom.xml
  15. README.md
  16. subprojects.json
  17. test-class-data.json
.teamcity/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