Also:
- warn the user about a possible delay after restart
- let the user know when installation is done
Signed-off-by: Eric Promislow <epromislow@suse.com>
- A reboot is needed when installing, and the continuation
needs to be run as admin, so write a sudo-style helper
to pull the command out of the registry and run it that way
- Putting a command in the RunOnce key didn't fire on restart, so
I'm manually managing the key instead
Signed-off-by: Eric Promislow <epromislow@suse.com>
There's no need to update Visual Studio when running on GitHub Actions
(because it already have the necessary parts); allow skipping it to reduce
the time CI takes.
We also don't need the tools; we manually install NodeJS & Python, and the
VM comes with git.
Signed-off-by: Mark Yen <mark.yen@suse.com>
Python 2.7 is long obsolete, but node-gyp still wants it. This means that
attempting to install it displays a deprecation warning; PowerShell will
see this warning (on stderr) and assume it means that the command
failed. Work around this by redirecting stderr for that command, and
instead letting exit statuses control failure detection.
Signed-off-by: Mark Yen <mark.yen@suse.com>
Stop assuming where Visual Studio is installed (instead, try to detect any
of the available installations). Also, try to run everything in parallel,
but in a way such that each individual task is in a readable block.
Signed-off-by: Mark Yen <mark.yen@suse.com>
Also, fix npm configuration - we don't have npm available in this shell
(because environment changes only get picked up upon restarting the shell).
Signed-off-by: Mark Yen <mark.yen@suse.com>
- Also install VC tools, otherwise node-gyp doesn't seem to work.
- Force MSBuild path in NPM.
- Install Git via scoop too, since we can't seem to find the MSVS version.
Signed-off-by: Mark Yen <mark.yen@suse.com>
It looks like my attempt to set the $PATH didn't work out; it's much easier
to just use the Python from scoop instead.
Signed-off-by: Mark Yen <mark.yen@suse.com>
This is an initial implementation; it doesn't do any checking and any error
will probably break things badly. This should probably only be used by the
Windows 10 development VM that is distributed by Microsoft.
Signed-off-by: Mark Yen <mark.yen@suse.com>
