https://pantsbuild.org/ logo
Powered by
#general
  • w

    witty-crayon-22786

    11/02/2017, 8:29 PM
    ...would read the go page though.
  • r

    rough-waiter-82403

    11/02/2017, 8:31 PM
    That’s the page I’ve been trying to work through. I can’t setup a source_root higher in the directory tree than the git root. I get 
    Can only BUILD gen if a Go local sources source root is defined
  • w

    witty-crayon-22786

    11/02/2017, 8:32 PM
    afaik, what it is expecting is:
  • w

    witty-crayon-22786

    11/02/2017, 8:32 PM
    <gitroot>/src/go
  • r

    rough-waiter-82403

    11/02/2017, 8:32 PM
    I can try moving all the files into a different directory but that will cause it to break the GOPATH imports
  • w

    witty-crayon-22786

    11/02/2017, 8:35 PM
    @rough-waiter-82403: it will work in the context of pants. if you're talking about vendored code, i'm less sure.
  • w

    witty-crayon-22786

    11/02/2017, 8:35 PM
    can see the 
    contrib/go/examples
    directory in the pantsbuild repo: https://github.com/pantsbuild/pants/tree/master/contrib/go/examples ... not sure if there are other good open source examples.
  • e

    enough-analyst-54434

    11/02/2017, 8:37 PM
    @rough-waiter-82403 the 
    Can only BUILD gen for a single Go local sources source root,
    is instructive. That says what it means, and Iunless I missed a big change, pants has a strong opinion on only allowing 1 go source root and 1 go remote source root.
  • w

    witty-crayon-22786

    11/02/2017, 8:38 PM
    yea, nothing fundamental has changed there.
  • e

    enough-analyst-54434

    11/02/2017, 8:40 PM
    @rough-waiter-82403 the context here was the go plugin was taken as a bit of greenfield to express more opinons - disallow custom target names, disallow custom source globs, force single source/3rdparty roots, etc. It may be that the latter breaks down in the face of real world go usage / export of go libraries to the outside world. Maybe some re-thought needed, but you'll need to guide things with your use-case / where Pants falls short.
  • r

    rough-waiter-82403

    11/02/2017, 8:42 PM
    I’m going to attempt setup all the build files manually as with a simple example project it can compile without issue, I just can’t get it to generate the build files. If I can get that to work for a “real world” project then I can look to see what it would take to update the buildgen.go plugin
  • e

    enough-analyst-54434

    11/02/2017, 8:43 PM
    Ok great.
  • m

    microscopic-intern-4465

    11/03/2017, 12:26 AM
    We are starting to migrate our repo from python2.7 to python3. Are there any gotchas to be aware of?
  • h

    happy-kitchen-89482

    11/03/2017, 12:28 AM
    I don’t think Pants itself runs on python3, or at least I’m not aware that this has been tested.
  • h

    happy-kitchen-89482

    11/03/2017, 12:28 AM
    However it should have no problem running/testing/bundling python3 code
  • h

    happy-kitchen-89482

    11/03/2017, 12:28 AM
    “should”
  • h

    happy-kitchen-89482

    11/03/2017, 12:28 AM
    you may discover some rough edges
  • e

    echoing-engineer-75628

    11/03/2017, 2:34 PM
    How are variables in BUILD files referenced? That is, how do I include them in my strings?
  • e

    echoing-engineer-75628

    11/03/2017, 2:34 PM
    name='gfc-aws-kinesis_${SCALA_REV}',
    etc.
  • e

    enough-analyst-54434

    11/03/2017, 3:07 PM
    BUILD files are parsed as python 2.7 files, so plain old python works, ie 
    name='gfc-aws-kinesis_{}'.format(SCALA_REV),
    . That said, if 
    name
    is a 
    jar
    parameter, you probably want 
    scala_jar
    . See the BUILD Dictionary under 'Other BUILD Symbols': https://www.pantsbuild.org/build_dictionary.html
  • e

    enough-analyst-54434

    11/03/2017, 3:07 PM
    At the next Pants major release version, BUILD files won't support arbitrary python code, they'll be purely declarative. So avoiding code if at all possible will help you in the long run.
    👍 2
  • r

    rough-dog-96241

    11/03/2017, 7:46 PM
    oof.
  • r

    rough-dog-96241

    11/03/2017, 7:46 PM
    That include passing dictionary literals as arguments to targets, @enough-analyst-54434?
    🤔 1
  • p

    prehistoric-advantage-59814

    11/03/2017, 9:17 PM
    Trying to stop my builds from using the cache. From what I've gathered it seems that clean-all is supposed to delete the artifact cache but subsequent builds still seem to use the cache. Help?
  • p

    prehistoric-advantage-59814

    11/03/2017, 9:17 PM
    (My ultimate goal is to see compile warnings, which I can't see when using the cache)
  • w

    witty-crayon-22786

    11/03/2017, 9:20 PM
    @prehistoric-advantage-59814: clean-all purges 
    .pants.d
  • w

    witty-crayon-22786

    11/03/2017, 9:21 PM
    to skip the cache for a task, you have two options: 
    --cache-ignore
    or 
    --no-cache-read
    . the former will rebuild something regardless of whether you just finished building it... the latter will just cause the cache to be skipped if the thing currently needs to be built
  • w

    witty-crayon-22786

    11/03/2017, 9:21 PM
    both should probably be specified directly to the relevant task
  • w

    witty-crayon-22786

    11/03/2017, 9:21 PM
    if this is a java/scala compile, that would be:
  • w

    witty-crayon-22786

    11/03/2017, 9:21 PM
    --cache-compile-zinc-ignore
    or 
    --no-cache-compile-zinc-read
1...185018511852...2420Latest