8757 2015-12-03 20:49:18 +0000 Automate the process of checking for dead links in recipes 2016-03-21 14:18:04 +0000 1 1 5 Infrastructure AutoBuilder autobuilder 2.1 x86 Multiple VERIFIED FIXED Medium enhancement 2.1 M1 1 juro.bystricky elizabeth.flanagan benjamin.esquivel bluelightning bogdanx.a.voiculescu elizabeth.flanagan infras.ab.watcher Infras.watcher ross.burton bogdanx.a.voiculescu --- --- Don't know oldest_to_newest 57016 0 juro.bystricky 2015-12-03 20:49:18 +0000 URL links in recipes can become obsoleted over the time. Recipes with dead links should be detected by a link-checker running on AB as part of QA. 57105 1 bluelightning 2015-12-07 19:37:12 +0000 Presumably you mean SRC_URI? 57107 2 juro.bystricky 2015-12-07 20:56:39 +0000 (In reply to comment #1) > Presumably you mean SRC_URI? Yes, I guess I should have been more specific. SRC_URI may become obsoleted (containing a dead link), but that may be detected quite a bit later, typically when building images from scratch. You will most likely have no problems, as the SRC_URI content will be fetched from a mirror, but still this should be detected and recipes updated accordingly. 57109 3 bluelightning 2015-12-07 21:41:48 +0000 So in concrete terms, I think this would be a simple matter of running: bitbake -c checkuri world (On a regular basis). 57110 4 juro.bystricky 2015-12-07 21:47:29 +0000 (In reply to comment #1) > Presumably you mean SRC_URI? Yes, I guess I should have been more specific. SRC_URI may become obsoleted (containing a dead link), but that may be detected quite a bit later, typically when building images from scratch. You will most likely have no problems, as the SRC_URI content will be fetched from a mirror, but still this should be detected and recipes updated accordingly. (In reply to comment #3) > So in concrete terms, I think this would be a simple matter of running: > > bitbake -c checkuri world > > (On a regular basis). Yes, something like that. The whole idea is to have this check automated (and presumably followed up by SWAT) 57744 5 elizabeth.flanagan 2016-01-12 13:52:57 +0000 http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=7823bff4fd66b835dea3e4d13dfb0017f234b24b 59934 6 bogdanx.a.voiculescu 2016-03-14 10:32:08 +0000 Hi Beth, I can not find this step on AB. https://autobuilder.yoctoproject.org/main/builders/nightly/builds/772 Please verify if patch is applied in production. 60157 7 ross.burton 2016-03-18 15:34:21 +0000 Its not a build set but a buildset: https://autobuilder.yoctoproject.org/main/builders/nightly-checkuri. 60158 8 ross.burton 2016-03-18 15:35:16 +0000 To save time, verifying myself. 60180 9 bogdanx.a.voiculescu 2016-03-21 06:35:38 +0000 Hi Ross, The commit comment was: " nightly.conf: add checkuri step [YOCTO #8757] Add a world -c checkuri step to nightly. Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>" for this file" /buildset-config.controller/nightly.conf So I looked for a build step in nightly.conf job. Also I looked for this commit to be executed in production; meaning this command "bitbake -c checkuri world" The "bitbake -k universe -c checkuri" command is running for a while, but it is a different commit on a different buildset. I agree "bitbake -k universe -c checkuri" is covering "bitbake -c checkuri world", and it is a solution to verify URL links in recipes. Still it is a different solution and not from this enhacement. 60194 10 ross.burton 2016-03-21 11:01:47 +0000 You're right but that was just the first iteration that landed in git, it was revised in this commit to be what is currently on the AB: commit 1c7b54394cf5cc94eca80b5092d0d8d7a4944102 Author: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Date: Mon Jan 18 11:28:36 2016 +0000 nightly-checkuri.conf: move checkuri to nowait checkuri takes about an hour to complete. moving it from nightly to it's own buildset. 60206 11 bogdanx.a.voiculescu 2016-03-21 14:18:04 +0000 Ross, thank you for clarification!