---
title: How dotenv Flow Interacts with CI / CD
privateVideoUrl: https://stream.mux.com/Y02ScTknekZYrlXeOf02XB7sOkmQm2ehcnqx3k3QxERTw.m3u8
isPublicLesson: true
code: https://gitlab.com/fullstackio/books/newline-course-apps/environment-variables-for-web-developers-app/-/tree/main/code/module_02/lesson_02.02/App?ref_type=heads
---

## Process

1.  Make sure your code is reading from the .env.test file locally and from the environment for your Continuous Integration build.
2.  Find out where environment variables are to be set in the dashboard of the service.
3.  Set the environment variables in the dashboard.

Kemal Ahmed

How dotenv Flow Interacts with CI / CD

In this lesson I'll answer, how do you run continuous integration tasks when

When you're using continuous integration tools, you still have to figure out

how to configure your application with environment variables.

For those who don't know what CI and CD are, they're typical automated

processes that happen after code is merged into a designated branch of Git

that is identified as being for certified ready code.

This can include anything from automated testing to building production ready

One of the most common tools for this is CircleCI.

To use it, we'll start off with our code from the last lesson.

The way it works is that it takes code from a Git repo and then processes it

So the code which this is in, the code repo that this is in, will be used as a

But first we have to add some tests to it and then run it using our test runner

I'm going to use a popular one called Jest and PM install-d. Jest.

Next we'll create a test script and add just to it.

Now that we have our test runner, Jest, and we've added our test script, let's

add a test folder and put a test in there.

In this test, we import the file from index.js and we run the dbload function.

Let's see what that looks like. To run it, you do npm test.

It failed because the code was set up to work as a lambda function, but we're

running it locally so the dot end variables are actually not brought in.

The problem with this function is we actually have to be calling the handler

And then there's two parameters, event, which isn't really being used.

So we'll just put a blank ID there and then call a context, which needs output

Before I show you the circle CI interface, I will create a configuration file

In there, you create a yaml file config.yml.

And this is the one that I'm using. I'll paste it in the description below.

And then push your code to get. And then we'll see what happens.

When we open circle CI and we set up the project, we'll see what happens.

And it fails because we didn't set the environment variables. Let's go do that

Environment variables. Add in one variable.

Once we've added the four environment variables, we can safely go back and re

After a while, I canceled it because I realized it was working for too long.

The problem is that we didn't run test function. We actually ran the run

What we have to do is open the config, run tests, and the command is npm test.

We'll open that up on circle CI and see what happens.

One last hint, if you are using .ncli to add any additional flags to whatever

you put two dashes and a space. And since we have to close the Mongo client

In the index added a Mongo client export, which should not be received as a

And in the test, I bring the handler in and I close it.

And that's what happens when I push that.

And success, the test pass. Thank you. And see you in the next one.

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Masterclasses

Tutorials

Fullstack React with TypeScript