Project

General

Profile

Refactor #17406

upgrade packages to use nodejs version 4.x

Added by Tomer Brisker about 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Debian/Ubuntu
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

some of the infrastructure (el7, jessie, trusty) uses nodejs v0.10, which is EOL.
All supported OSes can provide version >= 4.x using either epel or nodesource, which are supported and support es6 syntax.
This will also likely improve speed of asset compilation.

Associated revisions

Revision c4945cbb (diff)
Added by Michael Moll about 4 years ago

fixes #17406 - use nodejs >= 4.2

History

#1 Updated by Anonymous about 4 years ago

I opened https://github.com/theforeman/foreman-infra/pull/258 for adding the apt repos to the builders where needed and https://github.com/theforeman/foreman-packaging/pull/1421 for the DEB packaging part.

For the RPM part: EPEL does bring node 6.x now, so that should be a "yum update" and I think it would be good to have updated nodes in general, anyway... Then the version can get raised in the RPM specs also.

It's currently not possible to go to 6.x on Debian/Ubuntu, as nodesource does not provide aarch64 builds.

#2 Updated by Dominic Cleal about 4 years ago

  • Assignee set to Anonymous
  • Project changed from Foreman to Packaging
  • Subject changed from upgrade infrastructure to use supported nodejs versions to upgrade packages to use nodejs version 4.x
  • Category changed from Packaging to Debian/Ubuntu
  • Status changed from New to Ready For Testing
  • Legacy Backlogs Release (now unused) set to 189

#3 Updated by Dominic Cleal about 4 years ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/1421 added

#4 Updated by Anonymous about 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF