CJE Certified Jenkins Engineer (CJE) Questions and Answers

Aborted

Success

Unstable

Failure

Not Built

All orphaned jobs that match the " Orphaned Item Strategy " are cleaned up automatically every 24 hours.

All orphaned jobs are cleaned up every time the Multibranch project is saved.

All orphaned jobs that match the " Orphaned Item Strategy " configuration are cleaned up on every branch re-index process.

All " orphaned " jobs are cleaned up on every branch re-Index process.

Folders and views

Relational Database

Folders

Views

ephemeral and replaceable

tailored to specific builds

on-master

static

notice

alert

email

emailext

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.

smoke tests

acceptance tests

functional tests

non-regression tests

All of the others

Parameterized Trigger

Pipeline

Credentials

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 "

tests an Individual unit a component

verifies cross-functionalities

verifies that the complete software matches the specifications it was written to fulfill

is written when an Integration or multi-environment bog is fixed

None of these

junit-report " path to xml file "

generate " junit-report "

junit " path to xml file "

If your Jenkinsfile specifies parameters with the " parameters ' ' directive, those are the only parameters recognized when the Pipeline executes; any parameters that were specified In the " Project is parameterized " section of the Job configuration are cleared.

Use the " params " object to reference parameters that are defined on " The project is parameterized " section of the job configuration.

Use the " parameters " directive to define parameters for your Pipeline Inside your Pipeline code.

If you configure a build parameter of type File, then users can specify a file on the server as build input.

Source Code (or Control) Management

Structural Code Machine

Super Core Management

None of the above

All credential bindings support the " Secret Text " and " Standard username and password " credential types.

Credential IDs are case Insensitive.

The credential types supported are defined by the binding plugin (or the resource being accessed.

Most credentials called from a pipeline have Global scope, not System scope.

Add SSH Credentials

Add specific plugins

Create an Admin user with username and password

Add common plugins

GIT_COMMIT

GIT_ORIGIN_URL

GIT_URL

GIT_BRANCH

A groovy script needs to be approved.

A build is waiting for Input.

The build is waiting for an executor to be available.

An agent is being spawned.

consolidation

requirement

process definition

subset

superset

Beekeeper Upgrade Assistant if you are running CloudBees Jenkins Distribution or CloudBees Core.

An email message that is automatically sent to all users who have registered with the mailing list at Jenklnssd-advisories@googlegroups.com.

A banner displayed in the upper right section of the master ' s home page.

An email message sent to all users who are listed in the " Send security notifications ' ' field of the " Extended E-mail Notification " configuration.

Jenkins logs.

Building every commit.

Maintaining a single source repository.

Building everything manually with great care.

Making Builds Self-Testing.

Credentials

My Views

New Item

Manage Jenkins

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

Use the pipeline DSL to implement intricate networking and computational tasks that your Pipeline needs to do.

Simplify the test/debug process and improve performance of your pipeline by defining separate steps for each Important task performed by the pipeline.

Encapsulate common Jenkins logic within shared libraries when leveraging Declarative Pipelines.

Call scripts written In Shell, Batch, Groovy, or Python to implement any complex logic required for your pipeline; call these scripts as steps in your pipeline.

Use took such as Maven, Gradle, NPM, Ant, and Make to define most of the build work; cad these executables as steps In your pipeline.

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.

An employee on a DevOps project that ensures all systems are functional

The UI to install and configure plugins in the Jenkins WebGUI

None of these

A command line interface for adding documentation to Jenkins

Pass the argument -Dhuason.model .Run. lockworkspace=false in the Jenkins master Invocation.

Check " Do not lock workspace " In the Advanced Project Options of the project.

Multiple concurrent runs can never share the same workspace.

Define a " Custom workspace " path for the job.

A software development discipline where software is built so that it can be released to production at any time.

A software development discipline where software is released continuously as part of an automated pipeline.

Building in 60 minutes or less.

A software development practice where contributors are integrating their work very frequently.

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.

agent any

agent { label ' Slave 1 ' }

agent none

All of these

Ruby

Python

Java

.NET

Overwrite the hpi file on the file system

Click the " Downgrade to " button in the Plugin Manager

All of these

Use the advanced install option in the Plugin Manager to install an older hpi file than the plugin already installed.

All of these

java -jar /var/lib/jenkins/jenkins-cli.jar -s http://localhost:8080/

jenkins

jcli

Feature branching

All are common

Release branching

Developer branching

SSH Keys

All of these

Username/Password

Username/API Token

Click " New Item " in the left dashboard panel, then select " Folder "

None of these

Add a folder on the Jenkins master file system in /var/lib/jenkins

You can add one from another project ' s " Configuration " view

when { branch ' development ' }

when { branch ' master ' }

when( $branch == ' development ' )

when ' development '

Manage Jenkins - > Configure Global Security

Manage Jenkins - > Configure System

None of these

Manage Jenkins - > Configure Global Options

* * * * H/15

* * 15 * *

H/15 * * * *

15 * * * *

email

Slack

Jira

SMS messaging

All of the above

A username and password configured for the slave node

SSH keys with the Master ' s pub key set as an authorized key on the agent node

No special authorization setup

None of these

the Downstream Builds plugin

manual recording

the Pipeline plugin to fingerprint files

Pipeline labels

can be used to group a number of other steps into a logical unit for display

collects a set of artifacts that can be referenced in a later Pipeline step

prepares a test environment in Jenkins

transfers artifacts to a staging server for testing

Set the " GitHub hook trigger for GITScm polling " trigger

Set the " Poll scm " trigger, but you don ' t have to specify an interval

None of these

Set the " Build Periodically " trigger, but you don ' t have to specify an interval

Perl

Python

Ruby

Java

Sloan Digital Legal Conference

Super Digital Life Chain

None of these

Software Development Life Cycle

It tests the functionality of the project as a whole.

It tests against the product specifications

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

It tests components coming together.

/var/lib/jenkins

/etc/jenkins

With your source code

None of these

A Jenkins user ' s username and GitHub API token.

An SSH key matching an entry in the authorized_keys file of the user account that the Jenkins master process runs " as " .

A Jenkins user ' s username and Kerberos token.

An SSH key matching a Jenkins user ' s public key.

A Jenkins user ' s username and password or API token.

False

True

/tmp/Jenkins/

/var/lib/jenkins/secrets/

/usr/lib/jenkins/password/

/opt/jenkins/

If an environment variable b enclosed In single quotes, the Pipeline DSL dereferences the variable on the master ' s JVM and passes the calculated string to the sh or bat step; if the environment variable Is enclosed in double quotes, the name of the environment variable itself is passed to the " sh " or ' bat " step and the shell interpreter on the agent dereferences the variable.

If an environment variable Is enclosed In double quotes, the Pipeline DSL dereferences the variable on the master ' s JVM and passes the calculated string to the sh or bat step; if the environment variable is enclosed in single quotes, the name of the environment variable itself is passed to the " sh " or " bat " step and the shell interpreter on the agent dereferences the variable.

A Declarative Pipeline can use environment variables defined In Jenkins Itself (such as BUILD_NUMBER and JENKINS^URL), environment variables defined in an installed plugin (such as GIT„COMMIT or GIT .BRANCH, defined in the Git plugin), or environment variables that are coded as directives in the Pipeline itself; the semantics are identical for all environment variables.

An environment variable can be specified globally (to apply to all steps in the pipeline), for an individual step, or for one or more specified steps In the Pipeline,