jenkins

A Jenkins Declarative Pipeline uses explicit stage definitions and post blocks for structured CI/CD execution. You define an agent, configure stages for build steps, and add post actions for cleanup or notifications.

Handling credentials in a Jenkinsfile requires secure credential integration within the pipeline environment. You use Declarative syntax to inject credentials as environment variables, ensuring secure access without exposing secrets in the code.

Jenkins Declarative Pipeline supports parameterized builds and multi-branch workflows natively. You define parameters in the pipeline block and configure multi-branch pipeline scanning to automatically discover and build branches.

Interacting with the Jenkins API allows you to trigger remote builds and query pipeline status programmatically. You send HTTP requests to Jenkins API endpoints using authentication tokens to automate deployment coordination.

Scripted Pipeline is necessary for complex dynamic logic or shared library requirements that Declarative cannot handle. Declarative Pipeline is preferred for standard CI/CD tasks due to better readability and built-in safety features.

Configuring timeouts and retries in a Jenkins pipeline uses built-in Declarative options to prevent hanging builds. You add options like timeout and retry inside the pipeline or stage block to automatically handle transient failures.