BXMSPROD-1558 installing @kie/lock-treatment-tool using npx

[Ginxo]

https://issues.redhat.com/browse/BXMSPROD-1558

referenced pull requests:

• BXMSPROD-1558 using @kie/lock-treatment-tool kogito-editors-java#183
• [BXMSPROD-1558] @kie scope added kie-ci#1175
• [BXMSPROD-1558] @kie scope added lock-treatment-tool#1
• BXMSPROD-1558 documentation adapted lock-treatment-tool#2
• BXMSPROD-1558 using @kie/lock-treatment-tool kogito-editors-java#183
• https://github.com/kiegroup/kogito-apps/pull/1139
• BXMSPROD-1558 installing @kie/lock-treatment-tool using npx optaweb-employee-rostering#729
• BXMSPROD-1558 installing @kie/lock-treatment-tool using npx #612
• BXMSPROD-1558 installing @kie/lock-treatment-tool using npx process-migration-service#36

[kie-ci]

The (build) optaweb-vehicle-routing check has failed. Please check the logs.

[yurloc]

[2021-12-02T09:34:44.130Z] [INFO] --- frontend-maven-plugin:1.10.0:install-node-and-npm (install node and npm) @ optaweb-vehicle-routing-frontend ---
[2021-12-02T09:34:44.697Z] [INFO] Installing node version v12.16.2
[2021-12-02T09:34:44.697Z] [INFO] Downloading http://download.devel.redhat.com/rcm-guest/staging/rhba/dist/node/v12.16.2/node-v12.16.2-linux-x64.tar.gz to /home/jenkins/.m2/repository/com/github/eirslett/node/12.16.2/node-12.16.2-linux-x64.tar.gz
[2021-12-02T09:34:44.697Z] [INFO] No proxies configured
[2021-12-02T09:34:44.697Z] [INFO] No proxy was configured, downloading directly
[2021-12-02T09:34:47.972Z] [INFO] Unpacking /home/jenkins/.m2/repository/com/github/eirslett/node/12.16.2/node-12.16.2-linux-x64.tar.gz into /home/jenkins/workspace/KIE/kogito/main/pullrequest/optaweb-vehicle-routing.tests.optaweb-vehicle-routing/bc/kiegroup_optaweb_vehicle_routing/optaweb-vehicle-routing/optaweb-vehicle-routing-frontend/node/tmp
[2021-12-02T09:34:49.869Z] [INFO] Copying node binary from /home/jenkins/workspace/KIE/kogito/main/pullrequest/optaweb-vehicle-routing.tests.optaweb-vehicle-routing/bc/kiegroup_optaweb_vehicle_routing/optaweb-vehicle-routing/optaweb-vehicle-routing-frontend/node/tmp/node-v12.16.2-linux-x64/bin/node to /home/jenkins/workspace/KIE/kogito/main/pullrequest/optaweb-vehicle-routing.tests.optaweb-vehicle-routing/bc/kiegroup_optaweb_vehicle_routing/optaweb-vehicle-routing/optaweb-vehicle-routing-frontend/node/node
[2021-12-02T09:34:49.869Z] [INFO] Installed node locally.
[2021-12-02T09:34:49.869Z] [INFO] Installing npm version 6.14.4
[2021-12-02T09:34:49.869Z] [INFO] Downloading http://download.devel.redhat.com/rcm-guest/staging/rhba/dist/npm/npm-6.14.4.tgz to /home/jenkins/.m2/repository/com/github/eirslett/npm/6.14.4/npm-6.14.4.tar.gz
[2021-12-02T09:34:49.869Z] [INFO] No proxies configured
[2021-12-02T09:34:49.869Z] [INFO] No proxy was configured, downloading directly
[2021-12-02T09:34:50.801Z] [INFO] Unpacking /home/jenkins/.m2/repository/com/github/eirslett/npm/6.14.4/npm-6.14.4.tar.gz into /home/jenkins/workspace/KIE/kogito/main/pullrequest/optaweb-vehicle-routing.tests.optaweb-vehicle-routing/bc/kiegroup_optaweb_vehicle_routing/optaweb-vehicle-routing/optaweb-vehicle-routing-frontend/node/node_modules
[2021-12-02T09:34:51.732Z] [INFO] Installed npm locally.
[2021-12-02T09:34:51.732Z] [INFO]

Everything works as usual up to this point. But the following execution fails:

[2021-12-02T09:34:51.732Z] [INFO] --- frontend-maven-plugin:1.10.0:npx (lock-treatment-tool execution) @ optaweb-vehicle-routing-frontend ---
[2021-12-02T09:34:51.732Z] [INFO] Running 'npx @kie/lock-treatment-tool -- --registry=https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org/' in /home/jenkins/workspace/KIE/kogito/main/pullrequest/optaweb-vehicle-routing.tests.optaweb-vehicle-routing/bc/kiegroup_optaweb_vehicle_routing/optaweb-vehicle-routing/optaweb-vehicle-routing-frontend
[2021-12-02T09:36:13.148Z] [INFO] npm ERR! code ECONNREFUSED
[2021-12-02T09:36:13.148Z] [INFO] npm ERR! errno ECONNREFUSED
[2021-12-02T09:36:13.148Z] [INFO] npm ERR! FetchError: request to https://registry.npmjs.org/@kie%2flock-treatment-tool failed, reason: connect ECONNREFUSED 104.16.23.35:443

[yurloc]

@Ginxo I'm really not sure but maybe we're hitting eirslett/frontend-maven-plugin#1005 again. If that's the case, then the frontend plugin passes --registry=http://... as an argument to lock-treatment-tool instead of making it an option of the npx command.

Alternatively, the culprit might not be the frontend plugin but simply the -- at the end of <arguments>@kie/lock-treatment-tool --</arguments> which maybe turn the --registry option into an argument.

[Ginxo]

replaced by kiegroup/kogito-editors-java#184