Paving the way for the new ongoing CI ci-apps-hq, I worked on the way the CI dev is getting automatically the jobs.
Initially it was getting jobs from the branches on official apps.
But since, we’ve decided to turn official apps into high quality, we should expect more and more of those. Or at least I hope !
Nowadays, we have a strong limitation with external pull request, PR made on forked repositories and trying to be merged in the official repo. Because those PR aren’t on local branches.
Each time, one of us (me…) have to connect to the server to add it manually, so we can have a test from the CI on those PR.
We can’t expect that manual action with high quality apps, considering we would have a lot more of them.
So now the CI dev is getting its jobs from the github API, for each PR, not regarding anymore the branches themselves.
The big changes about that are:
The idea behind is first to not mixed PR from their branches, we could have many PR from testing from forked repositories. But you can’t have many time the same PR.
Second to simplify the naming of links in the PR, It would be simply the ID of the PR, and the same for each PR.
Also, we have, for example for nextcloud, a jobs https://ci-apps-dev.yunohost.org/jenkins/job/nextcloud_ynh%20PR174/, which is for https://github.com/YunoHost-Apps/nextcloud_ynh/pull/174. A PR from a forked repo. Without having to add it manually.