Answer:- Initially, Jenkins was called Hudson. However, due to some reasons, the name was changed from Hudson to Jenkins.

Answer:- First, we need to open the console output where the broken build is created and then see if there are any file changes that were missed. If we do not find any issues in this manner, then we can update our local workspace and replicate the problem and then try to solve it.

Answer:- First, we need to copy our jobs directory from the old to the new server. There are multiple ways to do it. We can either move the job from the installation by simply copying the corresponding job directory or we can make a clone of the job directory by making an existing job’s copy. For this, we need to have a different name, which we can rename later.

Answer:- Some steps for scheduling builds in Jenkins are as follows: • First, we should have a source code management commit. • We have to complete the other builds. • Then, we have to schedule it to run at a specified time. • We need to then give a manual build request.

Answer:- To configure Jenkins with Maven: 1. On the Jenkins dashboard, go to Manage Jenkins, and select Configure System 2. Scroll down until the Maven section is seen, and then go to Add Maven 3. Uncheck the ‘Install automatically’ box 4. Add any name for the setting and the location of the MAVEN_HOME 5. After saving, one can create a job with the ‘Maven project’ option

Answer:- To create a slave node in Jenkins: 1. Go to Manage Jenkins, and scroll down to Manage Nodes 2. Click on New Node 3. Set the node name, choose the Dumb slave option, and then click on OK 4. Enter the node slave machine details, and click on Save

Answer:- On the Jenkins dashboard, go to Manage Jenkins and then to Manage Plugins. In the Available section, tick off the ‘Deploy to Container Plugin’ box and install it. Then, restart the Jenkins server The next step is to go to the Build project and click on Configure. Choose the ‘Deploy war/ear to a container’ option In the Deploy war/ear to a container section, enter the server details on which the files need to be deployed, and press Save After a successful build, the necessary files will get deployed to the required container.

Answer:- The Puppet is a configuration management tool that is extensively used for automating the administration tasks. Puppet tool helps you deploy, manage and configure your servers.

Answer:- The Manifests are just files in Puppet wherein the client configuration is specified.

Answer:- The manifests that we define in modules can be included in the manifests. This makes it easier to manage the manifests. It is possible to push the chosen manifest on to the specific agent or node.

Answer:- The Facter is a system profiling library which is used to gather system information during a Puppet run. The Facter offers your information regarding the IP address, version of kernel, CPU and others.

Answer:- Puppet Kick lets you trigger the Puppet Agent from Puppet Master. During the run interval the Puppet Agent will send a request to Puppet Master.

Answer:- The MCollective is a tool that is developed by the Puppet labs for server orchestration. MCollective helps to run thousands of jobs in parallel using your own or existing plugins.

Answer:- You can use the Puppet tool for managing machines which are laptops, desktops and even workstations.