Jenkins is NOT continuous integration

Jenkins is NOT continuous integration

HomeValentina (Cupać) JemuovićJenkins is NOT continuous integration
Jenkins is NOT continuous integration
ChannelPublish DateThumbnail & View CountDownload Video
Channel AvatarPublish Date not found Thumbnail
0 Views
Many teams believe this: we have Jenkins, so we practice continuous integration (CI).

It's wrong.

If a team has Jenkins, but they are not merging code into the master branch on a daily basis, and if they do not have adequate test automation, then they are not practicing continuous integration.

To summarize: Jenkins does not equal CI.

THE REFERENCES:
– Continuous integration (Fowler): https://martinfowler.com/articles/continuousIntegration.html
– Minimum CD: https://minimumcd.org/minimumcd

FOLLOW:
– Newsletter: https://journal.optivem.com
– LinkedIn: https://www.linkedin.com/in/valentina…
– Twitter: https://twitter.com/valentinacupac
– GitHub: https://github.com/valentinacupac
-Instagram: https://www.instagram.com/valentinacupac
– YouTube: https://youtube.com/@valentinacupac
– Discord: https://discord.com/invite/e2vEY8krrC

#jenkins #cicd #continuousintegration

Please take the opportunity to connect and share this video with your friends and family if you find it useful.