Search code examples
continuous-integrationteamcityetlautosys

TeamCity : How to define build and deployment steps for ETL and Autosys components


I am working on continuous integration project to auto build and deploy ETL workflow and Autosys jil file to target environment. We are using Perforce P4 for source code repository and Nexus for artefacts repository. Both ETL and Autosys applications are hosted on linux server.

- Developers extract workflow in the form of xml using Repository Manager from Informatica and check-in to source repository in Perforce.
- Developers extract jil file of Autosys job and check-in to source repository in Perforce.

Requirement:

As part of CI process, when developers check-in their code to source repository build process should get triggered and create artefacts of checked-in code and copy to artefacts repository.

Deployment process should get automatically trigger when it find any new artefacts and deploy artefact to target environment.

I would highly appreciate if someone helps me to know:

  • build and deployment steps
  • requirement of manifest file

  • Solution

  • Regarding build/deployment steps its nothing more than: open build configuration->build steps create new step in e.g. following way:

    Runner type: command line step name: that_one_from_autosys working directory: %system.autosys.home% command executable: run_autosys_.bat