A.The entire repository is scanned so no commits are missed.

B.Builds are started on a defined cron schedule.

C.Avoid unnecessary overhead from polling.

D.Builds are started immediately after changes are committed.

A.Provide information on the current status and configuration options of the CloudBees Assurance Program.

B.Automatically install new CloudBees Core releases as soon as they are available.

C.Enforce and lock a specific configuration in the CloudBees Core instance defined by the administrator.

D.Notify the user when a new CloudBees Core release is available.

A.All stages in a Pipeline must execute on the same type of agent.

B.Stages are the logical segmentation of a Pipeline; they contain steps that define actual tasks.

C.Steps are the logical segmentation of a Pipeline; they contain stages that define actual tasks.

D.Any Pipeline DSL code that implements complex computational tasks must be located outside any stage block.

E.Each pipeline must have a global agent specification.

A.All instances must run the same Jenkins version.

B.All instances must run the same Jenkins version and the same JDK version.

C.All instances must be +/- one ma)or revision from each other.

D.Each instance can have a different Jenkins version and a different JDK version as long as they all run on the same operating system version.

E.All instances must run the same JDK version.

A.Merge Review

B.Polling

C.Version Control

D.Tagging

E.Webhooks