pantsbuild #general

Channels

welcome

github-notifications

announce

enough-analyst-54434

05/06/2016, 4:06 PM

I just updated the

CI Status

pants-devel@ thread, but Jenkins powered CI for your PRs and master is now back working.

enough-analyst-54434

05/06/2016, 4:06 PM

Important thing is no

CI this

enough-analyst-54434

05/06/2016, 4:06 PM

It just runs, and

CI this

comments will be ignored

enough-analyst-54434

05/06/2016, 4:06 PM

Trying to figure out a solution for re-builds.

enough-analyst-54434

05/06/2016, 4:07 PM

But I think everyone can do this for their PR via the Jenkins Re-Build button

enough-analyst-54434

05/06/2016, 4:07 PM

Need to confirm that for non-comitters

enough-analyst-54434

05/06/2016, 4:07 PM

If this is solid for today and over the weekend for folks I'll kill the Travis hook on Monday.

enough-analyst-54434

05/06/2016, 4:12 PM

I'll put together a doc today for CI consumers that has some screenshots for how to navigate this, but

Pipeline Steps

is the view you want to drill into individual shard red/green/in-progress

Shell Script

console views

rough-minister-58256

05/06/2016, 5:35 PM

nice

rough-minister-58256

05/06/2016, 5:36 PM

v much looking forward to faster CI

enough-analyst-54434

05/06/2016, 6:03 PM

Its a tradeoff

enough-analyst-54434

05/06/2016, 6:03 PM

Master is much slower, PRs are faster

enough-analyst-54434

05/06/2016, 6:04 PM

This will help speed for PRs if anyone wants to grab it: https://github.com/pantsbuild/pants/issues/3346

enough-analyst-54434

05/06/2016, 6:24 PM

Hey @brash-oxygen-26029 - can you see a

Rebuild

button here?: http://jenkins.pantsbuild.org/job/pantsbuild/job/pants/branch/PR-3326/3/

bored-art-40741

05/06/2016, 6:26 PM

Hey @enough-analyst-54434 let me know when your PRs / changes to Jenkins are stable. I'm going to work on getting a py2/py3/pypy axis set up for CI but I don't want us to step on each others' toes

bored-art-40741

05/06/2016, 6:26 PM

Probably it would be a good time for us to rewrite ci.sh, too

enough-analyst-54434

05/06/2016, 6:27 PM

I'm stable for gui clicky things

enough-analyst-54434

05/06/2016, 6:27 PM

The rest is version controlled script edits, so we won't collide

bored-art-40741

05/06/2016, 6:27 PM

My current though process is that we should do self checks and maybe unit tests for all language axes, and then do the full cross product for master

bored-art-40741

05/06/2016, 6:27 PM

Yeah I want to avoid merge-conflicting on Jenkinsfile basically

enough-analyst-54434

05/06/2016, 6:28 PM

tiny file, our brains can handle those conflicts I think

bored-art-40741

05/06/2016, 6:28 PM

Heh I'm also not going to have time until probably this weekend or possibly next week anyway, so just wanted to let you know

enough-analyst-54434

05/06/2016, 6:28 PM

enough-analyst-54434

05/06/2016, 6:29 PM

here is a healthy list of

infra

issues, almost all jenkins related too

enough-analyst-54434

05/06/2016, 6:29 PM

If anyone wants to pitch-in

enough-analyst-54434

05/06/2016, 6:29 PM

Maybe 1 you need to be Patrick or I to do right now, the rest are doable by anyone willing to read, ask, etc

limited-country-20626

05/06/2016, 7:21 PM

What should the version number of today's release be? Has that been decided/posted?

enough-analyst-54434

05/06/2016, 7:29 PM

Is there any reason not to make all releases from master follow 0.0.NNN forever, ie: use 0.0.83? If the 0.0.83 is also being used as an RC for, say 1.1.0 or 1.0.1, at the point in time folks say LGTM on the RC (0.0.83), the tag/branch process to associate 1.1.0 or 1.0.1 can happen?

enough-analyst-54434

05/06/2016, 7:29 PM

(this is a large departure from what I think folks have thought about!)

enough-analyst-54434

05/06/2016, 7:30 PM

An upside is master releases (and master releases as lazy RCs), will never be in danger of being picked up bu

pip install pantsbuild.pants