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

Pants

my PR URL seems to have disappeared: <http://jenkins.pantsbuild.org/job/pantsbuild/job/pants/branch/PR-3378>

Oh we should maybe turn off GC of PR runs, hm

well, curiously enough 3376 which was before that is still around

I am going to run the release script for 1.1.0-pre0.

so the publish failed on the docs push.
```
remote: Invalid username or password.
fatal: Authentication failed for '<https://github.com/pantsbuild/pantsbuild.github.io.git/>'

Publish to <http://pantsbuild.github.io/> failed.
```
Since it is pushing over https I guess I need to use an access token? I have 2 factor enabled +plus a USB key.

didn’t <@U053HNE90> change that back to ssh?

<https://help.github.com/articles/creating-an-access-token-for-command-line-use/>

then add to .netrc:
```
machine <http://github.com|github.com>
 login $USER
 password $PASS```

thanks...I already made the token but I didn't know about the .netrc entry. thanks!

so - the releases are already on PyPi. What is the protocol here, just run the docsite generation?

<@U053HNE90>: git aside, I want to land the last RB for <https://github.com/pantsbuild/pants/issues/3356> and do the 1 RB for <https://github.com/pantsbuild/pants/issues/3352> + 1 RB on how to use as a user before flipping

Right now it makes sense to do this through Travis, for throughput, or I spend for 2 more imacs

But I guess that doesn't need to block, just the 3 docs tasks, which ... back to work for me

Her'es one <@U053HNE90>: pipeline: <http://jenkins.pantsbuild.org/job/pantsbuild/job/pants/branch/PR-3333/1/flowGraphTable/> missing file: <http://jenkins.pantsbuild.org/job/pantsbuild/job/pants/branch/PR-3333/1/execution/node/83/log/>

In this sort of case the General SCM step shows green but console is empty, so clear fishy

I'll file an issue to look into this more.  I burned a few hours yesterday trying to permute on job setups, but none of the Jenkinsfile + handle PRs for free setups allow control over git details in the jenkins UI ... maybe their are more detailed Jenkinsfile steps that can be used though.

<https://github.com/pantsbuild/pants/issues/3385>

There are enough env vars set to do the git checkout totally manually, so I'm sure this can be sussed with effort