Often folks start learning the semantics and forget the concept<\/p>\n
The same goes with learning Jenkins, so here’s the ‘concept’:<\/p>\n
There used to be so many steps to deploy a product (ask someone who has been in a release manager kind of role)<\/p>\n
All that time was wasted on useless mis-management, trying to merge code properly which should have been done anyway in the first place<\/p>\n
Plus the time to do all these repetitive tasks day in day out<\/p>\n
A few ‘God gifted’ members of the software community started working to solve this back in 2004<\/p>\n
After lot’s of hard work, acquisitions and court trails, today we know that project as ‘Jenkins’ with over 1000 contributors<\/p>\n
Working towards the goal of making the deployment of software easier, the corner stone of DevOps<\/p>\n
A quick introduction to ‘how’ Jenkins solves this problem is in this article:<\/p>\n
#QsDaily #Automation #DevOps #Jenkins<\/p>\n