non regression tests

acceptance tests

smoke tests

functional tests

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.

only repositories that contain a Jenkinsfile in all their branches

all repositories that contain a 3enkinsfile in at least one branch or pull request

all repositories

only repositories that contain a Jenkinsfile in at least one branch

OpenSSL must be instated on the agent.

The agent's SSH Public Key must be in the master's authorized keys.

The pubic key of the credential that is used for the agent must be installed on the agent.

You must log into the agent with SSH and start the agent.

SSHD must be installed on the agent.

Join plugin

Job DSL plugin

Build Pipeline plugin

Promoted Builds plugin

Pipeline plugin (previously named "Workflow")

Provide environment variables that will be available during builds.

Display the worst status for a job inside the folder.

Provide an icon for the folder using a URL.

Count jobs with different statuses.

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.

Log in without entering a password.

Share a user/password pair between jobs.

Define what jobs a user can see.

Generate random passwords to use with third-party integrations.

Populate the "Email Notifications" section of the "System Configuration" page with a message to be sent as email to all registered Jenkins users.

Add text to the "System Message" held on the "System Configuration" page to populate a banner displayed across the top of the master's home page.

On the master's dashboard, dick 'add description" or "edit description" to populate a banner displayed across the top of the master's home page.

On the "System Configuration" page, choose the "Maintenance Alerts" option from the "Alerts" drop-down menu and populate the box with a

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.