Spencer
d8d65526c6
[eslint] enable no undef ( #10825 )
...
* [codeshift] add proper ignore comments
* [codeshift] apply require-to-import transform
* [codeshift/fixup] remove duplicate imports
* [eslint] upgrade config for react "unused" support
* [codeshift] apply remove-unused-imports transform
* [codeshift] apply remove-unused-basic-requires transform
* [codeshift] apply remove-unused-function-arguments transform
* [lintroller] fix argument list spacing
* [codeshift] apply remove-unused-basic-bars transform
* [codeshift/fixup] fixup unused basic var removals
* manually apply remove-unused-assignments transform
* [codeshift] reapply remove-unused-imports transform
* [codeshift] reapply remove-unused-function-arguments transform
* [eslint] autofix param spacing
* manually fix remaining no-undef errors
* use more descriptive file ignore pattern
* add eslint-plugin-react peerDependency
* replace values that looked unused in tests
* remove // kibana-jscodeshift-no-babel comment
* remove import statements from code required by api tests
* Remove '// kibana-jscodeshift-ignore' comments
* address review feedback
* remove remnant of removed if condition
2017-03-22 07:08:23 -07:00
Tyler Smalley
4b6d6275a4
Correctly reference the default bucket for the release task ( #9493 )
...
The configuration is nested under options instead of config in the new aws_s3 library.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-12-14 18:03:02 -08:00
Spencer
2f6654bcec
[eslint] re-enable no-var and prefer-const ( #9455 )
...
* [eslint] enable no-var and autofix
* [eslint] enable prefer-const and autofix
* [eslint] fix autofix-incompatible no-var and prefer-const violations
2016-12-13 10:44:27 -07:00
Tyler Smalley
ad97552c03
Upgrade to Node 6.4.0
...
* Updated dependencies to include graceful-fs ~4.0
* Replaced deprecated grunt-s3 package with suggested grunt-aws-s3
* Update licenses task to better support npm 3
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2016-08-25 08:40:14 -07:00
Court Ewing
1e2c953f16
Release task now always publishes to staging
...
Production builds should never be published directly from a local
machine. Instead, the release command will now publish to a
commit-specific staging URL, so you use it to publish a release
candidate, and then when those builds have been verified, you need to
copy the RC builds from on the staging location on s3 to the production
folder.
2016-06-17 14:26:08 -04:00
Jonathan Budzenski
032de94fe2
[build] Check for release files after build task
2016-05-19 13:17:05 -05:00
Jonathan Budzenski
d0c835d172
[build] Release packages to s3
2016-05-19 10:27:48 -05:00
Court Ewing
8161788eac
Remove npm shrinkwrap tasks
...
We're not maintaining the shrinkwrap as part of the repo, and it doesn't
add any value when being generated automatically as part of our build
process. In its current form, it actually makes it so we cannot
successfully create new builds without manually setting up a local
shrinkwrap first.
2015-09-17 17:57:46 -04:00
Joe Fleming
62df5a19c6
proper shrinkwrap in build and release
...
build will create it if it's missing, copy it to the build and also create a version without dev deps
release requires it and fatals if it doesn't exist
Conflicts:
tasks/build/index.js
2015-08-26 18:41:37 -07:00
spalger
219c7a3b9e
[build] allow installed plugins to use live compiled es7->es5
2015-08-14 16:20:48 -07:00
spalger
552b824711
[build] finish updates
2015-08-14 11:53:26 -07:00
spalger
e0d78a8475
switch to eslint
2015-07-31 17:16:09 -07:00
Rashid Khan
9912738e38
Add release task to upload to S3
2014-10-03 17:26:05 -07:00
