CCJE Certified CloudBees Jenkins Engineer (CCJE) Questions and Answers

Upgrade every plugin in the system to the latest available version.

Upgrade to a new version of CloudBees Core if it is available.

Upgrade every plugin In the CAP Collection to the version defined by CAP.

Replace every plugin in the system with the version defined by CAP.

Declarative syntax can express complex flows and conditionals.

A jenkinsfile can express the entire CI/CD process as code that is stored in a Source Code Management system.

Execution can be resumed after most failures.

The Jenkinsfile can incorporate any valid Apache Groovy code.

Declarative Pipeline uses the Pipeline domain specific language (DSL) to manipulate Jenkins objects.

Manage Jenkins - > Global Tool Configuration

Build tools need to be configured manually on each agent.

Jenkins Nodes - > Install Tools

Manage Jenkins - > Configure System

Modifying the authorization strategy configuration.

Administering Jenkins' global configuration.

Creating/copying jobs.

Triggering a new build.

Retrieving information from Jenkins for programmatic consumption

Build records.

Job configurations.

Folders configurations.

System configuration.

Views configurations.

Outage of a master will not block flows for all products.

You can easily restrict access to a department's protects to the users within that department.

You can tailor the installed plugins to be specific to the needs of the environment.

You can more easily create pipelines covering entire products.

Use a credential "SSH Username with private key", restricted to the Scope "Agents", for the node's SSH authentication.

Use a credential "SSH Username with private key", restricted to the Scope "System", for the node's SSH authentication.

You cannot use an SSH key pair. Configure a password for the agent's SSH user, and create a credential of type "Username with password" for the node's SSH authentication.

The SSH key will be stored in the )ENKINS_HOME/.ssh folder. Configure the agent to use a key from the "standard" SSH folder.

Scripted Pipelines usually execute significantly faster than the comparable Declarative Pipeline.

Declarative Pipelines usually use the "agent" section to define the node where the code should execute but the "node" parameter can be used instead and allows for additional options such as "customWorkspace’’.

Scripted Pipelines require extensive knowledge of the Apache Groovy syntax wher ease Declarative Pipelines can be implemented with minimal understanding of Groovy and so have a lower risk of syntax errors than Scripted Pipelines.

You can use the Declarative Directive Generator to help structure statements for Declarative Pipelines and use the Snippet Generator to help structure statements for Scripted Pipelines.

Scripted Pipelines can implement some functionality that Declarative Pipeline syntax does not support, although small bits of scripted syntax can be included In a Declarative Pipeline by using the "script" step.

M1 can only perform builds on S1.

M3 can only perform builds on S2.

M4 can perform builds on any shared agent.

M3 can only perform builds on S2 and S3.

M4 can only perform builds on S3.

Build parameters

Matrix based security

Job Configuration Restriction plugin

Declarative Pipeline

System environment variables

Provides a secure environment used to execute sh and bat scripts for all Pipelines and Freestyle Jobs.

Provides the secure environment used to run CLI commands.

Provides a largely unrestricted environment where sophisticated and trusted users can run Apache Groovy scripts to streamline management tasks.

Provides a secure environment to run python scripts to administer Jenkins.

Provides a largely unrestricted environment where sophisticated and trusted users can run sh and bat scripts to streamline management tasks.

Custom-developed plugins.

Jenkins core.

Build tool installers.

Open source plugins.

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.

Define team specific folders and restrict edit access to team members.

You cannot. Each team must use a separate master.

You do not need to do anything. Job editing is restricted to team members by default.

Define team-specific views and set the initial view to the team-specific view.

You should configure Global Pipeline Libraries at the Github Organization level: The libraries are running as "untrusted" code, allowing developer to run code on the Groovy sandbox.

You should not configure any Global Pipeline Libraries at the folder level: The libraries are running as "trusted" code, allowing all developers to execute privileged methods.

You should configure Global Pipeline Libraries at the Pipeline level: The libraries are running as "untrusted" code, allowing developers to run cod on the Groovy sandbox.

You should not configure any Global Pipeline Libraries at all: The libraries are running as "trusted" code, allowing all developers to execute privileged methods.

After the initial setup, the Beekeeper Upgrade Assistant will always be disabled.

Only the OPTIONAL plugins selected in the Setup Wizard and their dependencies will be installed, in their latest versions.

AN the OPTIONAL plugins will be installed, In the versions defined In the CAP Collection.

All the REQUIRED plugins will be Installed, in the versions defined in the CAP Collection.

Only the OPTIONAL plugins selected in the Setup Wizard and their dependencies will be Installed, In the versions defined in the CAP Collection.

Join plugin

Job DSL plugin

Build Pipeline plugin

Promoted Builds plugin

Pipeline plugin (previously named "Workflow")

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

A Jenkins user's username and GitHub API token.

A Jenkins user's username and Kerberos token.

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

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

Operating system buffer cache size and Iimits on open files.

Operating system limits on open files and forked processes.

Database query performance parameters.

Java memory heap size and garbage collector for heap.

Operating system limits on network packet size and interrupt latency.

Single Sign-On (security realm only)

Single Sign-On (security realm and Project-based Matrix authorization strategy)

Do not enforce security settings on masters

Single Sign-On (authorization strategy only)

Single Sign-On (security realm and authorization strategy)

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

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

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

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

Maximum number of Jobs which can be run concurrently on attached agents.

Number of CPU cores configured for this master.

Number of Java threads that can run Jenkins Jobs.

Number of Jobs that can execute simultaneously on the Jenkins master.

Number of external build agents that can be used for Jobs run on this Jenkins master.

Check the Jenkins Update Center.

Search for the plugin in the Jenkins artifact repository.

Email the maintainer.

Check the plugin wiki