0 buils founds with GitLab #79

aborderon · 2017-10-05T09:55:22Z

Hello,
I have a small problems to run node-build-monitor with GitLab.
I use Docker in production, so I have a Dockerfile and a config.js like :

{
  "monitor": {
    "interval": 30000,
    "numberOfBuilds": 12,
    "latestBuildOnly": false,
    "sortOrder": "date",
    "debug": true
  },
  "services": [
    {
      "name": "GitLab",
      "configuration": {
        "url": "https://gitlab.mycompagny.fr",
        "token": "myGitlabUserToken",
        "additional_query": "&search=mygroup&starred=true",
        "numberOfPipelinesPerProject": 3,
        "slugs": [
          {
            "project": "mygroup/myproject",
            "ref": "master"
          },
          {
            "project": "mygroup/myproject",
            "ref": "develop"
         }
        ]
      }
    }
  ]
}

but I have no results on the website and in my docker logs I get :

$ docker logs --tail all node-build-monitor

warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
9:32:37 AM | Check for builds...
9:32:37 AM | 0 builds found....
node-build-monitor 0.9.24 is listening on port 3000
9:33:07 AM | Check for builds...
9:33:07 AM | 0 builds found....

For information, my Gitlab uses a self-signed certificate.

Thank you for your help ;)

marcells · 2017-10-21T11:35:31Z

@datakurre Do you have any idea what could be wrong with the configuration?

marcells · 2017-10-23T19:32:16Z

@aborderon Could you try to debug the app to see what could be wrong?

aborderon · 2017-10-30T09:44:32Z

Yes @marcells , I found the problem, this is the self-signed certificate that I use with Gitlab.

In the request.js, the rejectUnauthorized property to false does not work.

I managed to access my GitLab builds by adding the line just below the exports module of GitLab.js but it is not an acceptable resolution :
module.exports = function () { process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

Do you have a better solution?

marcells · 2017-10-30T19:42:11Z

Hm, that's just an environment variable. Please remove your change from GitLab.js and try the following.

If you use the executable, just set it in your shell before starting the build-monitor. If you use docker, then take a look here how to define an environment variable.

Please let me know, if it worked.

aborderon · 2017-10-31T08:02:36Z

Hello, thank you for your answer. I run node-build-monitor with docker with the following command and it work:

docker run -d -p 3000:3000 -e NODE_TLS_REJECT_UNAUTHORIZED=0 --name node-build-monitor node-build-monitor

It would be necessary to add documentation for self signed certificates I think.

I will try to make a pull request to adding docker-compose support. I would take this opportunity to add a configuration with self signed certificates.

Thanks again !

marcells · 2017-10-31T08:32:07Z

Nice to hear! I did update the docs right now. Feel free to make a PR for docker-compose support.

ElinMagnusson · 2017-11-07T13:29:43Z

Can I somehow set NODE_TLS_REJECT_UNAUTHORIZED=0 when running the standalone version?

Or can you update the standalone version with this setting?

I tried setting it as a Windows environment variable but I still get 0 builds found...

marcells · 2017-11-07T20:47:22Z

Hm, that should work. At least for the Linux build I tested it.

Did you set it on cmd with set NODE_TLS_REJECT_UNAUTHORIZED=0 before starting node-build-monitor-win.exe from the same cmd session?

I did create a new version right now, which outputs the important environment variables, when you start the monitor.

ElinMagnusson · 2017-11-08T06:47:30Z

Hi Marcells, thank for your reply!

Yes I tried that and the variable is printed and set to 0:

Printing environment Variables...
    PORT = unset (Default: 3000)
    NODE_TLS_REJECT_UNAUTHORIZED = 0
node-build-monitor is starting...
07:39:59 | Check for builds...
node-build-monitor 0.9.27 is listening on port 3000...

Now I instead get "check for builds.." and "node-build-monitor is listening on port ... " but there is no message about number of builds?

With version 9.2 I get

07:39:44 | Check for builds...
07:39:44 | 0 builds found....
node-build-monitor 0.9.20 is listening on port 3000

marcells · 2017-11-08T07:02:37Z

So there was a response with 0 builds now. Could it be, that your configuration is wrong?

kasperschnack · 2019-07-22T16:59:35Z

Hi I'm having this same problem. The server is running but I can't see in any logs why no builds are fetched. Only output I git from docker-compose logs is this:

docker-compose logs
Attaching to docker_node-build-monitor_1
node-build-monitor_1  | warn:    --minUptime not set. Defaulting to: 1000ms
node-build-monitor_1  | warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
node-build-monitor_1  | error: Could not read .foreverignore file.
node-build-monitor_1  | error: ENOENT: no such file or directory, open '/build-mon/app/.foreverignore'
node-build-monitor_1  | Printing environment Variables...
node-build-monitor_1  |     PORT = unset (Default: 3000)
node-build-monitor_1  |     NODE_TLS_REJECT_UNAUTHORIZED = unset (Default: 1)
node-build-monitor_1  | node-build-monitor is starting...
node-build-monitor_1  | node-build-monitor 0.9.55 is listening on port 3000...

I've tried setting NODE_TLS_REJECT_UNAUTHORIZED: 0 under service: node-build-monitor: environment in docker-compose.with-tfs-proxy.yml. Still nothing happens :/. My config looks like this:

{
  "monitor": {
    "interval": 3000,
    "latestBuildOnly": true,
    "sortOrder": "date",
    "debug": false
  },
  "services": [
    {
      "name": "GitLab",
      "configuration": {
        "url": "<company-Gitlab-url>",
        "token": "<api-token>",
        "numberOfPipelinesPerProject": 3,
        "pipeline": {
          "status": ["running", "pending", "success", "failed", "canceled", "skipped"]
        }
      }
    }
  ]
}

Any idea what I could be doing wrong?

Ok it seems i was using the wrong kind of token (readonly before - now api). No builds appear on the server but at least now i get an error:

docker [master●] % docker-compose logs
Attaching to docker_node-build-monitor_1
node-build-monitor_1  | warn:    --minUptime not set. Defaulting to: 1000ms
node-build-monitor_1  | warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
node-build-monitor_1  | error: Could not read .foreverignore file.
node-build-monitor_1  | error: ENOENT: no such file or directory, open '/build-mon/app/.foreverignore'
node-build-monitor_1  | Printing environment Variables...
node-build-monitor_1  |     PORT = unset (Default: 3000)
node-build-monitor_1  |     NODE_TLS_REJECT_UNAUTHORIZED = unset (Default: 1)
node-build-monitor_1  | node-build-monitor is starting...
node-build-monitor_1  | node-build-monitor 0.9.55 is listening on port 3000...
node-build-monitor_1  | /build-mon/app/services/GitLab.js:46
node-build-monitor_1  |                     pipelines = pipelines.filter(function(pipeline) {
node-build-monitor_1  |                                           ^
node-build-monitor_1  |
node-build-monitor_1  | TypeError: pipelines.filter is not a function
node-build-monitor_1  |     at /build-mon/app/services/GitLab.js:46:43
node-build-monitor_1  |     at Request._callback (/build-mon/app/services/GitLab.js:36:17)
node-build-monitor_1  |     at Request.self.callback (/build-mon/node_modules/request/request.js:185:22)
node-build-monitor_1  |     at emitTwo (events.js:106:13)
node-build-monitor_1  |     at Request.emit (events.js:194:7)
node-build-monitor_1  |     at Request.<anonymous> (/build-mon/node_modules/request/request.js:1161:10)
node-build-monitor_1  |     at emitOne (events.js:96:13)
node-build-monitor_1  |     at Request.emit (events.js:191:7)
node-build-monitor_1  |     at IncomingMessage.<anonymous> (/build-mon/node_modules/request/request.js:1083:12)
node-build-monitor_1  |     at Object.onceWrapper (events.js:293:19)
node-build-monitor_1  | error: Forever detected script exited with code: 1
node-build-monitor_1  | error: Script restart attempt #1
node-build-monitor_1  | Printing environment Variables...
node-build-monitor_1  |     PORT = unset (Default: 3000)
node-build-monitor_1  |     NODE_TLS_REJECT_UNAUTHORIZED = unset (Default: 1)
node-build-monitor_1  | node-build-monitor is starting...
node-build-monitor_1  | node-build-monitor 0.9.55 is listening on port 3000...
node-build-monitor_1  | /build-mon/app/services/GitLab.js:46
node-build-monitor_1  |                     pipelines = pipelines.filter(function(pipeline) {
node-build-monitor_1  |                                           ^
node-build-monitor_1  |

marcells added the question label Oct 30, 2017

aborderon closed this as completed Oct 31, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

0 buils founds with GitLab #79

0 buils founds with GitLab #79

aborderon commented Oct 5, 2017

marcells commented Oct 21, 2017

marcells commented Oct 23, 2017

aborderon commented Oct 30, 2017

marcells commented Oct 30, 2017

aborderon commented Oct 31, 2017

marcells commented Oct 31, 2017

ElinMagnusson commented Nov 7, 2017

marcells commented Nov 7, 2017 •

edited

Loading

ElinMagnusson commented Nov 8, 2017

marcells commented Nov 8, 2017

kasperschnack commented Jul 22, 2019 •

edited

Loading

0 buils founds with GitLab #79

0 buils founds with GitLab #79

Comments

aborderon commented Oct 5, 2017

marcells commented Oct 21, 2017

marcells commented Oct 23, 2017

aborderon commented Oct 30, 2017

marcells commented Oct 30, 2017

aborderon commented Oct 31, 2017

marcells commented Oct 31, 2017

ElinMagnusson commented Nov 7, 2017

marcells commented Nov 7, 2017 • edited Loading

ElinMagnusson commented Nov 8, 2017

marcells commented Nov 8, 2017

kasperschnack commented Jul 22, 2019 • edited Loading

marcells commented Nov 7, 2017 •

edited

Loading

kasperschnack commented Jul 22, 2019 •

edited

Loading