Java

Perforce

Subversion

Git

Maven

None of these

junit-report "path to xml file"

generate "junit-report"

junit "path to xml file"

START_TIME

JOB_NAME

NODE_NAME

BUILD_NUMBER

All of these

Using a regular expression pattern

Explicitly set projects to view

Explicitly set recursively in sub-folders

There is no graphical Plugin Manager

Dashboard Left Panel -> Manage Jenkins -> Configure System -> Manage Plugins

None of these

Dashboard Left Panel -> Manage Jenkins -> Manage Plugins

It shows items that match a filter regular expression.

It shows all items configured in Jenkins.

It shows all items a user has permission to view in Jenkins.

None of these

Jenkins

Subversion

Git

Both Git and Subversion

All of these

Click existing item; in the item view page, select "move" on the left panel; select target folder.

For new items, click folder; in the folder view, select new item; it will automatically be added to that folder.

Hover and click arrow on existing item, choose "move", select target folder.

None of these

A pioneer in education

An organizational culture where developers and operations are working in harmony

The practice of developing optimal work practices

Add text to the "System Message" field on the "System Configuration" page to populate a banner displayed across the top of the master's home page.

On the "System Configuration" page, choose the "Maintenance Alerts" option from the "Alerts" dropdown menu and populate the box with a message to be added to all build logs.

Populate the "Email Notifications" section of the "System Configuration" page with a message to be sent as email to all registered Jenkins users.

On the master's dashboard, dick "add description" or "edit description" to populate a banner displayed across the top of the master's home page.

The default number of executors on a node is 4.

You can run many of them in parallel.

They can run on the master.

It runs projects dictated by Jenkins.

You could use the Parameterized Trigger Plugin to trigger from an upstream project.

Both "Triggered by another project" and the "Parameterized Trigger Plugin"

Use the run() function passing the downstream projects name from within an upstream project build step.

In the downstream build, you can select "Triggered by another project"

.rb

.hpi

.groovy

.java

agent { label 'docker'}

None of these

agent { docker 'openjdk'}

agent docker

Create additional Jenkins Masters and deploy the job to each one. Schedule the job staggered by 30 minutes on each one so that the additional master servers won’t be busy if the first job runs long.

Add one or more slave nodes to the environment, this will allow us to deploy code to multiple end points at one time. Break up the single job into multiple jobs so that each one can be triggered by the successful completion of the previous job to eliminate scheduling problems on beginning a new build in the event subsequent steps run longer than the intended time period.

None of these

Remove the performance testing from the build. Schedule performance testing as a separate job 30 minutes after the build runs and trigger a rollback if the performance testing fails at this point.

Continuous deployment means the code CAN be released at any time, while continuous integration means it is released continuously.

Continuous delivery means the code CAN be released at any time, while continuous integration means it is released continuously

Continuous integration is just the practice of integrating code continuously. It doesn't necessarily mean that it can be released at any time like continuous delivery

Continuous delivery and continuous integration are the same thing.

Maintain a single source repository.

Do everything manually with great care.

Build every commit.

Make the build self-testing.

Maven

Cobertura

Ant

Gradle

True

False

"${VARIABLE}"

Both "${VARIABLE}" and $VARIABLE

%{VARIABLE}

$VARIABLE

Any Pipeline DSL code that Implements complex computational tasks must be located outside any stage block.

Steps are the logical segmentation of a Pipeline; they contain stages that define actual tasks.

Stages are the logical segmentation of a Pipeline; they contain steps that define actual tasks.

Each pipeline must have a global agent specification.

All stages in a Pipeline must execute on the same type of agent.

Ant project

Make project

Grade project

Pipeline project

Freestyle project

Folders

Relational databases

Folders and views

Views

None of these

Using an expression that matches a node's name or label

Select the node from the "Project Configuration" view

Set the projects in the "Manage Node" view