WebDAV support improvements

This MR adds support for the clean-betas script, which replaces the ad-hoc solution currently installed on our server.

added 2 commits

• 852070d2 - [dav] Rename config file as ~/.bdtrc
• 4d1bebb5 - [dav] Rename config file as ~/.bdtrc (bis)

Compare with previous version

added 1 commit

• 774779ec - [dav] Make clean-betas work properly

Compare with previous version

added 1 commit

• 41ccce24 - [ci] Move clean-betas to CI (pre-nightlies)

Compare with previous version

merged

mentioned in commit 1cd9e861

@andre.anjos I think the best thing is to run cleanup after a successful build of nightlies, not before build.

It came to mind, but that would mean the clean-up is only run iff the nightlies succeeds, which may lead to accumulating betas for weeks.

I also thought to restricting the cleanup to once a week... Running this every night may break a random installation running at the same time.

What do you think, @amohammadi?

Another option is to do (https://docs.gitlab.com/ee/ci/yaml/#when):

when: always

That may work and I agree it would be "cleaner".

It came to mind, but that would mean the clean-up is only run iff the nightlies succeeds, which may lead to accumulating betas for weeks.

Running clean-ups when nightlies fails breaks our setup untill nightlies is green again. For examples, bob/docs stops working, we cannot create a stable beta environment from the channel anymore and ...

So I still think it should be run after nightlies is green.

OK for me, but I think this will create a very big stress on having green nightlies all the time (or the disk is going full).

You can add a manual clean-up stage as well that we can trigger manually in bob.nightlies.

stages:
  - cleanup_manual
  - build
  - cleanup

cleanup_manual:
  when: manual

Let's try that.