Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upbuild: initial .travis.yml implementation #21059
Conversation
addaleax
requested review from
Trott and
nodejs/tsc
May 31, 2018
nodejs-github-bot
added
the
meta
label
May 31, 2018
addaleax
added
the
build
label
May 31, 2018
Trott
approved these changes
May 31, 2018
trivikr
approved these changes
May 31, 2018
This comment has been minimized.
This comment has been minimized.
|
Is there an explanation why do we need this? |
This comment has been minimized.
This comment has been minimized.
|
@vkurchatkin It gives people feedback a lot faster than waiting for people to manually kick off our CI. Is there any downside? (There’s a chance it doesn’t work out the way we want to, because we generate too many jobs as a project, but I don’t see the harm in trying.) |
This comment has been minimized.
This comment has been minimized.
|
I would like this to be limited to Linux to reduce the load on Travis. If
the goal is to have a quick feedback, having a single job is better.
We can always test OS X on our regular CI.
Il giorno gio 31 mag 2018 alle 17:48 Anna Henningsen <
notifications@github.com> ha scritto:
… @vkurchatkin <https://github.com/vkurchatkin> It gives people feedback a
lot faster than waiting for people to manually kick off our CI. Is there
any downside? (There’s a chance it doesn’t work out the way we want to,
because we generate too many jobs as a project, but I don’t see the harm in
trying.)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#21059 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADL43SfYh0CTvALN2xbd1O6aIiGgu6rks5t4BDRgaJpZM4UVORV>
.
|
This comment has been minimized.
This comment has been minimized.
|
@mcollina Seems fine to me, updated! |
This comment has been minimized.
This comment has been minimized.
I was looking forward to having macOS tests running on something other than the EOL'ed 10.10 that we run it on in CI. |
maclover7
approved these changes
May 31, 2018
|
LGTM, but with a comment... In theory, we could get this functionality from our existing infra. The github-bot's comment-to-start-build script could be repurposed to trigger a "lite build" or a full CI run. At the risk of this turning into a rant, the number of people actively contributing to the build wg is down to a number that can fit on one hand, and we're in search of more contributors (happy to talk about ways to get involved in any capacity with anybody who's interested) While I am okay with introducing Travis, I would also urge everybody that depends on Node to take another look at the almost 200 machines that we've already got, and see how we could use them in a smarter way. |
This comment has been minimized.
This comment has been minimized.
|
@addaleax oh, I get it, since we don't want to run CI automatically on our infra |
This comment has been minimized.
This comment has been minimized.
|
I'm generally good with this so long as it is understood by all collaborators that a travis run does not replace a full CI run. |
jasnell
approved these changes
May 31, 2018
ofrobots
approved these changes
May 31, 2018
This comment has been minimized.
This comment has been minimized.
|
@vkurchatkin, why not enabling the automatically CI when a Pull Request is created or commented by a CTC or collaborator? |
This comment has been minimized.
This comment has been minimized.
|
@jasnell I think it’s at least worth noting that this does cover the same things as |
This comment has been minimized.
This comment has been minimized.
|
Once we run the experiment for a while and validate it, sure :) |
This comment has been minimized.
This comment has been minimized.
|
I'm ambivalent about this.... |
This comment has been minimized.
This comment has been minimized.
|
Here's a named jobs hack: .travis.yml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index c3b4119ed2f..e9e03a94700 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -7,9 +7,11 @@ matrix:
include:
- os: linux
node_js: "latest"
+ env: NAME=linter
script:
- NODE=$(which node) make lint-ci
- os: linux
+ env: NAME=test
install:
- ./configure
- make -j2 V= |
BridgeAR
approved these changes
May 31, 2018
danbev
approved these changes
Jun 1, 2018
Leko
approved these changes
Jun 1, 2018
This comment has been minimized.
This comment has been minimized.
Agreed, and if we see Travis is worsening the situation in the Build WG, we can always remove it in the future. |
mmarchini
approved these changes
Jun 1, 2018
nodejs
deleted a comment from
refack
Jun 1, 2018
shisama
added a commit
to shisama/node
that referenced
this pull request
Jun 9, 2018
shisama
added a commit
to shisama/node
that referenced
this pull request
Jun 11, 2018
shisama
added a commit
to shisama/node
that referenced
this pull request
Jun 12, 2018
targos
added a commit
that referenced
this pull request
Jun 13, 2018
shisama
added a commit
to shisama/node
that referenced
this pull request
Jun 17, 2018
This was referenced Jun 20, 2018
calebeby
added a commit
to Pigmice2733/scouting-frontend
that referenced
this pull request
Jun 20, 2018
This was referenced Jun 20, 2018
joyeecheung
referenced this pull request
Jun 21, 2018
Closed
git-node: count jenkins pipeline and/or Travis as effective CI runs #259
This comment has been minimized.
This comment has been minimized.
|
Just wanted to pop in and say, Thank you! This is great for someone like me who only contributes once every few months with small PRs since I forget the contributing guidelines. Now I can get instant feedback on my PR without waiting for a maintainer to tell me I did it wrong |
This comment has been minimized.
This comment has been minimized.
It's easier for the maintainers too. EVERYBODY WINS!!!11!!!!1! |
addaleax commentedMay 31, 2018
•
edited
Let’s see if this works!
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes