If you want to publish e-mail reports, you have two possibilities in Giddyap, you can publish the
report as an artifact and view it within the job, or you can use Getler pages to publish e-mail, websites,
pages, or how do you want to call them?
With Ditlev pages and some e-mail skills, you can create and publish an e-mail website, generate dashboards
that contain test results and your reports from the test.
In this lecture, I will show you a simple example of how he can use Getler pages to publish an existing
estimate report before we get started.
Please note that not all lab installations have this feature active if you are not using it left that
come back with your system administrator regarding this feature if you cannot see it.
Going back to our pipeline configuration, we'll do the following, we'll have to create a new job and
that job will be called pages.
I'm going to create a new stage called Publishing.
Now, at this stage, right at the end.
Today are a few things that we need to do in order to publish things so in the scripting part.
We are going to create a new folder and that folder will be called public.
In the public folder will be all the e-mail files that we want to publish.
No, currently we do not have any e-mail files, but if you remember from API testing, we have generated
an e-mail report.
So for that reason, we can use that E in my report to publish it.
Let's move it from there to a public folder.
So the path is Newman's report, that e-mail, and we're going to move it to public index that e-mail.
Finally, in order to get everything to work, we have to publish the artifacts because the publishing
job will look for this artifact.
So the path that we are interested in publishing is public.
So let's run this and see how it looks like.
So now looking at a pipeline, there are a few things I want you to observe.
First of all, you will see the publishing stage, which is right at the end.
It contains pages.
Now, if you look at the front pages, there's absolutely nothing significant about it, it simply creates
the public folder.
It moves the report e-mail to public index that HTML.
It uploads to artifacts.
And that is it.
No deployment, nothing.
Going back to the pipeline overview, you will see that under the deploy stage, there's also an additional
job called pages is deployed.
You cannot click on it, but if you go over the jobs themselves and go at the deployed stage, you'll
be able to notice that this is an external job that has deployed to pages.
You will not be able to see the console, but you will see that it has passed and that everything is
OK.
In a project, if you go to settings, pages.
You will have this page displayed and the main information that you're getting from here is that your
pages are served under this address.
It's important to remember that, especially for the first deployment, it may take up to 30 minutes
before this address will work.
So it does require a bit of patience.
I assume this is running, you can click on the link and hopefully will get the report that has been
generated, displayed here under pages.