Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Dockerize ESLint - #12796

Closed
ghost wants to merge 4 commits into
masterfrom
unknown repository
Closed

Dockerize ESLint#12796
ghost wants to merge 4 commits into
masterfrom
unknown repository

Conversation

@ghost

@ghost ghost commented Sep 27, 2017

Copy link
Copy Markdown

@cowlicks

Copy link
Copy Markdown
Contributor

Why do we run eslint inside docker, instead of in the git repo?

@ghost

ghost commented Sep 29, 2017

Copy link
Copy Markdown
Author

We mount /opt to be /chromium. Should probably make it more obvious.

@ghost

ghost commented Sep 29, 2017

Copy link
Copy Markdown
Author

@cowlicks @Hainish Review please.

@cowlicks

Copy link
Copy Markdown
Contributor

@koops76 sorry if my question was unclear. I'd like to know why we should dockerize this test? It seems like it adds an unnecessary layer of abstraction.

@ghost

ghost commented Sep 30, 2017

Copy link
Copy Markdown
Author

@cowlicks Speeds up the test, since we already have node dockerized, but we have to install ESLint each time.

@cowlicks

Copy link
Copy Markdown
Contributor

@koops76 I'm working on a PR that will run eslint as an independent test in travis. So it won't run for every test in travis #12624

@ghost ghost closed this Oct 1, 2017
@ghost
ghost deleted the docker-eslint branch October 1, 2017 05:11
@ghost

ghost commented Oct 1, 2017

Copy link
Copy Markdown
Author

@cowlicks Closing until you finish.

@ghost

ghost commented Oct 2, 2017

Copy link
Copy Markdown
Author

Closing in favor of #12624.

This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant