As fungi pointed out maybe an easy solution is to replace the nodejs4-publish-to-npm job to nodejs8-publish-to-npm [1].

Reviews are welcome :)

[1] https://review.opendev.org/c/openstack/project-config/+/781536

Előd

On 2021. 03. 16. 10:34, Herve Beraud wrote:

Here is a summary from our previous meeting [1] related to this topic.

Apparently the error is caused by the old version of nodejs [2] (usually lower than v6).

This error is on an independent project [3] so normally the NodeJS supported runtimes are the same that with the current series (AFAIK we use NodeJS 10) [4]

This job uses xenial and xenial seems to provide nodejs 4.2.6 [5] that could explain why we see this error.

However, this job inherits from `publish-openstack-artifacts` [6] and this one defines a nodeset based on focal [7] so I wonder why we use xenial here [8].

Notice that focal comes with NodeJS 10.19 [4].

The last execution of this job (`release-openstack-javascript`) was successful but it was 18 months ago [9], unfortunately logs aren't longer available for these builds.

It could be worth seeing which version of ubuntu was used during this period.

Maybe the solution is simply moving this javascript job onto a nodeset based on focal.

Thoughts?

[1] eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-03-11-17.00.log.html#l-186

[2] https://stackoverflow.com/questions/64414716/unexpected-token-in-yarn-installation

[3] https://releases.openstack.org/reference/release_models.html#independent

[4] https://governance.openstack.org/tc/reference/runtimes/wallaby.html#node-js-runtime-for-wallaby

[5] https://pkgs.org/search/?q=nodejs

[6] https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L780

[7] https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L8

[8] https://zuul.opendev.org/t/openstack/build/cdffd2a26a0d4a5b8137edb392fa5971/log/job-output.txt#743

[9] https://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-javascript

Le jeu. 11 mars 2021 à 12:42, Thierry Carrez <thierry@openstack.org> a écrit :

We had a release job failure during the processing of the tag event when
1.3.0 was (successfully) pushed to openstack/monasca-grafana-datasource.

Tags on this repository trigger the release-openstack-javascript job,
which failed during pre playbook when trying to run yarn --version with
the following error:

/usr/share/yarn/lib/cli.js:46100
   let {
       ^

SyntaxError: Unexpected token {
     at exports.runInThisContext (vm.js:53:16)
     at Module._compile (module.js:373:25)
     at Object.Module._extensions..js (module.js:416:10)
     at Module.load (module.js:343:32)
     at Function.Module._load (module.js:300:12)
     at Module.require (module.js:353:17)
     at require (internal/module.js:12:17)
     at Object.<anonymous> (/usr/share/yarn/bin/yarn.js:24:13)
     at Module._compile (module.js:409:26)
     at Object.Module._extensions..js (module.js:416:10)

See https://zuul.opendev.org/t/openstack/build
/cdffd2a26a0d4a5b8137edb392fa5971

This prevented the job from running (likely resulting in nothing being
uploaded to NPM? Not a JS job specialist), which in turn prevented
announce-release job from announcing it.

--
Thierry Carrez (ttx)

--

Hervé Beraud

Senior Software Engineer at Red Hat

irc: hberaud

https://github.com/4383/

https://twitter.com/4383hberaud

-----BEGIN PGP SIGNATURE-----

wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+
Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+
RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP
F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G
5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g
glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw
m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ
hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0
qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y
F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3
B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O
v6rDpkeNksZ9fFSyoY2o
=ECSj
-----END PGP SIGNATURE-----