Merged and pushed.

Fine with me.

Any further comments on the code, Malte?

Thanks for the comments on bitbucket!

I added this item to the meeting agenda.

Certainly looks interesting, but I think this kind of infrastructure thing needs
to be discussed with everyone. Especially if it means that we have to add a
bitbucket-specific YAML file to the root of the repository. (Yuck!)

IOW, that's the kind of thing I'd like to see discussed at a Fast Downward meeting.

After some experimentation, I think the feature works really well and it could be 
a useful addition to our workflow.

I made a pull request here:
https://bitbucket.org/jendrikseipp/downward/pull-requests/59

In the top right on the pull request page you can see whether the issue branch 
passes all tests ("x of 1 passed"). Clicking on the link shows the test output.

Information about passing and failing builds is also available on overview pages, 
e.g. https://bitbucket.org/jendrikseipp/downward/pull-requests/.

If we merge this branch, the only step necessary for enabling continuous 
integration for a different repo is going to "Pipelines" in that repo and 
enabling the pipelines feature.

Interesting! BTW, it's also possible to run buildbot on revisions that are not
yet part of the repository, so we could e.g. have a script that triggers the
buildbot on the current local revision. I'm not sure if this feature is
currently enabled, and if yes, it's only enabled for people who are logged into
the buildbot (because of course this feature allows arbitrary code execution on
all buildslaves). So this could be an alternative that is easier to arrive at
from our current infrastructure. (I'm not saying I prefer either solution, just
wanted to mention the possibilities.)

Bitbucket recently added support for continuous integration (under the name 
"pipelines": https://confluence.atlassian.com/bitbucket/bitbucket-pipelines-
792496469.html). In this issue, I'd like to evaluate how useful this feature is 
for our workflow. Ideally, it could allow us to run code and style tests for 
branches before we merge them, simplifying the review process.