Continuous Integration stratedgy on AWS
I have been using a Jenkins to manage application life cycle like continuous integration, build, and deployment in hosted environments. Now that I am starting to explore AWS, I am wondering if the same approach would still be valid. I am looking to setup a build server (Jenkins) to manage all CI, build, and deployment jobs. These jobs should be either triggered automatically (CI), or with a single click (maybe a few params). I tried out Elastic Beanstalk and Heroku CLI, but they don't seem to have good tools for defining jobs.
Is Jenkins still a good choice for the cloud, if not, what are the alternatives.
I have been using a Jenkins to manage application life cycle like continuous integration, build, and deployment in hosted environments. Now that I am starting to explore AWS, I am wondering if the same approach would still be valid. I am looking to setup a build server (Jenkins) to manage all CI, build, and deployment jobs. These jobs should be either triggered automatically (CI), or with a single click (maybe a few params). I tried out Elastic Beanstalk and Heroku CLI, but they don't seem to have good tools for defining jobs.
Is Jenkins still a good choice for the cloud, if not, what are the alternatives.
No comments:
Post a Comment