vamshiyerrapati

ArchiveArtifactsPipeline

When there are test failures, it is often useful to grab built artifacts from Jenkins for local analysis and investigation. This is made practical by Jenkins’s built-in support for storing "artifacts", files generated during the execution of the Pipeline. This is easily done with the archiveArtifacts step and a file-globbing expression, as is demonstrated in the example

CleanupPipeline

Since the post section of a Pipeline is guaranteed to run at the end of a Pipeline’s execution, we can add some notification or other steps to perform finalization, notification, or other end-of-Pipeline tasks.

demo-webhooks

DeploymentPipeline

The most basic continuous delivery pipeline will have, at minimum, three stages which should be defined in a Jenkinsfile: Build, Test, and Deploy. For this section we will focus primarily on the Deploy stage, but it should be noted that stable Build and Test stages are an important precursor to any deployment activity.

DevOps-Sample1

This project is a sample for training purposes.

DevOps-Training

EmailPipeline

here are plenty of ways to send notifications, below are a few snippets demonstrating how to send notifications about a Pipeline to an email, a Hipchat room, or a Slack channel.

example.github.io

This is an example

FinishupPipelines

inishing up When the Pipeline has finished executing, you may need to run clean-up steps or perform some actions based on the outcome of the Pipeline. These actions can be performed in the post section.

Git-GitHub-Training

DevOps Training Udemy

vamshiyerrapati/ArchiveArtifactsPipeline

When there are test failures, it is often useful to grab built artifacts from Jenkins for local analysis and investigation. This is made practical by Jenkins’s built-in support for storing "artifacts", files generated during the execution of the Pipeline. This is easily done with the archiveArtifacts step and a file-globbing expression, as is demonstrated in the example

vamshiyerrapati/CleanupPipeline

Since the post section of a Pipeline is guaranteed to run at the end of a Pipeline’s execution, we can add some notification or other steps to perform finalization, notification, or other end-of-Pipeline tasks.

vamshiyerrapati/demo-webhooks

vamshiyerrapati/DeploymentPipeline

The most basic continuous delivery pipeline will have, at minimum, three stages which should be defined in a Jenkinsfile: Build, Test, and Deploy. For this section we will focus primarily on the Deploy stage, but it should be noted that stable Build and Test stages are an important precursor to any deployment activity.

vamshiyerrapati/DevOps-Sample1

This project is a sample for training purposes.

vamshiyerrapati/DevOps-Training

vamshiyerrapati/EmailPipeline

here are plenty of ways to send notifications, below are a few snippets demonstrating how to send notifications about a Pipeline to an email, a Hipchat room, or a Slack channel.

vamshiyerrapati/example.github.io

This is an example

vamshiyerrapati/FinishupPipelines

inishing up When the Pipeline has finished executing, you may need to run clean-up steps or perform some actions based on the outcome of the Pipeline. These actions can be performed in the post section.

vamshiyerrapati/Git-GitHub-Training

DevOps Training Udemy

vamshiyerrapati/GK-Angular-Test

vamshiyerrapati/java-tomcat-maven-example

Example Java + Maven Tomcat application

vamshiyerrapati/JavaPipeline

To Create a Pipeline in Java - Example

vamshiyerrapati/JavaTraining

vamshiyerrapati/Jenkins_Upgradev3

vamshiyerrapati/maven-samples

A simple Maven project intended as an example for use in a presentation about Maven.

vamshiyerrapati/MultilineShellPipeline

vamshiyerrapati/NodeJsPipeline

vamshiyerrapati/ParameterInputPipeline

Asking for human input to proceed Often when passing between stages, especially environment stages, you may want human input before continuing. For example, to judge if the application is in a good enough state to "promote" to the production environment. This can be accomplished with the input step.\In the example below, the "Sanity check" stage actually blocks for input and won’t proceed without a person confirming the progress.

vamshiyerrapati/PythonPipeline

vamshiyerrapati/RecordingTestsPipeline

Jenkins can record and aggregate test results so long as your test runner can output test result files. Jenkins typically comes bundled with the junit step, but if your test runner cannot output JUnit-style XML reports, there are additional plugins which process practically any widely-used test report format. To collect our test results and artifacts, we will use the post section.

vamshiyerrapati/RippleMaven

vamshiyerrapati/RubyPipeline

vamshiyerrapati/Sample-Maven-Project-

vamshiyerrapati/Sample-Project

This project folder is for pratice

vamshiyerrapati/SampleMavenProject

vamshiyerrapati/starter-web

Simple starting point website project based upon Initializr

vamshiyerrapati/TimeoutsRetriesPipeline

The "Deploy" stage retries the flakey-deploy.sh script 3 times, and then waits for up to 3 minutes for the health-check.sh script to execute. If the health check script does not complete in 3 minutes, the Pipeline will be marked as having failed in the "Deploy" stage. "Wrapper" steps such as timeout and retry may contain other steps, including timeout or retry.

vamshiyerrapati/TimeoutsRetriesPipeline2

The "Deploy" stage retries the flakey-deploy.sh script 3 times, and then waits for up to 3 minutes for the health-check.sh script to execute. If the health check script does not complete in 3 minutes, the Pipeline will be marked as having failed in the "Deploy" stage. "Wrapper" steps such as timeout and retry may contain other steps, including timeout or retry. We can compose these steps together. For example, if we wanted to retry our deployment 5 times, but never want to spend more than 3 minutes in total before failing the stage:

vamshiyerrapati/vamshiyerrapati.github.io