|Re: [cross-project-issues-dev] SimRel 2019-09 Repository Quality|
On 02.09.2019 10:30, Mickael Istria wrote:
Indeed, I am aware of those reports. The presentation just makes it difficult to get a real overview and it is not highly navigable.
The report details for installable units are particularly useful for figure what depends on what and how it depends on those things. So, for example, when there are duplicates, one can determine which things rely on which versions and how specific the range of that dependency is...
The report is also intended to do a deeper analysis of the actual
artifacts as well, i.e., the process already does actually mirrors
the artifacts and ensures they can be unzipped, for example.
Ideally I'd be able to test that native artifacts are properly
signed, but I don't know how to do that yet...
Yes, at some point we have to enforce rules. I'm incline, for example to ask to PMF be removed from the train because I doubt they will be responsive and are a source of too many problems.
But whose builds will fail?
Certainly the job is super easy to configure:
I tried to minimize the amount of shell script involved...
Not at this point, but someone has already asked for such a thing in the Bugzilla.
I can lead a horse to water, and I can even be the horse and do some of the drinking myself, but no matter what, the horses in general will have to do their own drinking
Back to the top