Introduction to Amazon Code Pipeline with Java part 7: the third party action user signup process
May 7, 2016 Leave a comment
Introduction
In the previous post we went through an overview of third party actions in Amazon CodePipeline. They are similar to custom plugins in other CI tools like TeamCity and Jenkins. However, their structure, architecture and deployment are very different. The third party action developer must be aware of the job agent and how it communicates with an Amazon CodePipeline endpoint to pull new jobs and process them in some way. The job agent is the connecting tissue between CodePipeline and your backend services. You can deploy multiple job agents for load balancing.
In this post we’ll continue looking at the communication flow between the third party action and CodePipeline.