Maximilien Riehl

If you want to jump to dir you need to eval it on the shell side. We have it in [fw](https://github.com/brocode/fw) (which you also could consider using :wink: ). The...

@locolupo what do you think? Will the new documentation structure on read the docs allow us to do this in an intuitive fashion? Would you add these things to the...

Are you referring to https://github.com/pybuilder/pybuilder/blob/master/src/main/python/pybuilder/ci_server_interaction.py? When I started this the intent was to support progress for arbitrary tasks eventually, not just tests. So it's definitely the right place to add...

> I cannot imagine any scenario where automagic TeamCity messages would be a problem. Worst case the user has some extra ##teamcity[some thing] lines in the output. Agreed. Also the...

FTR test reporting has been automagic for quite a while. I never got any complaints. I think it's important to not be intrusive to existing builds but we currently check...

Also think we should keep both. IMHO the main site (jekyll on github pages) is still great as a landing page, for release notes and some getting started stuff. The...

@locolupo I added a hook but it seems to build only from master.

Some thoughts: - We should ensure presence of the thing we actually need. So if we want to call a binary (say `pandoc`) then we should simply ensure that the...

I think the descriptions should override each other instead, makes more sense to see the python specific description when the python version of run_unit_tests is used? This would mean always...

> i understand but why do we need a "default" @description("foo") in the core_plugin.py? i think an empty description makes in more clear that you need a descripion in your...