# Configuring for postman collection running

**URL:** <https://community.jenkins.io/t/configuring-for-postman-collection-running/7447>\
**Category:** Using Jenkins\
**Tags:** docker\
**Created:** [May 17, 2023, 8:56pm UTC](https://community.jenkins.io/t/configuring-for-postman-collection-running/7447 "2023-05-17T20:56:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![karlkras](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@karlkras](https://community.jenkins.io/u/karlkras)\
**Post date:** [May 17, 2023, 8:56pm UTC](https://community.jenkins.io/t/configuring-for-postman-collection-running/7447/1 "2023-05-17T20:56:35Z")

</div>

I’m attempting to configure my jenkins instance (docker jenkins/jenkins:llts-jdk11) to run postman collection tests via newman integration.  
I’ve followed instructions on how to perform this with various instructional references, [one of which like this](https://stackoverflow.com/questions/53142260/run-newman-in-jenkins) but it doesn’t appear to be working. Looking at the logs I see this:

> WARNING h.m.DownloadService$Downloadable#updateNow: No tool installer metadata found for jenkins.plugins.nodejs.tools.MirrorNodeJSInstaller

so I’m assuming it’s failing.  
Attempting to create a job with a execute shell script with this in it:

> node --version  
> newman --version

and getting this on test results:

```auto
Building in workspace /var/jenkins_home/workspace/test_two
[test_two] $ /bin/sh -xe /tmp/jenkins12107471891086250062.sh
+ node --version
/tmp/jenkins12107471891086250062.sh: 2: node: not found
Build step 'Execute shell' marked build as failure
Finished: FAILURE

```

any ideas on how to fix this? Assuming something is broken?

---

<div class="post-metadata">

**Author:** ![vitaliizghonnik](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/vitaliizghonnik/32/7089_2.png) [@vitaliizghonnik](https://community.jenkins.io/u/vitaliizghonnik)\
**Post date:** [February 19, 2024, 7:37am UTC](https://community.jenkins.io/t/configuring-for-postman-collection-running/7447/2 "2024-02-19T07:37:02Z")

</div>

Hello @Karl, I’m new here, and just read your request.  
I had the same idea that you have been pursuing, so maybe my experience may somehow be useful for you, I hope.

I’ve had the same aim as you did, and after a while, I’ve decided to customize my image.  
I’ve designed the custom image based on the jenkins/jenkins official image, which I pushed on the DockerHub, which you can find in the link below:  
[newman\_jenkins\_plugins\_report](https://hub.docker.com/r/vitalzghonnik/newman_jenkins_plugins_report) image.

Or if you want, you can build your one by adding some of the following instructions in the Dockerfile, I guess:

```auto
RUN apt-get install -y curl && \
    curl -sL https://deb.nodesource.com/setup_16.x | bash - && \
    apt-get install -y nodejs
RUN apt-get update && apt-get install -y npm
RUN npm install -g newman

```

I want to let you know that the instruction you asked for is a part of my Dockerfile, but not the entire file.  
I hope it can be of assistance to you.

---

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [February 19, 2024, 9:17am UTC](https://community.jenkins.io/t/configuring-for-postman-collection-running/7447/3 "2024-02-19T09:17:32Z")

</div>

Are you using an agent, or is everything happening on the controller itself? `node` is not installed by default in the Jenkins controller image. You could try launching a Jenkins instance with `node` installed on an agent and see if it works for you. Clone the [quickstart-tutorials](https://github.com/jenkins-docs/quickstart-tutorials) repository and launch `docker compose up -d node` . This should provide you with a working Jenkins instance, featuring both a controller and an agent, ready to handle `node` pipelines.