CloudBees CJE - Certified Jenkins Engineer (CJE)

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.

@daily

H H * * *

30 12 * * *

All 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.

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.

db-dump

restart

who-am-i

shutdown

CaII the fingerprintArtifact() step immediately after the archiveArtifacts( ) step.

Enable the Declarative Pipeline 'enableFingerprints' 'option' .

Set the Fingerprint Artifacts global configuration option.

Set the "fingerprint: true" argument for the archiveArtifactsQ step.

No action is required; Declarative Pipelines automatically record a fingerprint for each artifact.

It ensures there are no mistakes

None of these

It's faster

It's more thorough

Use the pluginManager.downgrade method in the script console.

Select the version you want to use in the global configuration section for this plugin.

Select one of the previous versions in the Plugin Manager.

Manually download and install the previously installed version.

Use the "downgradeplugin" command In the Jenkins CI I

Use the button on the Plugin Manager that allows a downgrade to the previously installed version.

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.

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.