WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.200 --> 00:00:10.600
In this video, I will introduce you to devops pipeline phases that

1
00:00:10.600 --> 00:00:13.500
 are used for software development in deployment life cycles.

2
00:00:15.200 --> 00:00:18.800
We talked in a previous video about devops philosophies in particular

3
00:00:18.800 --> 00:00:21.500
 the flow from left to right the

4
00:00:21.500 --> 00:00:24.600
 objective of any software development life cycle is to release code

5
00:00:24.600 --> 00:00:27.400
 to your customer in a predictable frequent and repeatable

6
00:00:27.400 --> 00:00:27.900
 manner.

7
00:00:28.500 --> 00:00:31.000
A devops pipeline does just that.

8
00:00:32.400 --> 00:00:35.400
A pipeline is the process and tooling that moves software from

9
00:00:35.400 --> 00:00:36.900
 the developer to the customer.

10
00:00:37.700 --> 00:00:40.800
It is usually broken down into six phases. They are

11
00:00:40.800 --> 00:00:44.100
 plan develop build tests release and

12
00:00:43.100 --> 00:00:44.600
 monitor.

13
00:00:45.700 --> 00:00:48.000
Let's discuss each of these in more detail.

14
00:00:48.800 --> 00:00:51.500
The planning stage is used to plan out

15
00:00:51.500 --> 00:00:55.400
 the project roadmap infrastructure or architecture. The

16
00:00:54.400 --> 00:00:57.300
 requirements of flushed out and broken into

17
00:00:57.300 --> 00:01:00.000
 small chunks of work. Some common tools that are used

18
00:01:00.200 --> 00:01:02.600
 in this stage are jira and pivotal tracker.

19
00:01:03.300 --> 00:01:06.700
In the development stage you write code according to your roadmap

20
00:01:06.700 --> 00:01:09.700
 and use a central Source control repository where

21
00:01:09.700 --> 00:01:12.300
 you save your work. Once that code is

22
00:01:12.300 --> 00:01:15.600
 complete and peer-reviewed. It is pushed up to the source control

23
00:01:15.600 --> 00:01:18.600
 repository where automated tasks kick

24
00:01:18.600 --> 00:01:21.200
 off the build stage some common tools that

25
00:01:21.200 --> 00:01:24.300
 are used in this stage are Vim vs code and

26
00:01:24.300 --> 00:01:24.600
 get

27
00:01:25.500 --> 00:01:28.100
The building stage takes a code commit or

28
00:01:28.100 --> 00:01:31.300
 pull request from the center repository and builds

29
00:01:31.300 --> 00:01:31.400
 it.

30
00:01:32.200 --> 00:01:35.300
After building a successful, the new code changes are ready

31
00:01:35.300 --> 00:01:38.700
 for testing if the build fails in any way the pipeline

32
00:01:38.700 --> 00:01:41.100
 is halted and then the error is sent back

33
00:01:41.100 --> 00:01:42.500
 to the person who committed the code.

34
00:01:43.300 --> 00:01:47.100
Some popular tools that are used in this stage are Jenkins containers

35
00:01:46.100 --> 00:01:49.600
 in AWS code pipeline in the

36
00:01:49.600 --> 00:01:52.300
 testing phase your code from the build stage is

37
00:01:52.300 --> 00:01:55.400
 run through different types of tests, like unit tests or linting.

38
00:01:56.100 --> 00:01:59.700
If testing fails at all, the pipeline stops, and

39
00:01:59.700 --> 00:02:01.300
 the code committer is then notified.

40
00:02:02.100 --> 00:02:06.000
Some tools that are used in this stage are Jenkins Circle CI

41
00:02:05.100 --> 00:02:08.200
 and programming language testing Frameworks.

42
00:02:10.400 --> 00:02:13.300
The release stage is where the final artifact that is past the

43
00:02:13.300 --> 00:02:16.300
 build and test stages gets one more round

44
00:02:16.300 --> 00:02:16.900
 of testing.

45
00:02:17.500 --> 00:02:20.500
These tests are usually integrational performance regression

46
00:02:20.500 --> 00:02:21.100
 in nature.

47
00:02:21.700 --> 00:02:24.300
Once these pass the artifact is ready

48
00:02:24.300 --> 00:02:27.100
 for delivery to a production environment. This will either be

49
00:02:27.100 --> 00:02:30.900
 an automated release to production like continuous deployment or a

50
00:02:30.900 --> 00:02:32.700
 stage one like continuous delivery.

51
00:02:33.200 --> 00:02:36.500
Some common tools that are used in this stage are Jenkins X

52
00:02:36.500 --> 00:02:39.200
 Argo CD and AWS code

53
00:02:39.200 --> 00:02:39.600
 deploy.

54
00:02:40.900 --> 00:02:43.300
In the monitoring stage metrics and

55
00:02:43.300 --> 00:02:46.500
 data are gathered from the release and are checked for possible errors

56
00:02:46.500 --> 00:02:49.300
 or regression. If the application is throwing

57
00:02:49.300 --> 00:02:52.300
 errors at a rate that violates some threshold that you

58
00:02:52.300 --> 00:02:55.300
 have set then the releases automatically roll back

59
00:02:55.300 --> 00:02:56.200
 to a known good state.

60
00:02:56.900 --> 00:02:59.600
The data gathered in this stage like performance

61
00:02:59.600 --> 00:03:02.300
 and errors are then fed all the way back

62
00:03:02.300 --> 00:03:06.000
 to the plan stage to begin this process all over again some

63
00:03:05.400 --> 00:03:08.400
 popular tools that are used in this stage are

64
00:03:08.400 --> 00:03:11.900
 Prometheus data dog and AWS cloudwatch

65
00:03:11.900 --> 00:03:12.500
 metrics.

66
00:03:14.400 --> 00:03:17.600
In this video you learned about the process of releasing code

67
00:03:17.600 --> 00:03:20.300
 to your customer. There are six distinct stages

68
00:03:20.300 --> 00:03:23.600
 that help control the flow from left to right you begin

69
00:03:23.600 --> 00:03:26.500
 at the plan stage and progress all the way through till

70
00:03:26.500 --> 00:03:29.400
 you reach the monitor stage. Each stage is

71
00:03:29.400 --> 00:03:31.500
 automated and should halt if any of them fail.

72
00:03:32.100 --> 00:03:35.300
There are numerous tools like get Jenkins and containers that each

73
00:03:35.300 --> 00:03:38.300
 stage can use to make the process of shipping code easier.

74
00:03:40.700 --> 00:03:43.400
In the next video, we will learn about containers and how

75
00:03:43.400 --> 00:03:46.300
 they are managed using a container orchestrator. See you

76
00:03:46.300 --> 00:03:46.400
 soon.
