We have reached the end of this DevOps assignment, to be honest it was quite interesting, some tasks were pretty easy, but others taught me a lot of new things. For instance, I already had a working Virtual Machine with Linux, 2FA in github and a bit of knowledge with apache. New things like cron jobs, setting up a LAMP stack and developing my own continuous integration system was really interesting.
There are existing frameworks and services that can replace most of this work, some of this are:
Jenkins: An open source CI/CD server that allows the automation of the different stages of a delivery pipeline.
Pros:
- It is open source and free
- Has a wide range of plugins
- Integrates and works with all major tools
- Has APIs that lets you tailor the amount of data that you fetch.
Cons:
- Unpredictable costs derived from the server
- Lack of governance
- Lack of analytics
[Source]
Bamboo: Atlassian’s CI/CD server solution that has many similar features to Jenkins.
Pros:
- Integrates with other Atlassian tools
- Great notification scheme
- Easy enterprise-grade administration
Cons:
- Doesn’t support forks
- Very limited basic license
TeamCity: a Java-based build management and continuous integration server from JetBrains.
Pros:
- Easy installation
- Cross-platform build support
- Supports build chains
Cons:
- Expensive
- Inter-branch merges trigger emails to unrelated committers
- Plugins don’t get updated often
[Source]
Continuous integration and automation of tests are some of the most important excise tasks needed to survive in this fast paced environment of developing, changes need to be built as fast as possible and errors should be detected and corrected as soon as possible, so having this is definitely a life saver, it is important to value this tasks and the people that perform them for the team.
Ubora 