Jenkins CI feature – Easy Project 2019

Jenkins CI feature – Easy Project 2019

Hello, Easy Project users. Let me show you a new plugin for continuous
integration. You can activate it in the modules on each
particular project. There is a module called Continuous integration. Let’s check it and then let’s go into the
settings and then the Continuous integration module, which is already activated there. First of all, you have to predefine the connection
to your CI/CD tool that you’re using. In my case, I am using the Jenkins so let’s
try the connection first and wait while it works. Then you have a chance to select from the
various pipelines. The selection depends on the purpose of your
project. In my case, I have a project for creating
a new company website, and then I would like to automate the mechanism to be able to follow
the DevOps practices. Then for each piece of the code like this
automatic mechanism, I would like to launch a syntax control of the HTML code. So by drag-and-drop of the task, I would like
to launch this syntax check, and for this syntax check, I have created the job. So I will switch to Jenkins and in here you
can see this is my job and in the configuration, I’m using a utility for checking the HTML
syntax. This utility is paired with the report in
the GitLab, and you can see this is the report what the developers are using for the storage
of each piece of the page from my website. So here I have a configuration as a set, and
right now let’s write in the API token and then pair this job with our automated mechanism. So I will select a job and then I have a chance
to connect to a concrete task. In my case, I would like to launch it for
all of the tasks, and then there is a chance to limit even the type of the task but I will
leave it empty. Right now, I would pair it with a concrete
status like HTML code check. It means that once the task will switch to
this status, the system will automatically launch the job. And what does it mean in practice? If I will drag and drop the task so it will
launch the job. So, let’s try it right now. For example, let’s take this Contact page
and then move it to HTML code check column in Kanban board. Then we can open the task and here you can
see we have a new tab activated there, which is called Easy Jenkins CI. Here is the result from the job, it’s still
pending because it takes a few seconds, however, the result can already be seen and it’s already
paired with the running job. And here you can see it’s a failure because
for this demo I just created a couple of bugs inside the code just to demonstrate that the
utility is really controlling the syntax in this Contact page’s HTML, which is stored
in the GitLab. This is the page. So here we can even go into details and click
on it, and then we are redirected and we can double-check this is the job what we have
launched. Here we can double-check logs so you can see
the line where the fail appeared, and then what is the concrete failure message. The same result can also be found here in
the line, followed by the failure message.

You May Also Like

About the Author: Oren Garnes

Leave a Reply

Your email address will not be published. Required fields are marked *