[TIMOB-19804] Windows: Modify Windows SDK build process to grab and use JavaScriptCore from a URL
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2015-11-03T17:26:58.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 5.1.0 |
| Components | Tooling, Windows |
| Labels | n/a |
| Reporter | Christopher Williams |
| Assignee | Christopher Williams |
| Created | 2015-10-27T14:00:24.000+0000 |
| Updated | 2015-11-17T01:45:36.000+0000 |
Description
Our current build for Windows SDK assumes we have a pre-built JSC installed on the machine and an environment variable pointing at it. This means that we have to VPN and RDP into the build agents to set up a new/different JSC build to use - grab the zip, unzip it, and then change the environment variable JavaScriptCore_HOME to point at the new folder. This means we can't try out new versions of JSC in a new build or PR.
We should change the build scripts (in groovy and/or the node scripts) to be able to point at a new JSC build URL to use for the build - so that we can make PRs that update JSC and see if the build/tests pass, and so that we eliminate the manual steps in setting up the build.
Closing ticket