Make CI run on old branch 0.x

[phil-davis]

We want to be able to run CI on the old 0.x branch. Investigate if there is some way that we can run a drone "cron" job on a regular basis for 0.x (probably we will run it weekly)

The 0.x branch still needs some future support, and might have fixes added.

[dpakach]

I have added a weekly cron job on branch 0.x. Can we close this now @phil-davis

[phil-davis]

I see the WEEKLY Cron Jobs entry here in drone: https://drone.owncloud.com/owncloud/files_pdfviewer/settings

But I don't see any weekly drone run here: https://drone.owncloud.com/owncloud/files_pdfviewer

@dpakach I wonder why it does not run?

[phil-davis]

I added another weekly cron job, and made sure to put 0.x (lowercase "x") as the branch name. On the UI list of jobs it shows as 0.X (uppercase "X"). I wonder if there is a case mismatch problem?

I created a branch 0.X at the same commit as branch 0.x - let's see if a weekly job runs in the next week.

[phil-davis]

I changed the status to Blocked. We need to wait and see if a weekly job runs some time in the next week.

[phil-davis]

I don't see any weekly runs in https://drone.owncloud.com/owncloud/files_pdfviewer - somehow it does not even start enough to give an error message.

I added a daily (=nightly) CI on 0.x branch in https://drone.owncloud.com/owncloud/files_pdfviewer/settings

Let's see if a run happens overnight - if so, then there is some problem with weekly drone settings.

[phil-davis]

https://drone.owncloud.com/owncloud/files_pdfviewer
There is only the ordinary nightly drone CI run on master. The job for branch 0.x did not run.
I have made a branch name zero that does not start with 0 and added a nightly job for that - I get suspicious that there will be a problem with a branch name starting with 0 or with0. (looks like a floating point number...)

Now we wait until tomorrow and see if it runs.