Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: exclude npm test directories on Windows #23001

Merged
merged 1 commit into from
Oct 2, 2018

Conversation

richardlau
Copy link
Member

npm test directories are excluded on other platforms by
tools/install.py. Do the same on Windows.

Fixes: #22901

Checklist

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. windows Issues and PRs related to the Windows platform. labels Sep 21, 2018
@richardlau
Copy link
Member Author

For reference, this is the relevant bit of tools/install.py that excludes the test directories:

node/tools/install.py

Lines 84 to 89 in 058c5b8

# npm has a *lot* of files and it'd be a pain to maintain a fixed list here
# so we walk its source directory instead...
for dirname, subdirs, basenames in os.walk('deps/npm', topdown=True):
subdirs[:] = filter('test'.__ne__, subdirs) # skip test suites
paths = [os.path.join(dirname, basename) for basename in basenames]
action(paths, target_path + dirname[9:] + '/')

@@ -332,7 +332,7 @@ copy /Y ..\README.md node-v%FULLVERSION%-win-%target_arch%\ > nul
if errorlevel 1 echo Cannot copy README.md && goto package_error
copy /Y ..\CHANGELOG.md node-v%FULLVERSION%-win-%target_arch%\ > nul
if errorlevel 1 echo Cannot copy CHANGELOG.md && goto package_error
robocopy /e ..\deps\npm node-v%FULLVERSION%-win-%target_arch%\node_modules\npm > nul
robocopy ..\deps\npm node-v%FULLVERSION%-win-%target_arch%\node_modules\npm /e /xd test > nul
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

robocopy documentation has the syntax as robocopy <Source> <Destination> [<File>[ ...]] [<Options>] so I've moved the existing option (/e) to the end of the command line in addition to the new option to exclude test directories.

@richardlau
Copy link
Member Author

cc @nodejs/build-files @nodejs/platform-windows @nodejs/npm

@richardlau
Copy link
Member Author

Also note this is going to be tricky to test as the regular CI doesn't build the installer/7z/zip packages.

@joyeecheung
Copy link
Member

There is a https://github.com/nodejs/build/blob/master/jenkins/xml/smoketest-release.xml in the build repo, I wonder what it's for...can we use it? Is it somewhere on Jenkins?

@richardlau
Copy link
Member Author

There is a https://github.com/nodejs/build/blob/master/jenkins/xml/smoketest-release.xml in the build repo, I wonder what it's for...can we use it? Is it somewhere on Jenkins?

Not (as far as I can see) on https://ci.nodejs.org/view/All/. Maybe it's on ci-release (which I don't have access to)?

@refack
Copy link
Contributor

refack commented Sep 21, 2018

Any chance we can make install.py windows compatible instead?

nodejs/build:jenkins/xml/smoketest-release.xml@master

Landed under the title jenkins: add job config files for deleted jobs... Which makes sense since the fragile bits in ci-release are WRT to firewalls, certificates, and the specific workers that are mapped to it.

I triggered a test build https://ci-release.nodejs.org/job/iojs+release/3779/

@richardlau
Copy link
Member Author

Any chance we can make install.py windows compatible instead?

It's certainly possible but it's not a one line change. We'd have to take into account the differences between the directory layouts on Windows vs the Unix-like platforms and things like symlinks not being used on Windows. Also even though I know it's not a supported platform I wonder if changing install.py for Windows would affect mingw/msys.

#22901 (comment)

@richardlau
Copy link
Member Author

I triggered a test build https://ci-release.nodejs.org/job/iojs+release/3779/

Thanks. Could you, or someone else who has access the release ci report back on the results when the build completes?

@refack
Copy link
Contributor

refack commented Sep 21, 2018

No /test/ in npm
node-v11.0.0-rc.0-win-x64.zip

7z l node-v11.0.0-rc.0-win-x64.zip | grep "x64/node_modules/npm/[^/]*$"
2018-05-26 02:00:21 ....A         3258         1471  node-v11.0.0-rc.0-win-x64/node_modules/npm/.mailmap
2018-08-03 02:00:25 ....A          350          195  node-v11.0.0-rc.0-win-x64/node_modules/npm/.npmignore
2018-05-26 02:00:21 ....A         1228          529  node-v11.0.0-rc.0-win-x64/node_modules/npm/.travis.yml
2018-05-24 13:56:30 ....A          993          598  node-v11.0.0-rc.0-win-x64/node_modules/npm/appveyor.yml
2018-09-03 06:00:20 ....A        23475         9843  node-v11.0.0-rc.0-win-x64/node_modules/npm/AUTHORS
2018-09-03 06:00:20 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/bin
2018-09-03 06:00:20 ....A        61603        20601  node-v11.0.0-rc.0-win-x64/node_modules/npm/CHANGELOG.md
2018-05-26 02:00:21 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/changelogs
2018-05-24 13:56:30 ....A          554          337  node-v11.0.0-rc.0-win-x64/node_modules/npm/configure
2018-09-03 06:00:20 ....A         4566         1715  node-v11.0.0-rc.0-win-x64/node_modules/npm/CONTRIBUTING.md
2018-05-24 13:56:30 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/doc
2018-09-03 06:00:20 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/html
2018-09-03 06:00:20 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/lib
2018-05-24 13:56:30 ....A         9977         3524  node-v11.0.0-rc.0-win-x64/node_modules/npm/LICENSE
2018-05-24 13:56:30 ....A          159          123  node-v11.0.0-rc.0-win-x64/node_modules/npm/make.bat
2018-05-26 02:00:21 ....A         5802         1469  node-v11.0.0-rc.0-win-x64/node_modules/npm/Makefile
2018-05-24 13:56:30 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/man
2018-09-03 06:00:21 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/node_modules
2018-09-03 06:00:21 ....A         7671         2218  node-v11.0.0-rc.0-win-x64/node_modules/npm/package.json
2018-09-03 06:00:20 ....A         4871         2144  node-v11.0.0-rc.0-win-x64/node_modules/npm/README.md
2018-09-03 06:00:21 D....            0            0  node-v11.0.0-rc.0-win-x64/node_modules/npm/scripts

@richardlau
Copy link
Member Author

I realised on the way home that this change only affects the 7z/zip packages. Will need to look at the WiX files to work out if we can do the equivalent for the msi installer.

@richardlau
Copy link
Member Author

I think this is the bit that generates the npm files for WiX:

<HeatDirectory ToolPath="$(WixToolPath)" Directory="..\..\..\deps\npm" PreprocessorVariable="var.NpmSourceDir" DirectoryRefId="NodeModulesFolder" ComponentGroupName="NpmSourceFiles" GenerateGuidsNow="true" SuppressFragments="false" OutputFile="..\..\..\npm.wxs" RunAsSeparateProcess="true">

@refack
Copy link
Contributor

refack commented Sep 22, 2018

I think this is the bit that generates the npm files for WiX:

I think it should work off the directory generated by the :package label, i.e. node-v%FULLVERSION%-win-%target_arch%\node_modules\npm

P.S. I just checked, the msi does indeed contain /npm/test/

@richardlau
Copy link
Member Author

Yes, I think working off the directory created for :package will be simpler than the official way to exclude files/directories with heatwhich is to use XSLT (which I fear would scare off even more contributors from the Windows install build files). Would need some refactoring as currently you can skip package and go to msi in which case the directory would not be created.

@addaleax
Copy link
Member

I realised on the way home that this change only affects the 7z/zip packages. Will need to look at the WiX files to work out if we can do the equivalent for the msi installer.

@richardlau Is this WIP? I’m adding the label but please remove it if I’m mistaken about that.

@addaleax addaleax added the wip Issues and PRs that are still a work in progress. label Sep 24, 2018
@richardlau
Copy link
Member Author

I realised on the way home that this change only affects the 7z/zip packages. Will need to look at the WiX files to work out if we can do the equivalent for the msi installer.

@richardlau Is this WIP? I’m adding the label but please remove it if I’m mistaken about that.

Yes, thanks. I don't think we should merge this unless the contents of the msi installer match the 7z/zip packages.

@joaocgreis
Copy link
Member

@richardlau thanks for working on this! The relevant upstream issue is wixtoolset/issues#4023, so there is no easy way to exclude the tests with Heat. It should be easy to get the npm folder from the package folder instead of deps, but vcbuild needs to be adapted to have a common section for package and msi that runs this robocopy line.

@richardlau richardlau removed the wip Issues and PRs that are still a work in progress. label Sep 25, 2018
@richardlau
Copy link
Member Author

richardlau commented Sep 25, 2018

Updated:

  • split part of :package to a :stage_package step that is run if either msi or package is set
  • replace references to ..\..\..\deps\npm with ..\..\..\Release\node-v$(FullVersion)-win-$(Platform)\node_modules\npm in tools/msvs/msi/nodemsi.wixproj. Note that the existing :package step always staged in Release but there should be no difference wrt npm for debug/release and x64/x86 configurations (i.e. even the debug configurations reference Release to pick up the staged npm) so I've left it always staging in Release.

I gave this a quick build/install locally and no npm and/or npm dependency test directories were installed. If this looks okay, please could someone with access to the release CI do a test build for others to try?

@danbev
Copy link
Contributor

danbev commented Sep 26, 2018

@richardlau richardlau added install Issues and PRs related to the installers. npm Issues and PRs related to the npm client dependency or the npm registry. labels Sep 26, 2018
@joaocgreis joaocgreis added the semver-major PRs that contain breaking changes and should be released in the next major version. label Sep 27, 2018
@joaocgreis
Copy link
Member

This should be semver-major. While I can't think of a good reason anything would break, we are removing files from the published packages and installer. This already has the necessary TSC reviews, unless @joyeecheung or @jasnell withdraw their approvals.

Copy link
Member

@joyeecheung joyeecheung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still LGTM

@richardlau
Copy link
Member Author

richardlau commented Sep 27, 2018

@richardlau
Copy link
Member Author

This should be semver-major. While I can't think of a good reason anything would break, we are removing files from the published packages and installer. This already has the necessary TSC reviews, unless @joyeecheung or @jasnell withdraw their approvals.

@jasnell I added a second commit for the msi installer after your approval; does this still look good to you?

The most recent resume CI is green, so I'd like to land this early next week to make the semver-major cutoff for v11.x (#22180 (comment)).

cc @nodejs/tsc (as per https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md#involving-the-tsc since this is defensively semver-major).

npm test directories are excluded on other platforms by
`tools/install.py`. Do the same on Windows.

Fixes: nodejs#22901

PR-URL: nodejs#23001
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: João Reis <reis@janeasystems.com>
@richardlau richardlau merged commit b3b3f53 into nodejs:master Oct 2, 2018
@richardlau
Copy link
Member Author

Landed in b3b3f53.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI. install Issues and PRs related to the installers. npm Issues and PRs related to the npm client dependency or the npm registry. semver-major PRs that contain breaking changes and should be released in the next major version. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build: windows releases should not include npm tests
8 participants