Feature #9573
closed
Include deployment of build base intended for preset verification job Linux 3.14
Added by Evgeny Novikov about 5 years ago.
Updated about 5 years ago.
Description
At the moment the almost default Klever deployment configuration file (klever-minimal.json.sample) does not include any build bases. So, users can not start verification immediately after deployment. We should fix that, especially, taking into account that the fix should be trivial.
Besides, there is another production preset job "Linux 3.14 kernel subsystems", but I am not sure that it should be so now.
- Target version set to 3.0
- Status changed from New to Resolved
I implemented this in branch deploy-linux-3.14-build-base. Let's wait for tests results.
BTW, everybody can specify build base archives within deployment configuration files from now.
- Status changed from Resolved to Closed
Tests passed, so, I merged the branch to master in commmit:afaaf5f.
I make preset job "Linux 3.14 kernel subsystems" non-production. I think that is a good rule of thumb to upload archives of corresponding build bases and include links to them within deployment configuration files for all production verification jobs.
- Status changed from Closed to Open
It turned out that normal local deployment fails with build base archives due to permission issues. Indeed, scripts download archives so that only root can access them.
BTW, there is not such the issue with, say, Klever Addons since scripts automatically extract corresponding archives themselves if so.
- Status changed from Open to Closed
I fixed the issue in 7c16a1b to master. Now it seems that all deployment variants work well.
Thanks to youyan from Fujian LANDI Commercial Equipment Co., Ltd for reporting the issue.
Also available in: Atom
PDF