What is Jenkins | Jenkins Tutorial for Beginners | Jenkins Continuous Integration Tutorial | Edureka

Video is ready, Click Here to View ×


****** DevOps Training : ******
This DevOps Jenkins Tutorial on what is Jenkins ( Jenkins Tutorial Blog Series: ) will help you understand what is Continuous Integration and why it was introduced. This tutorial also explains how Jenkins achieves Continuous Integration in detail and includes a Hands-On session around Jenkins by the end of which you will learn how to compile a code that is present in GitHub, Review that code and Analyse the test cases present in the GitHub repository. The Hands-On session also explains how to create a build pipeline using Jenkins and how to add Jenkins Slaves.

The Hands-On session is performed on an Ubuntu-64bit machine in which Jenkins is installed.

To learn how Jenkins can be used to integrate multiple DevOps tools, watch the video titled ‘DevOps Tools’, by clicking this link:

For doubts & queries on DevOps, post the same on Edureka Community:…

41 Comments on “What is Jenkins | Jenkins Tutorial for Beginners | Jenkins Continuous Integration Tutorial | Edureka”

  1. Got a question on the topic? Please share it in the comment section below and our experts will answer it for you. For Edureka DevOps Training and Certification curriculum, Visit our Website: http://bit.ly/2O59dHy Use code "YOUTUBE20" to get Flat 20% off on this training.

  2. Hey Edureka/Sourabh
    I just have a basic doubt.. In the initial part of the video regarding continuous integration, you said that it will pull the changes and build up the code and gives the developer regarding the success/failure of the build.
    So here my doubt is what is meant by the build.. I mean on what basis does it build.. what is the success and failure of a build?
    Also I am asking you for another doubt before proceeding further..
    If the integration server is pulling up to build as soon a change is made, so that they will get to know the errors.. what errors do they get to know? Also practically it is not possible to test all the builds generated after every commit.. because testing of 1 build itself would take a lot of time. so then what about the bugs of Application?
    Next doesn't it create a confusion regarding which build was tested and it's changes ..

  3. hi i faced error when i build log : > C:Program FilesGitbingit.exe rev-parse –is-inside-work-tree # timeout=10

    Fetching changes from the remote Git repository.. how to fix build status is Failure

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.