using Jenkinsfile;

using a DSL;

using Jenkins API;

using run steps in Jenkins;

using Bash;

parameters

triggers

workspace

options

parallel

Part of an application to be versioned and reviewed like any code

This is a sequence of steps

This is a text file

This is a sequence of tasks

This is a foundation of "Pipeline-as-code

End-to-end tests: check an application by simulating user interaction.

Security tests, scans the application’s dependencies for known security issues.

Smoke tests:  that check if the  infrastructure is ready to accept deployments.

Unit tests, validate that functions or classes behave as expected.

Integration tests, are used to verify that the different components of an application work well together.

The build stage is the first stretch of a CI/CD pipeline.

The build stage is validates that the application is buildable and provides a testable artifact.

The build stage includes using tools to analyze code.

The build stage automates steps like downloading dependencies, installing tools and compiling.

The build stage is responsible for building the binary, container, or executable program for the project.

Ease of use; easy to configure, operate, and troubleshoot.

Cost; the platform should not be costly.

Reproducibility; the same code should always yield the same results.

Reliability; we are depends on the CI server for testing and deployment, so it must be reliable.

Speed; the platform should be fast and scalable to obtain results in a few minutes.

Continuous deployment requires automatic delivery of the project build to users.

Continuous deployment is a process that takes the output from the delivery pipeline and deploys it to the production system in a safe and automated way.

Continuous deployment is an optional step-up from continuous delivery.

In continuous deployment, developers deploy the code directly to the production stage when it is developed.

Any testing strategy is performed.