In the directory each input artifact can be found inside a
<pipeline name>/<artifact name> folderby artifact name, e.g. if TeamCity CodePipeline action is a part of a pipeline named
TestPipeline and , has an input artifact named
MyApp and the previous action has uploaded some
application-bundle-1.0.zip zip file for this artifact name - then during the corresponding TeamCity build, the artifact will be available as
Similarly, after the build finishes, the files found under the artifact output folder specified by the
codepipeline.artifact.output.folder configuration parameter (which is
%system.teamcity.build.tempDir%/CodePipeline/output by default) are uploaded to the S3. Each artifact must be placed in a <pipeline_name>/represented by an
.zip archive, e.g. to publish some
application-bundle-2.0.zip some zip file as an artifact named
MyAppBuild for pipeline
TestPipeline, place it to
%codepipeline.artifact.output.folder%/TestPipeline/MyAppBuild/application-bundle-2.0.zip. You can achieve this, for example, by adding a Command line build step to your build which runs
cp <output_file_name> MyAppBuild.zip %codepipeline.artifact.output.folder%/<pipeline_name>/<artifact_name>/<output_file_name>.
It's recommended by the AWS to use one of zip, tar, tar.gz (tgz) archive types to package artifacts for the AWS CodePipeline.
Trigger poll interval
By default TeamCity build triggers are polled every 20 seconds. To change this period for the AWS CodePipeline Action build trigger, specify
codepipeline.poll.interval configuration parameter.