1
00:00:02,260 --> 00:00:09,760
It seems now that we can work with magic quests and we branches, but still we only have two environments

2
00:00:09,760 --> 00:00:11,800
we have to staging and we have to production.

3
00:00:13,090 --> 00:00:21,370
And the question is, wouldn't it be nice to have, like for each branch, for each future, a way to

4
00:00:21,370 --> 00:00:24,940
view the changes that we have made on an actual system?

5
00:00:27,310 --> 00:00:35,290
And this is actually possible we can create environments for every much request so we can automatically

6
00:00:35,290 --> 00:00:38,900
spin up a dynamic environment for each much request.

7
00:00:39,490 --> 00:00:43,840
And this allows us to review the changes on an actual system.

8
00:00:44,140 --> 00:00:51,520
And if needed, we can run some more advanced tests if we want to be pretty similar to what we have

9
00:00:51,520 --> 00:00:57,160
done on production, where we have the server, it's running and then we can check always everything

10
00:00:57,160 --> 00:00:58,990
integrating well, does everything look good?

11
00:01:00,400 --> 00:01:08,020
And this is not only a good thing for developers, but it can be quite valuable for testers or product

12
00:01:08,020 --> 00:01:11,140
owners, product managers or anybody interested.

13
00:01:12,430 --> 00:01:19,530
And seeing how the new future looks like maybe it's not a small fix, maybe it is a much larger feature,

14
00:01:20,290 --> 00:01:25,750
and for that reason it will be nice to send somebody a link and say, hey, this is what I've been working

15
00:01:25,750 --> 00:01:25,990
on.

16
00:01:26,590 --> 00:01:27,880
This is the latest version.

17
00:01:28,300 --> 00:01:34,390
Go on to this address and take a look and let me know what you like, how this works for you if everything

18
00:01:34,390 --> 00:01:34,830
is OK.

19
00:01:35,530 --> 00:01:42,490
So a non developer would be able to inspect the work that somebody has done by visiting an address and

20
00:01:42,490 --> 00:01:46,480
not having to download code and compiling stuff and starting servers locally.

21
00:01:46,870 --> 00:01:48,220
And this can be very convenient.

22
00:01:48,490 --> 00:01:50,890
And this is exactly what we are going to do in this lecture.

23
00:01:51,430 --> 00:01:57,220
We are gonna spin up a dynamic environment for every which request that we have.

24
00:01:58,860 --> 00:02:05,220
So in order to do that, let's see if we need an additional state and probably we do.

25
00:02:06,690 --> 00:02:09,560
So let's call this system review.

26
00:02:09,570 --> 00:02:12,170
So we are trying to review the changes that we are doing.

27
00:02:12,370 --> 00:02:14,610
So going to call this deploy review.

28
00:02:20,550 --> 00:02:21,810
And that's at a new job.

29
00:02:33,290 --> 00:02:36,620
This will be the same job name as the stage.

30
00:02:38,710 --> 00:02:40,840
And what are we trying to do?

31
00:02:41,290 --> 00:02:46,870
Well, it's pretty simple, what we are actually trying to do is pretty similar to what we have here.

32
00:02:47,680 --> 00:02:50,870
We are trying to deploy something, too.

33
00:02:51,520 --> 00:02:56,380
So what we are trying to do is do you a search in order to deploy whatever we have.

34
00:02:57,310 --> 00:02:59,350
And we're going to change this a bit.

35
00:02:59,350 --> 00:03:02,830
But for the moment, it's quite nice as we have it.

36
00:03:10,150 --> 00:03:17,500
We only want to do it for my request so I can remove myself from here, so this will be only available

37
00:03:17,500 --> 00:03:19,060
for each and every budget request.

38
00:03:20,500 --> 00:03:22,720
And additionally, we need to specify the environment.

39
00:03:25,270 --> 00:03:32,830
Now, the way I would do it is like this we're specifying the environment and the name of the environment

40
00:03:32,830 --> 00:03:40,810
will be review slash and this is an environment variable that is provided by Gottleib.

41
00:03:41,820 --> 00:03:49,140
And you will soon see how it looks like and the address that we are going to use is in the zone and

42
00:03:49,170 --> 00:03:53,370
this is, uh, your Eleni's variable that we can use.

43
00:03:54,930 --> 00:03:58,140
So I think we almost have everything that we need.

44
00:03:58,440 --> 00:04:03,600
We still need to put this information here so to properly deploy.

45
00:04:12,390 --> 00:04:17,880
And we should actually have everything in order to create this environment on the fly.

46
00:04:18,390 --> 00:04:25,830
Now, you'll notice here because in the name we are using variables and no longer hard coding stuff,

47
00:04:26,760 --> 00:04:29,280
it will automatically pick up this value.

48
00:04:29,280 --> 00:04:34,890
And for each branch that we create, it will create a new environment.

49
00:04:36,830 --> 00:04:43,370
And search here will deploy to that environment, so I'm going to create a new branch and push the changes

50
00:04:43,370 --> 00:04:47,080
to the branch and we quickly take a look at how that works.

51
00:04:50,600 --> 00:04:56,660
We now have extended the pipeline for the branches and for the merger request, and what we can see

52
00:04:56,660 --> 00:04:59,400
is that dynamic environment has been created.

53
00:04:59,720 --> 00:05:04,850
Now, the name of this environment is review slash feature dynamic environments, because this is the

54
00:05:04,850 --> 00:05:08,660
way I have known my branch and we can view the app.

55
00:05:09,170 --> 00:05:10,940
So the website that we have created.

56
00:05:11,840 --> 00:05:18,620
So this is the address of the website that we have now is the zone dash review, dash feature and then

57
00:05:18,620 --> 00:05:19,280
some strings.

58
00:05:20,210 --> 00:05:22,210
And this is automatically dynamic.

59
00:05:22,220 --> 00:05:25,340
So we haven't configured this specific address.

60
00:05:25,790 --> 00:05:28,190
We have just used the variables and.

61
00:05:29,180 --> 00:05:34,460
What happened is that we now have this dynamic environment, we can sell it to somebody or anybody looking

62
00:05:34,460 --> 00:05:37,390
at this specific feature can simply take a look.

63
00:05:37,460 --> 00:05:38,810
Hey, how does this look like?

64
00:05:38,810 --> 00:05:39,530
Oh, interesting.

65
00:05:40,490 --> 00:05:48,200
And can take a look up to code and see what we have changed and everything and can especially make comments

66
00:05:48,770 --> 00:05:49,430
review.

67
00:05:49,610 --> 00:05:55,850
Hey, why did you write that this look good, this looks bad, can give it a thumbs up for example,

68
00:05:56,990 --> 00:06:02,630
and eventually can go into merging and lifecycle of this branch and some.

69
00:06:07,610 --> 00:06:13,570
This is something very cool that we have achieved in this lecture now, our deployment process is still

70
00:06:13,580 --> 00:06:18,320
very simple, but it's very, very nice to see how we can take advantage of this environment.

71
00:06:18,650 --> 00:06:23,730
Holwell to integrate and get MCI and how we can see what we are doing.

72
00:06:23,750 --> 00:06:24,950
We are taking everything.

73
00:06:24,950 --> 00:06:28,400
We are creating dynamic environments for each of these branches.

74
00:06:28,760 --> 00:06:30,370
And this is very, very nice.

75
00:06:30,380 --> 00:06:34,910
And as you have seen, the configuration isn't that hard to understand.

76
00:06:35,300 --> 00:06:39,620
So it's quite, quite easy to follow what's going on and how everything works.