Notes: There is no need to select the check boxes of the other plugins in this filtered list because the main Blue Ocean

• 
  There is no need to select the check boxes of the other plugins in this filtered list because the main Blue Ocean plugin has other plugin dependencies (constituting the Blue Ocean suite of plugins) which will automatically be selected and installed when you click one of these "Install" buttons.
  
• 
  If you chose the Install without restart button, you may need to restart Jenkins in order to gain full Blue Ocean functionality.
  

• 
  Once a Jenkins environment has Blue Ocean installed, after logging in to the Jenkins classic UI, you can access the Blue Ocean UI by clicking Open Blue Ocean on the left.
  

• 
  Alternatively, you can access Blue Ocean directly by appending /blue to the end of your Jenkins server’s URL - e.g. https://jenkins-server-url/blue.
  

4.10. What is meant by Jenkinsfile?

• 
  Jenkinsfile is a text file that contains the definition of a Jenkins Pipeline and is checked into source control.
  
• 
  It is written in Groovy-like syntax, if your IDE is not correctly syntax highlighting your Jenkinsfile, try inserting the line #!/usr/bin/env groovy at the top of the Jenkinsfile.
  

4.11. What is Jenkins Shared Library?

• 
  When we say CI/CD as code, it should have modularity and reusability. And mainly it should follow the DRY principles. He is where Jenkins Shared Library comes in to play.
  
• 
  Jenkins Shared library is the concept of having a common pipeline code in the version control system that can be used by any number of pipelines just by referencing it. In fact, multiple teams can use the same library for their pipelines.
  
• 
  You can compare it with the common programming Library. In programming, we create individual libraries which can be used by anyone just by importing it into their code.
  
• 
  For example, if you have a ten java microservices pipelines, the maven build step will be duplicated in all the 10 pipelines. And whenever a new service gets added, you will copy and paste the pipeline code again. Also, let say you want to change some parameter in the maven build step, you will have to do it all the pipelines manually.
  
• 
  For the same scenario, can write a shared library for maven build, and in all the pipelines we just must refer the maven build library code. In future for any maven changes, all you must update it they shared library code. It will be applied to all the pipelines.