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

Pants

you can do something like `wrap([$class: 'AnsiColorBuildWrapper', 'colorMapName': 'XTerm', 'defaultFg': 1, 'defaultBg': 2]) { ... }` to get colored output

we also do something like
```
def get_git_hash() {
    sh "git rev-parse HEAD &gt; githash"
    readFile("githash").replace("\n", "")
}

def get_git_branch() {
    sh "echo ${env.JOB_NAME} | cut -d/ -f 2 &gt; gitbranch"
    readFile("gitbranch").replace("\n", "")
}```

to be able to read the current githash we're building and the branch name

it's a bit nasty to have to do something like this but last time I checked, there wasn't a more pleasant way to do it

<@U053HHEDG>: do you have time to look at <https://rbcommons.com/s/twitter/r/3698/> ?

(heads up: c5d68be852b280323a1a2176905a16b5858efdcf was out of sync with its review/pr, so it was reverted)

FYI Garrett just discovered a huge speed up on his laptop with:
```
ignore_patterns: [
    ".*/",
   ...
]
```
in pants.ini.  Excludes `.cache`, `.git` and `.pants.d` Worth making a default for everyone I think.

Oh, just my luck. My build comes up on Travis and its all `apt-get install failed`

But, on the good side, <https://github.com/pantsbuild/pants/pull/3262> shows that my build passed on the Jenkins runner!

<@U053H6LQS>: hm... i think `.*` is already a default pattern. but i suppose that doesn't match directories, now does it...

We had already overridden the defaults so maybe it is fine the way it is.

Plugin question: it looks like there’s no BUILD file type, so do we associate them with the text file type?

<@U051221NF>: it should go with python files if you need any build file assistance (not super good right now). otherwise it doesnt matter

That’s what i thought, but then you get loads of “missing symbol” inspection errors

If I associate the “BUILD" filename pattern with the text file type, I get no errors but also no syntax coloring

If I associate it with the Python file type, I get errors

<@U053H6LQS>: <@U06A03HV1> <@U04S45AHA>  so at this point I think the main thing left for me to able to move  our code to pants is building our play app. How do you guys suggest I go about that?