pantsbuild #general

Hi everyone. Have been digging through the docs and code, and couldn't quite find I'm looking for. Is it possible to tell pants (ideally via the command line) to only run java/scala tests with certain annotations, similar to junit Categories or Scalatest Tags. If not possible out-of-the box, what alternatives would you recommend? The closest I found was pants tags, which I think could be made to fit our team's use case, but don't quite provide the level of granularity that we'd like.

rough-sundown-61224

04/06/2017, 3:33 PM

@high-advantage-47550 Hope it works for y’all

witty-crayon-22786

04/06/2017, 4:59 PM

@fast-megabyte-33579 : do you have different configs for the two tasks?

fast-megabyte-33579

04/06/2017, 5:08 PM

@witty-crayon-22786 I don't think so but I will check

most-farmer-27910

04/06/2017, 6:45 PM

Do I need to define a

provides

on my scala_library target in order to publish locally?

most-farmer-27910

04/06/2017, 6:47 PM

And separate question - why do I need to define a

repo

in the

provides

config? Am I misunderstanding that?

enough-analyst-54434

04/06/2017, 7:11 PM

1st, yes - it names the artifact. 2nd, we don't assume maven central, so yes.

most-farmer-27910

04/06/2017, 7:12 PM

thanks @enough-analyst-54434

most-farmer-27910

04/06/2017, 7:12 PM

1 makes sense

most-farmer-27910

04/06/2017, 7:12 PM

2 I'm still a little confused about

enough-analyst-54434

04/06/2017, 7:13 PM

2 is confusing and hard to configure, just a sec for doc pointers.

most-farmer-27910

04/06/2017, 7:13 PM

okay thanks

enough-analyst-54434

04/06/2017, 7:14 PM

http://www.pantsbuild.org/publish.html

most-farmer-27910

04/06/2017, 7:17 PM

thanks, I've been looking at those. It seems confusing to me that if I just want to publish locally, I still have to a) set up a plugin w/ my repository b) possibly set up netrc file and c) tie all that into my pants.ini file. Is that right?

most-farmer-27910

04/06/2017, 7:18 PM

I can go through that if necessary though

most-farmer-27910

04/06/2017, 7:18 PM

Then can you configure an artifact to publish to different repos depending on environment? i.e. dev-local v. CI

most-farmer-27910

04/06/2017, 7:18 PM

(maybe that's an odd corner case)

high-advantage-47550

04/06/2017, 7:20 PM

it’s all python, so you could encode that with an env var check or something somewhere 🙂

enough-analyst-54434

04/06/2017, 7:23 PM

@most-farmer-27910 I'm honestly not sure how deep the validation is on the provides fields. Try just filling in org and name and seing if a local publish works, may blow up if validation is overly aggressive.

enough-analyst-54434

04/06/2017, 7:24 PM

And no, you can't configure multiple destinations right now, @high-advantage-47550's suggestion is the path, basically we'd need some code contributions unless you hack it up in a local plugin that has a new target type doing environment shenanigans, etc.

enough-analyst-54434

04/06/2017, 7:26 PM

The history of this is basically the driving idea that publish is only for the outside world - we wanted a monorepo for internal sharing. That idea is of course not universal; your situation may require internal publishes for sharing between many repos, at least during a transition period.

most-farmer-27910

04/06/2017, 7:30 PM

@enough-analyst-54434 ahhh I see. History makes sense. Yeah, in that transition period now which is why I'm going through some hoops 😞

most-farmer-27910

04/06/2017, 7:30 PM

thanks

witty-crayon-22786

04/06/2017, 8:17 PM

@most-farmer-27910 : to configure alternate destinations in local vs ci, you can use

--config-override=pants.ci.ini

, for example, pointing to a reconfiguration of the repos

witty-crayon-22786

04/06/2017, 8:18 PM

https://github.com/stuhood/pants-ivy-example contains a complete example, although it doesn't do the "use a plugin to avoid repeating yourself" bit for repositories.