Free Practice Questions for CloudBees CCJE Exam

To allow continuing the build on another agent.

To avoid having to rerun the entire Pipeline If a transient error occurs.

To visually separate stages.

To run additional tests.

To configure pipelines to send a progress report by email when a checkpoint is reached.

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 she! Interpreter on the agent dereferences the variable.

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.

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 m the Git plugin), or environment variables that are coded as directives In the Pipeline Itself: the semantics are identical for all environment variables.

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

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.

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

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.

Operations Center enables you to interconnect different CI systems, such as CloudBees CodeShip and Jenkins

It is easier to share resources among Jenkins masters that are connected to the same Operations Center.

It is easier to run Pipelines on the Operations Center because it can retrieve resources from all connected masters.

Operations Center handles the build toad more efficiently by scheduling tasks on idle Jenkins masters.

It Is easier to perform administration tasks (such as upgrading a plugin) on a group of masters that are attached to the same Operations Center.

The "Publish JUnR results" reporter finds the test reports.

All build steps are successful.

There is at least one SKIPPED test case.

All publishers before "Publish JUnit results" assign the SUCCESS status.

The overall "stability report amplification factor" is greater than 1.00.

There is at least one FAILED test case.

unit build data using the job setting "Discard old builds".

Change the order of jobs in the pipeline.

Gear the Jenkins cache.

Increase the size of the JENKINS.HOME partition/logical volume.

Make sure you regularly delete unused views.

Users will notice that builds in progress on the failed node are lost but they will not notice any downtime on the service because the sessions and workload are shared between participating Client Master nodes; we have an active-active HA setup.

Users will not notice anything because participating Master nodes share workloads together; we have an active-active HA setup.

Users will experience a brief downtime, comparable to the time required to reboot a Jenkins master in a non-HA setup. Freestyle builds that were in progress are lost, but Pipeline builds will resume when the secondary master is online; we have an active passive setup.

Users will not notice anything because the sessions are shared between participating Client Masters and the $JE NKINS HOME directory of the failed Client Master Is copied to resume the failed master's work; we have an active passive setup.

They can be stored on an NFS shared folder of your infrastructure.

They can be stored on the Jenkins master, inside the JENKINS.HOME/.globallibrary folder.

They can be stored by the Jenkins administrators, using a custom Job manager.

They can be stored on a git repository hosted by the Jenkins master.

They can be stored on an external SVN repository.

Download the value from a URL during the build itself.

Define the environment variable in a shared library function that each Job calls.

Set the environment variable on each pipeline or Job.

Define the environment variable on the Operations Center so it is available to all pipelines and Jobs, whereever they run in the duster.

Put all the pipelines and Jobs on one master or in one folder and set the environment variable in that master or folder.

group

steps

collect

stage

steps