github/atom
1
1
Fork 0
mirror of https://github.com/atom/atom.git synced 2026-01-14 17:38:03 -05:00
Code Issues Packages Projects Releases Wiki Activity
36,579 Commits 140 Branches 571 Tags
cfba94e4e459d2fdcb4857af362a35b03e5ff109
Commit Graph

1222 Commits

Author SHA1 Message Date
Winston Liu
cfba94e4e4 Undebugify 2019-05-07 23:31:37 -04:00
Winston Liu
33be2276a4 ⬆️ apm@2.2.2-1 to remove bundled node.exe 2019-05-07 21:12:39 -04:00
Winston Liu
a6eabb2ae4 Log apm install output 2019-05-07 20:35:25 -04:00
Winston Liu
d0265096fd 🎨 debug message 2019-05-07 20:02:54 -04:00
Winston Liu
a960367364 Pray tell, what is our arch? 2019-05-07 15:40:38 -04:00
Winston Liu
7512da8f3d Okay, add it to the end 2019-05-07 15:29:04 -04:00
Winston Liu
ee9deacb48 Try running with verbose 2019-05-07 15:20:34 -04:00
Rafael Oleza
682fa45e36 Ignore some non-essential packages from the startup script 2019-04-25 18:00:44 +02:00
Rafael Oleza
4ceebe8a98 ⬆️ electron-link@0.4.0 2019-04-25 16:47:29 +02:00
Ash Wilson
57e4931206 ⬆️ electron-link@0.3.3 2019-04-22 21:05:24 -04:00
Jason Rudolph
f3f32c45cc Merge pull request #19176 from atom/respect-package-lock-on-ci 
Teach CI to use versions specified in package-lock.json
 2019-04-19 17:13:38 -04:00
Nathan Sobo
406e033323 Merge pull request #19183 from atom/ns/upload-windows-crashes-on-release-branches 
On Azure DevOps, upload Windows crash dumps to S3 on release branches
 2019-04-19 13:52:47 -06:00
Nathan Sobo
4bc43eb358 On Azure DevOps, upload Windows crash dumps to S3 on release branches 
On release branches, we can't upload crash dumps because they will leak
secret environment variables. So instead we will upload them to our S3
bucket with 'private' ACL. They can then be manually retrieved via the
AWS CLI with our private credentials.
 2019-04-18 17:04:49 -06:00
Nathan Sobo
7ef8f06cd2 Only upload Windows crash reports if the S3 key environment var is null 
This seems like a more robust test than the isRelease variable I was
testing previously. Our goal is to not leak secrets such as the S3 key,
so this is a more direct test of that.
 2019-04-18 15:15:31 -06:00
Nathan Sobo
b03d49973e On Azure DevOps, publish crash reports on non-release Windows branches 
Since we don't expose sensitive information on these branches, we can
use the regular artifact publishing mechanism
 2019-04-18 10:49:14 -06:00
Jason Rudolph
fce5a8974f Fix issue upgrading npm & use upgraded version 2019-04-18 10:59:33 -04:00
Jason Rudolph
cb3f24fc5c Use env var to specify path to npm binary 2019-04-18 09:53:40 -04:00
Jason Rudolph
680e48485a Set PATH so that Azure DevOps macOS builds use correct npm 
Before we run script/bootstrap on the macOS build, the preceding build
step installs npm 6.2.0 as the global npm version. It installs npm at
`/usr/local/bin/npm`. However, a _different_ version of npm appears
earlier in the PATH. The PATH looks like this:

```
/Users/vsts/hostedtoolcache/node/8.9.3/x64/bin:
/usr/local/lib/ruby/gems/2.6.0/bin:
/usr/local/opt/ruby/bin:
/usr/local/opt/curl/bin:
/usr/local/bin:
/usr/local/sbin:
/Users/vsts/bin:
/Users/vsts/.yarn/bin:
/usr/local/go/bin:
/Users/vsts/Library/Android/sdk/tools:
/Users/vsts/Library/Android/sdk/platform-tools:
/Users/vsts/Library/Android/sdk/ndk-bundle:
/Library/Frameworks/Mono.framework/Versions/Current/Commands:
/usr/bin:
/bin:
/usr/sbin:
/sbin:
/Users/vsts/.azcopy
```

There's an npm executable at
/Users/vsts/hostedtoolcache/node/8.9.3/x64/bin/npm.

To get the build to use the global version of npm, this commit puts
/usr/local/bin at the beginning of the PATH.
 2019-04-17 17:27:32 -04:00
Jason Rudolph
ce94241bde Configure Azure DevOps bootstrapping step to run with CI env vars 2019-04-17 12:23:05 -04:00
Jason Rudolph
4980439f0c Require npm 6+ on CI 
This change will allow us to use `npm ci` instead of `npm install` on 
CI, so that we can respect the package-lock.json file.
 2019-04-17 11:48:28 -04:00
Rafael Oleza
91558332de Add debugging message specifying which step failed 2019-04-12 12:53:20 +02:00
Rafael Oleza
a7ac4a2147 Change the way exitCodes are passed from the test steps 2019-04-12 12:52:55 +02:00
Ash Wilson
ae5b1eb680 Exclude superstring from any dependency path 2019-04-08 13:49:09 -04:00
David Wilson
9ef6477b92 Temporarily disable draft release creation on release branches 2019-04-05 15:01:28 -07:00
Jason Rudolph
9e03795c20 Provide the BUILD_ARCH env var for bootstrapping Windows env on VSTS 
`script/vsts/windows-run.js` checks the BUILD_ARCH env var, so let's 
make sure it's populated.
 2019-04-03 13:11:24 -04:00
Jason Rudolph
166658f588 Add back bootstrapping to script/build on Windows 
Hopefully this will resolve the error we're seeing here:

https://github.visualstudio.com/Atom/_build/results?buildId=37021&view=logs&jobId=97a617bf-bcbd-5dfa-bba2-cfba2747b693&taskId=1e1369e9-1c56-59b0-830c-f1606a680c8a&lineStart=13&lineEnd=19&colStart=1&colEnd=1

🤞
 2019-04-02 19:43:45 -04:00
Jason Rudolph
5f52a8e0b0 Lint earlier in the build process 2019-04-02 19:43:44 -04:00
Rafael Oleza
3bfec7169a Exclude fuzzy-native from the v8 snapshot 2019-03-29 21:04:49 +01:00
Rafael Oleza
4d3e71d25a Ignore node_modules of the fuzzy-native package 2019-03-29 19:21:06 +01:00
Winston Liu
f7d123ca8c Update package-lock.json 2019-03-26 14:44:08 -04:00
Rafael Oleza
874016b785 Add GITHUB_TOKEN env var to the npm install step (take 2) 
This will prevent issues when installing the `vscode-ripgrep` package
 2019-03-20 14:41:22 +01:00
David Wilson
ccc7233e51 Add GITHUB_TOKEN env var to the npm install step 
This will prevent issues when installing the `vscode-ripgrep` package
 2019-03-19 11:50:26 -07:00
Rafael Oleza
9d7467f7b2 ⬆️ fuzzy-finder@1.10.1 2019-03-19 12:45:42 +01:00
Ash Wilson
401a5a7d0a Merge pull request #18946 from atom/aw/electron-version-in-build-env 
Set Electron version within the build process environment
 2019-03-06 11:53:46 -05:00
Ash Wilson
c513d1c024 Set ELECTRON_VERSION to the current Electron version. 2019-03-06 10:39:33 -05:00
Landon Abney
55cdc398f6 Use includes instead of indexOf 
Co-Authored-By: rafeca <rafeca@gmail.com>
 2019-02-28 19:30:03 +01:00
Rafael Oleza
8daaf3834e Enable linter on spec/ folder 2019-02-28 19:30:03 +01:00
Jason Rudolph
3b195122c4 Tell VSTS to build electron-* branches 2019-02-25 15:17:09 -05:00
Jason Rudolph
9ff5160b45 Update package-lock.json and script/package-lock.json 2019-02-25 15:14:53 -05:00
Jason Rudolph
c9e6d04e8c Revert "Merge #18603 from atom/electron-3-0" 
This reverts commit b92ae2ad04, reversing
changes made to d4fe5ccfeb.
 2019-02-25 13:41:59 -05:00
Jason Rudolph
46fa62ac59 Revert "Merge #18815 from atom/electron-3.1.3" 
This reverts commit e81f71318a, reversing
changes made to bded0c102a.
 2019-02-25 13:37:35 -05:00
Rafael Oleza
034a05c8f4 Enable linter on packages/ folder 2019-02-25 13:05:02 +01:00
Ash Wilson
b5898b8e07 Actually dump minidump contents to the file 2019-02-22 15:02:47 -05:00
David Wilson
ce4180e9f1 Upload Windows delta nupkg artifacts in release builds 2019-02-17 15:12:07 -08:00
Ash Wilson
402fa903fd Merge pull request #18802 from atom/aw/jasmine-junit-xml 
Report test result metadata to Azure DevOps
 2019-02-16 11:02:20 -05:00
Ash Wilson
efd9151589 Revert temporary script/test changes 2019-02-15 16:09:27 -05:00
Ash Wilson
06a1a38d25 Oh. Right. That's interpreted as a .bat file 2019-02-15 14:56:39 -05:00
Ash Wilson
60aaca8ecc Er, maybe no separator at all? 2019-02-15 13:02:25 -05:00
Ash Wilson
a645a8e638 Windows path separator maybe 2019-02-15 11:16:33 -05:00
Ash Wilson
536c582e2b Respect Atom.SkipTests 2019-02-15 11:16:19 -05:00