A free video tutorial from TetraNoodle Team
REAL KNOWLEDGE. REAL EXPERIENCE. REAL VALUE.
4.1 instructor rating • 72 courses • 156,543 students
Learn more from the full courseDevOps: CI/CD with Jenkins pipelines, Maven, Gradle
Build continuous integration, continuous delivery and DevOps pipelines with Java, Gradle, Maven, Artifactory & Sqitch.
03:27:28 of on-demand video • Updated February 2019
- You will get introduced to continuous integration (CI) and learn what it is all about.
- Learn why continuous integration is important (especially in fast paced agile environment)
- In any real world software project - databases are a key component. You will learn how to maintain and version control database schema in an automated fashion via RoundHousE
- You will learn how to build an automated continuous integration (CI) pipeline with Jenkins and its various plugins
- Build CI and CD pipelines using Jenkins, Gradle, Maven, Artifactory and corresponding plugins
- You will learn how to configure, secure and extend Jenkins
- The continuous integration (CI) pipeline will integrate the automated builds with Git repositories hosted in GitHub
- You will also learn how to manage the build artifacts which are produced by the continuous integration (CI) builds
English [Auto] After the installation is complete we can go back to the wiki and see what we need to do next. Looks like we need to start Kingdon's on our Sango as Linux instance. We have a great utility called service which can start or stop our Jenkins instance. All you need to do is copy and execute this command service Jenkyns start OK. Great. Our Jenkin's has started. Excellent. Now obviously it will not be very convenient if you have to start Jenkins manually every time. It will be great. The service started automatically as our Linux system boots up this next command achieves just that. Let's copy and execute this command. See H.K. config. Jenkins OK with this command you're Jenkins will start automatically. Anytime we start our Linux operating system. Great let's verify the status of Jenkyns service. Once again we will execute the command service Jenkyns status. And as you can see Jenkins is active and running now. We are now ready to access Jenkin's to manage and configure it. Let's move further since this is a vanilla version of scent OS version 7. This particular Linux machine doesn't have any graphical interface at all. That is why the only way for us to access the Jenkins user interface is to navigate to our Jenkin's instance from our windows host machine using a web browser. But this virtual machine has been installed with bridge adapter mode. That is why the only way for us to access our Jenkins service is to manage special host files in Windows to modify that file. We will launch command prompt on our windows host with administrator privileges and navigate to Windows system directory backslash drivers backslash EDC here to edit our hosts file we will open it up with Notepad. This host files helps the Windows system in DNS and IP resolution for our host. All we need is to get our IP address from our Linux machine and input it here in our hosts file. Also to map this IP address we need to get our hostname from our Linux machine. We can get it by executing the command hostname which in our cases Jenkyns noodle that Tatra and also paste it here in our hosts file. Good. Now our Windows host can easily resolve the IP addresses for our Linux machine. Now if we navigate to this you are no Jenkin's noodle that Tatra in our browser window it will direct us to the virtual machine. We will save and close our hosts file now. Great let's go to our browser and continue our configuration process. We will navigate to our Jenkin's host name with the default port for Jenkins which is 8 0 8 0. OK great. We are presented with this wizard for configuring our Jenkyns instance because this is our fresh installation of Jenkins in order to proceed further. We need to unlock it by supplying Jenkins administrator password. Jacob configures a default initial administrator password which can be found at this location. We will copy this path here and go back to our S-sh session for our Linux machine and open this file. And here is the initial password. Now click on continue. OK. Excellent Now Jenkins instance has been unlocked and we can proceed further next Jenkins is presenting us with two options for configuring our Jenkin's instance install suggested plugins. This means Jenkins will configure our instance with the recommended plugins and the second option is select plugins to install which naturally provide more control over configuration. For now let's select the select plugins to install so that you can get a behind the scenes look at all the plugins that are available for Jenkin's. Jenkins has a vast community which has contributed hundreds of plugins to its vast ecosystem. As you can see there are quite a few of them and each one listed here has its own description. The selected plugins are the plugins which get installed when we select the install suggested plugins option and the installation wizard. These are the most useful and popular plugins which Jenkins community has selected to be installed by default. These other plug ins we generally need to run unnecessary death ops pipelines in typical environments. Of course after installing these default plugins we are free to install more plug ins as per our requirements. We will focus on the most important and the most original plugins which will be instrumental in running and using our Jenkins server effectively. Let's start with dashboard view. Basically all this plugin does is add visual diagrams to your jobs. For instance if you have many jobs and they take a while to run and you find it easier to visualize the process with some graphical statistic that this dashboard view will provide that functionality to you. The most important plug in in the context of this corps is the pipeline plug in for continuous delivery pipelined plug and appeared in Jenkins version 1.5 at the very beginning. It was just a simple groovy script which provided basic management for Jenkins jobs. But since that it has matured into a much more useful plugin the next plug in is build the pipeline plug in the plug and provides a graphical interface for managing pipelines. Lets select this plug in for our Jenkintown Stellas. Well using this plugin we will not need to write any code or scripts to build our pipelines with the help of this plugin we can manage our jobs via the graphical interface it provides which is much more user friendly. Also we need to install coffee artifact plugin because only this plugin allows us to manage specific continuous integration and continuous delivery jobs. Source code management plugins are rather useful too. Here we select the plug in suitable for our respective source code management tools. In our case we all use get lab or get hub. Maybe we will also use bitbucket plug in select select all these plugins. Next the plugins that we'd select are S-sh plug in and publish over S-sh plug in both these plug ins are used to execute some commands over S-sh to remote host or to pass them files over to S-sh. We will install all these necessary plugins as we start building our build pipeline and we need that specific add on for now to move forward efficiently. We will go back and select install suggested plugins option at this point. Jenkins will download all the necessary dependencies from the Internet. That is why you must make sure that your Jenkins machine is connected to the Internet. Let's wait and allow Jenkins to install unnecessary installation files before continuing further after the installation of all dependencies are Jenkyns instance is now ready great. Now we have successfully installed Jenkins and are ready to use it and manage it.