Hi, On Tue, 6 Apr 2010, Adrian Schröter wrote:
Note that this will make multimedia:apps rebuild much more often than usually necessary. This is because standard/ always contains the just
It can be also the opposite, building against standard can lead to the blocked state, if it is currently building. While building against snapshot/ may trigger on each change in your project (source or binary changes).
Huh? Changes in your project will cause rebuild requests no matter what base repo you build against. Or at least they ought to.
So, to get work done it's indeed okay to temporarily switch to standard/ as base repo, ... ... ... but in the interest of build power (and download bandwidth for users of your repo), please don't forget to switch back to snapshot/ when the problem has solved itself there (by copying over from standard/).
That is too simple and depends on the work pattern. You may trigger more builds with snapshot/ depending on it.
How could this happen?
standard/ is still the recommended default target.
Priorisation of the builds needs to be handled from us on the server side in any case.
It's always better to have fewer rebuild trigger requests, no matter how clever the priorisation is, so I don't get what you're trying to say. Building against snapshot/ should never generate more rebuild requests, than building against standard/, except if the copying from standard/ to snapshot/ is buggy. Ciao, Michael.