All livecheck job to buildbot

[mojca]

I still need to perform some testing, but I would like to ask for some general feedback nonetheless.

I would like to run livecheck on the buildbot on regular basis to get a list of outdated port and show those in the new app.

The approach that I just submitted might be somewhat problematic as it might block other jobs for too long. Should I create another builder on the same slave? Any further suggestions?

@arjunsalyan @umeshksingla

[ryandesign]

I would expect port livecheck all to take many hours to run, and for it not to provide useful results, since so many ports' livechecks are broken.

[mojca]

Getting feedback that livecheck is broken is already useful result, in particular when we will be able to combine that data with statistics and author, so that we could quickly check which of the most widely used ports have broken livechecks or outdated version, and start with those.

I'm pretty sure that the lack of feedback is partially responsible for the vast number of broken livechecks, and that this is the first step towards improvement.

What approach do you propose here? Should I create another builder on the same slave/worker as other jobs, so that it could run in parallel with the rest? Will this conflict with other selfupdate etc. jobs i.e. does it require a separate macports installation to work correctly?