TeamCity CI configs - plus links to one-touch Jenkins, GoCD, Concourse, TeamCity builds, API scripts & configs for most major CI systems: Azure DevOps, GitHub Actions, GitLab CI, BitBucket CI, Travis CI, Circle CI, AWS CodeBuild, GCP Cloud Build, AppVeyor, BuildKite, CodeShip, Drone.io, Semaphore CI, Shippable, Wercker...
TeamCity CI configurations, synchronized from my automated TeamCity cluster.
.teamcity/
- XML format live sync’dexports/
- JSON exports using API scripts in DevOps Bash tools repokotlin/
- Kotlin exports from UI.teamcity.vcs.oauth.json
- VCS connection to this repo via OAuth.teamcity.vcs.ssh.json
- VCS connection to this repo via SSH keyteamcity.sh - one-shot TeamCity cluster on Docker with automated agent authorization and VCS integration via API calls.
TeamCity on Docker - docker-compose.yml
TeamCity on Kubernetes configurations are here.
Kubernetes configs - extensive Kubernetes configurations, including TeamCity-on-Kubernetes & Jenkins-on-Kubernetes, plus advanced templates for most major kubernetes objects
Jenkinsfile
.concourse.yml
Templates - templates for many CI systems, code and configs eg. advanced Jenkinsfile & Jenkins Shared Library (Groovy), GitHub Actions, Travis CI, CircleCI, AWS CodeBuild, GCP Cloud Build, Makefile, Vagrantfile, Dockerfile, docker-compose.yml etc.
Advanced Nagios Plugins - 450+ production monitoring checks including for the Jenkins API
All my major GitHub repos contain fully working live configs for most major CI system out there.
See CI/CD notes in my public Knowledge Base for more details and comparisons between different CI/CD systems.
You can boot any of these CI and run the repo’s build with a single short one-word command using the scripts above.
Jenkinsfile
at the top of each repo.concourse.yml
at the top of each reposetup/gocd_config_repo.json
in each repo.teamcity.vcs.oauth.json
/ .teamcity.vcs.ssh.json
connection to this repoThe rest of my original source repos are
here.
Pre-built Docker images are available on my DockerHub.