Integrate Code & AI into CI/CD Pipelines 🚀

Welcome to this comprehensive tutorial on integrating CODANT AI with your CI CD pipelines.

In today's video we will explore how CODANT AI can transform your workflow by providing quality gates, comprehensive security scanning and test coverage tracking.

While we will focus heavily on Azure DevOps today, but the things remain similar for BitBucket, GitHub and other services.

Codant A offers three powerful tasks.

We will cover them in details.

So first thing we need to do is click on this link which will take you to Codente extension.

You can click get it for free or manually.

You can go to the marketplace and search for code and a.

Once you install it you can see the extension in your extension section.

Kudent AI offers three powerful tasks that we will cover here.

One is quality gates.

Second is automated scans.

Third one is test coverage.

By the end of this video you will understand how to configure this task.

Maximum effectiveness let's deep dive in.

Before jumping into the code, let's understand what each task does.

Code and Quality Gates is your first line of defense.

Think of it as a gatekeeper that ensures code meets of your organization quality standards before it it can be merged.

It automatically detects the current repository and commits and applies quality gates rules you have configured in your code and AI dashboard.

Let me take me take you to the code and AI dashboard.

So go to the settings and we need to enable the quality gates and we need to add the configurations here along with the scopes.

Now come to the second one which is Coda Anti CI Scan is your comprehensive analysis engine.

It scans for export secrets like APIs, keys, passwords, tokens and code quality issues.

Code smells, security vulnerabilities, SQL injections, IAC and dependency vulnerabilities.

So we need to enable this.

In your Codeant app, Go to the settings and go to analysis configurations and and you can enable it and you can see the each individual scan.

So enable it here.

Yeah.

Now the third thing is CODANT Coverage helps you to track your effectiveness over the time.

It supports multiple test coverage formats including XML based formats such as Jaco, Co and Clover as well as test based formats like lcov.

This enables you to upload coverage reports from virtually any testing framework in Java, Python, JavaScript, Go and many more.

You will get visibility into how well your code is tested regardless of which coverage tool your project uses.

Now let's see things in action starting with Azure, DevOps.

Let's start with example 1.

The basic quality gate.

This is simple with just one parameter, your access token current AI automatically detects your current repository, the commit being built and applies your configured quality gate.

That's it.

Now look at the example 2.

Now here we are scanning an external GitHub repository from our Azure DevOps pipeline.

Notice we have added the external GitHub Access Token and the external service.

It can be GitHub or GitLab and the commit ID.

Now in the third example we are adding some optional parameter such as timeout and the polling interval.

By default the values of this timeout will be 300 second, I.e.

5 minutes, and the polling interval will be 15 seconds.

Moving to the CA scan task.

This is where security gets serious.

In this example shows the basic configuration just your access token, similar to what we have configured for quality gates.

And in the example 2 we are scanning GitHub repository but the pipelines in is in Azure DevOps third variant here you can see there is one parameter optional parameter called scanners.

So these are the security scans which you wanted to perform.

The default value is sast and scn.

So now if you want to scan for secrets, then you can mention secrets here along with iac.

Or if you want to perform all the scans you can just mention all.

And this is the timeout which we wanted to increase depending upon your size of your repo.

Now let's talk about code and coverage task.

It's similar to both Quality gates and CA scan, but with one additional parameter called coverage path.

This is the path to the coverage file we have generated.

And in the second example for multi platform coverage tracking here also we need to add the coverage path.

This should point to the file which is in the Azure DevOps pipeline.

And in the third example you can see there are some optional parameters we can add.

One is the timeout and the module.

So if you want to test coverage for a particular module, we can pass the module name and the module path here.

That's it.

From Message thank you.