Turn off branch builds for Travis and AppVeyor

[ilyavolodin]

Currently any PR made by core member of ESLint team is built 10 times on Travis. 5 as PR and 5 as branch. I think we can safely turn off branch builds in both Travis and AppVeyor and lower the load we put on those services (also it's sometimes takes longer for both branch and PR builds to complete).

[platinumazure]

👍 especially if team members can do branch builds on demand.

[not-an-aardvark]

@platinumazure I'm not sure that would be possible. Could you elaborate on why you would find this useful? (It seems like it would be easier to just run npm test locally, but there might be a component that I'm missing.)

[platinumazure]

Well, npm test only runs tests on one Node version, so it would be nice to have Travis branch build functionality for testing occasionally on all environments- but only on demand rather than on every branch push, to achieve the stated goal of faster builds. EDIT: Really, this is just "nice to have" from my perspective.

…

On Jun 26, 2017 2:46 PM, "Teddy Katz" ***@***.***> wrote: @platinumazure <https://github.com/platinumazure> I'm not sure that would be possible. Could you elaborate on why you would find this useful? (It seems like it would be easier to just run npm test locally, but there might be a component that I'm missing.) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8804 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARWekIqwO8Mbr4L-5IGSjqHBRFAehT4ks5sIAqNgaJpZM4OExuE> .

[ilyavolodin]

One additional extra. I noticed that our CI builds are for some reason building jsDoc documentation after each build. Not really sure why that's necessary. We should remove it to speed builds up.

[platinumazure]

@eslint/eslint-team Any thoughts on this issue?

[gyandeeps]

I think we have majority vote for this. Do we still need to discuss this in TSC meeting?

[alberto]

I don't think so. Marking as accepted.