1
00:00:04,030 --> 00:00:10,150
If you want to publish e-mail reports, you have two possibilities in Giddyap, you can publish the

2
00:00:10,150 --> 00:00:18,700
report as an artifact and view it within the job, or you can use Getler pages to publish e-mail, websites,

3
00:00:18,700 --> 00:00:20,410
pages, or how do you want to call them?

4
00:00:20,890 --> 00:00:28,750
With Ditlev pages and some e-mail skills, you can create and publish an e-mail website, generate dashboards

5
00:00:28,750 --> 00:00:32,320
that contain test results and your reports from the test.

6
00:00:33,180 --> 00:00:39,270
In this lecture, I will show you a simple example of how he can use Getler pages to publish an existing

7
00:00:39,270 --> 00:00:42,520
estimate report before we get started.

8
00:00:42,540 --> 00:00:48,450
Please note that not all lab installations have this feature active if you are not using it left that

9
00:00:48,450 --> 00:00:53,220
come back with your system administrator regarding this feature if you cannot see it.

10
00:00:55,150 --> 00:01:01,240
Going back to our pipeline configuration, we'll do the following, we'll have to create a new job and

11
00:01:01,240 --> 00:01:02,740
that job will be called pages.

12
00:01:04,160 --> 00:01:06,650
I'm going to create a new stage called Publishing.

13
00:01:11,260 --> 00:01:13,870
Now, at this stage, right at the end.

14
00:01:17,510 --> 00:01:22,330
Today are a few things that we need to do in order to publish things so in the scripting part.

15
00:01:23,320 --> 00:01:27,730
We are going to create a new folder and that folder will be called public.

16
00:01:28,880 --> 00:01:33,120
In the public folder will be all the e-mail files that we want to publish.

17
00:01:33,530 --> 00:01:39,500
No, currently we do not have any e-mail files, but if you remember from API testing, we have generated

18
00:01:39,500 --> 00:01:40,670
an e-mail report.

19
00:01:41,030 --> 00:01:44,300
So for that reason, we can use that E in my report to publish it.

20
00:01:44,780 --> 00:01:47,960
Let's move it from there to a public folder.

21
00:01:51,270 --> 00:01:58,590
So the path is Newman's report, that e-mail, and we're going to move it to public index that e-mail.

22
00:02:01,280 --> 00:02:06,640
Finally, in order to get everything to work, we have to publish the artifacts because the publishing

23
00:02:06,680 --> 00:02:08,539
job will look for this artifact.

24
00:02:09,419 --> 00:02:12,380
So the path that we are interested in publishing is public.

25
00:02:13,810 --> 00:02:16,210
So let's run this and see how it looks like.

26
00:02:18,420 --> 00:02:22,370
So now looking at a pipeline, there are a few things I want you to observe.

27
00:02:22,920 --> 00:02:26,740
First of all, you will see the publishing stage, which is right at the end.

28
00:02:26,760 --> 00:02:28,050
It contains pages.

29
00:02:29,400 --> 00:02:35,430
Now, if you look at the front pages, there's absolutely nothing significant about it, it simply creates

30
00:02:35,430 --> 00:02:36,380
the public folder.

31
00:02:36,630 --> 00:02:41,010
It moves the report e-mail to public index that HTML.

32
00:02:41,250 --> 00:02:42,600
It uploads to artifacts.

33
00:02:42,600 --> 00:02:43,850
And that is it.

34
00:02:44,100 --> 00:02:45,660
No deployment, nothing.

35
00:02:46,880 --> 00:02:52,580
Going back to the pipeline overview, you will see that under the deploy stage, there's also an additional

36
00:02:52,580 --> 00:02:54,250
job called pages is deployed.

37
00:02:54,500 --> 00:03:01,250
You cannot click on it, but if you go over the jobs themselves and go at the deployed stage, you'll

38
00:03:01,250 --> 00:03:05,270
be able to notice that this is an external job that has deployed to pages.

39
00:03:06,170 --> 00:03:10,520
You will not be able to see the console, but you will see that it has passed and that everything is

40
00:03:10,520 --> 00:03:10,850
OK.

41
00:03:12,630 --> 00:03:15,810
In a project, if you go to settings, pages.

42
00:03:16,680 --> 00:03:21,300
You will have this page displayed and the main information that you're getting from here is that your

43
00:03:21,300 --> 00:03:23,640
pages are served under this address.

44
00:03:24,360 --> 00:03:30,600
It's important to remember that, especially for the first deployment, it may take up to 30 minutes

45
00:03:30,600 --> 00:03:32,670
before this address will work.

46
00:03:32,850 --> 00:03:34,800
So it does require a bit of patience.

47
00:03:35,890 --> 00:03:41,740
I assume this is running, you can click on the link and hopefully will get the report that has been

48
00:03:41,740 --> 00:03:44,050
generated, displayed here under pages.

