CJE Exam Dumps - Certified Jenkins Engineer (CJE)

.rb

.hpi

.groovy

.java

If you check the "Enable rollbacks when upgrading" box, future updates to an the plugin can easily be rolled back when necessary.

The previous public release of a plugin is installed for reliability instead of Installing the most recent public release.

Most plugins can be Installed without stopping and starting Jenkins.

You must install all required and optional dependencies before Installing the plugin with the plugin manager.

If you are running Jenkins under an HTTP proxy, you must configure HTTP proxy access for the plugin manager before Installing or updating plugins.

updates plugins

starts the build of a job

sends notification once the build is completed

detects code changes in the repository

Only top-scoped projects will determine the folder's health

None of these

Folders don't have health

Items in nested sub-folders are used to calculate the folder's health.

It tests components coming together

It tests against the product specifications.

It tests a small piece of functionality, usually at the class method level.

It tests how well your code is tested.

The changes the team makes will be released to production at any time.

The software development team will increase the frequency at which code changes are committed to the build, test, and deployment cycles.

Software changes will now be added to an automated pipeline.

Build time objectives will be targeted to take less than 60 minutes.

Run all builds on agents and never on the master itself.

Use the maximum number of executors at all times and avoid using labels.

Avoid modifying Java parameters that control heap size and garbage collection.

Use plugins as much as possible.

Allocate specific masters for different build types and teams.

None of these

It's only used for freestyle projects

It contains the definition for a pipeline

It contains the basic configuration for Jenkins

Declarative Pipelines cab be restarted after a Jenkins failure but not after a transient outage (such as a network failure or disk space exhaustion).

Declarative Pipelines can be resumed only after a transient outage (such as a network failure or disk space exhaustion).

All Declarative Pipelines are restartable by default, with the same inputs (commit to build, parameters, etc) as the original run. Any data that was built In the original run Is available only If the preserveStashes() option Is specified In the Jenkinsfile

Declarative Pipelines that use Docker containers can not be resumed because the docker APIs that Jenkins calls to create the container are not serialized

A Declarative Pipeline can be restarted only If the preserveStashes() option Is set In the pipeline.

98%

80%

60%

75%

Continuous Integration

Continuous Deployment

Continuous Delivery

Infrastructure as Code

environment(MAJOR_VERSION = 1)

environment { steps { sh " export MAJOR_VERSION=1" }}

environment { MAJOR_VERSION = 1 }

environment [MAJOR_VERSION=1]

Because executors cannot be allocated on the master.

Because executors offloaded onto build nodes are not performant.

Because it prevents the CPU being overloaded during parallel polls.

Because it prevents builds from overloading a master's CPU/memory.

Because builds cannot be run In parallel on a master.

No default administrator account is created; you have to configure security manually.

A default administrator account is created with username "admin" and password "ad

A default administrator account is created with username "admin" and password from the file

JENKINS_HOME/secrets/initialAdminPassword

A default administrator account is created and you cannot re-enable security.

It tests against the product specifications.

It tests the functionality of the project as a whole.

It tests components coming together

It tests a small piece of functionality, usually at the class method level.

Java

Perforce

Subversion

Git

Maven

Pull requests

Disabled projects

Scripts waiting approval

Builds waiting for an executor

Validate with the CI system, write the new functional code, and then verify that the test passes.

Write a new test, validate with the a system, and then write the new functional code.

Write a new falling unit test, write the new functional code to fix the test, verify that the test passes, and then refactor the code.

Write a new failing unit test, write the new functional code to fix the test, and then verify that the test passes.

Trigger even if the build fails.

Trigger only if the build succeeds during working hours.

Trigger only if the build produces artifacts.

Trigger only if the build succeeds.

Trigger even if the build is unstable.

There is no graphical Plugin Manager

Dashboard Left Panel -> Manage Jenkins -> Manage Plugins

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

None of these

Feature branching and release branching, but not developer branching, are common branching strategies.

Developer branching and feature branching, but not release branching, are common branching strategies.

Developer branching, feature branching, and release branching are common branching strategies.

Release branching and developer branching, but not feature branching, are common branching strategies.

Use an input step just before the deploy stage.

This is not possible using Pipeline, because a Pipeline must run from start to finish without human interaction.

Create a separate Pipeline to run the deploy stage.

Use a stage step just before the deploy stage.

Copy artifact files to the agent file system

Upload the artifact files to a central artifact repository.

Stash artifact files.

Commit the artifact files to git.

An upstream project has more build steps

An upstream project triggers a downstream project.

A downstream project produces no artifacts.

A downstream project triggers an upstream project.