If git is blocked due to proxy issues, the system should fall back to a source mirror. (In fact, I thought this worked in the past, so I believe this is a regression). Make sure this is a permanent part of automated testing. If that's hard, add it to manual testing until it's automated.
This has been confirmed to work on 1.6, marking this as an enhancement for the 1.7 testing plans.
after a short talk with Paul, a first test would be to block before a build the git using the firewall, then see if a build (e.g. minimal) can be completed using the fallback source mirrors.
Sorry for this, but I am having trouble understanding the original intent of this test (or possibly something was lost in translation) Do you want this test to check that: 1) if git isn't working, build completes by getting the needed packages by another method (wget, ftp or whatnot) or 2) if the git source location (git.yoctoproject.org for example) isn't working, it switches to a different download mirror (say a local mirror you've set up in advance) I hope I was coherent enough in my description.
The first thing - that if git isn't working, the http mirrors have the necessary artifacts
Test case proposed: https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1058 Feedback would be appreciated.
Just looking over the test case: 1) It doesn't specify the starting condition - unless you already assume this for all test cases, you need to ensure you start with these recipes unfetched (so perhaps a bitbake -c cleanall <recipe> first, or alternatively state that you should start completely clean with an empty DL_DIR and TMPDIR) 2) Rather than offering a choice we should be explicit about what needs to be tested. If we're starting completely clean then I'd say bitbake -c fetchall core-image-sato would be a good target.
Comments noted. Test case has been updated. Marking as resolved.
Closing.