Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

yea, would disagree: for 1.1.0-pre0, 1.0.0 would be the previous release. all notes should go in master, but it's unclear whether version bumps should all go there as well

yeah - i probably wasn't clear but I came to ~almost the same conclusion. But I was going to use 1.0.0-rc3 since that is the last release in the CHANGELOG.  The 1.0.0 release isn't on master branch at all

(by which I mean mentioned in the CHANGELOG)

I am proceeding with using the 1.0.0 tag - the changelog in master will jump from 1.0.0-rc3 to 1.1.0-pre0

Sorry, <@U06A03HV1> — sucked into an afternoon of meetings.

stu - I am about to push the release to CR. Your last patch is included - but it caused a timout on jenkins and it looks like the Travis run for your pull requests maybe also timed out.

Red since here: <http://jenkins.pantsbuild.org/job/pantsbuild/job/pants/branch/master/2/>

This shard: <http://jenkins.pantsbuild.org/job/pantsbuild/job/pants/branch/master/2/execution/node/150/log/>

<@U04S45AHA>: how do you find the shard logs?

From the 1st link choose pipeline steps on the left

<@U054MQUPL>: fyi ^ timeout in tests/python/pants_test/pantsd/test_pantsd_integration.py

yea, and i had CI runs _after_ that in jenkins that succeeded. so suspect flakiness, or persistent effects between jenkins runs

I think Mateo noted same failure on Travis

So its likely flaky and not jenkins-specific

Although I'm not seeing it on Travis unless <@U0607UFLH> clicked rebuild on a shard?

```                     tests/python/pants_test/pantsd/test_pantsd_integration.py .
                     tests/python/pants_test/backend/codegen/tasks/test_wire_integration.py ..
                     tests/python/pants_test/backend/jvm/tasks/test_junit_run_integration.py Xs..x
                     tests/python/pants_test/backend/jvm/subsystems/test_incomplete_custom_scala.py ....
                     tests/python/pants_test/backend/codegen/tasks/test_antlr_integration.py ..
                     tests/python/pants_test/pantsd/test_pantsd_integration.py 
FAILURE: Timeout of 6660 seconds reached


22:22:28 111:07   [complete]
               FAILURE```

hmm, seems kinda odd that test_pantsd_integration.py is in there twice?

let me try to repro w/ some verbose logging on travis

<@U054MQUPL>: probably easier to get your run going in jenkins

is there a reasonable way to set env vars for a run in jenkins?