Description

Create maven app with Spring boot

Sub-Requirements

• Use Maven for the build tool
• Use spring boot to create a simple application
• Create at least one JUnit test
• Use Git to track the history of the application

Source

Use Jenkins to set up a distributed pipeline that will compile and test a Maven project...

You must use the following:

• Git: As a version control system for the software
  ...
• Spring boot: To create the Maven app
• Maven: To compile the program

The following requirements should be met:

• The app should be built with Maven

Requirement addressed

#1

Description

• Generate a simple hello world spring boot application (consider using the Spring Initializer
• Add a JUnit test to the code base
• Capture a screenshot of the maven build succeeding on the command line for the demo page
• Capture evidence that the application uses Spring Boot for the demo page

Description

Create controller and two agent Jenkins instances.

Sub-requirements

• Create an AWS EC2 server instance with Jenkins install to act as the controller
• Create two other AWS EC2 instances
• Configure two non-controller instances as distinct Jenkins agents

Source

You’re tasked with designing a Jenkins architecture that involves one master and two slave nodes, all hosted on various AWS instances.

You must use the following:
...

• Jenkins: To create the build pipeline
  ...
• AWS EC2: To run the [controller] and [agent] nodes

The following requirements should be met:
...

• There should be three EC2 instances to run the master and two slave nodes.

Description

Create a pipeline job to build then test the code

Sub-requirements

• Create pipeline job with a JenkinsFile
• Configure pipeline to have a build and a test stage
• Configure pipeline build triggers on the controller instance

Source

The build jobs should always be triggered by the [controller] and executed on the slaves. You have to set up a pipeline on the [controller] node and write a [JenkinsFile] that clearly differentiates the tasks to be run on various [agents].

The following requirements should be met:
...

• All builds should be triggered and monitored by the [controller] node.

Requirement addressed

#3

Description

• Generate a multibranch build pipeline in Jenkins via connections to this repo
• Configure a build and test stage in the build pipeline
• Configure build job to be triggered on push
• Configure build job to be triggered nightly

Requirement addressed

#2

Description

• Spin up 3 AWS EC2 instances (named controller, agent1, agent2 - if you have a choice)
• Capture screenshot showing the existence of all 3 AWS instances

Requirement addressed

#4

Description

• Configure build and test stages to run on distinct agents (and not the controller)
• Run the job
• Verify the controller can monitor the status of the stages run on the individual agents
• Capture evidence for demo page that req 4 is completely met

Requirement addressed

#2

Description

• Install Jenkins on the controller AWS EC2 instance
• Capture evidence that Jenkins is installed on the agent for the demo page

Requirement addressed

#2

Description

• Connect the agents to the controller (probably just setting up ssh keys)
• Ensure agents are capable of executing maven stuff
• Capture evidence for demo page that Jenkins sees the two agents

Description

Configure the build pipeline such that one agent always performs the build stage and the other agent always performs the test test stage.

Sub-requirements

• Build (compile) stage will be performed exclusively on one agent
• Testing will be performed exclusively on the other agent
• Agent selection will be specified in the JenkinsFile
• Controller must monitor status of stages on agents

Source

Use Jenkins to set up a distributed pipeline that will compile and test a Maven project on two different [agent] nodes respectively.

The build jobs should always be triggered by the [controller] and executed on the [agents]. You have to set up a pipeline on the master node and _write a [JenkinsFile] that clearly differentiates the tasks to be run on various [agents].

The following requirements should be met:
...

• All builds should be triggered and monitored by the [controller] node.
• Compilation and testing should be done on dedicated [agent] nodes.