Setup¶

• Same as in Issue #333

Issue¶

When running the job-configuratior and some repository credentials are wrong/missing, it hangs forever without giving a warning/error.

I know this is a feature to some extend, but this is actually really annoying because in order to find the repo which is causing this, the users will do:

1. Start the job-configurator
2. Wait
3. Realise the job-configurator does not continue - abort
4. Restart with --debug
5. Wait
6. Realise there are 8 jobs in parallel and abort again, as console output will not help here
7. Restart with --debug -j 1
8. Wait
9. Find the repository which is causing this effect - fix and restart the configurator normally
10. Wait
11. Realise that there is another repo causing issues
12. Go to 1. -.-

yeah, there is a lot of waiting involved :/

Fix Proposal¶

• Have a max timeout for the repos & show an error for
• A better overview of the pralell jobs (rsb-logger timeline/scope style would be so nice!)
• A commandline switch to control this

Thanks <3