Re: [sr-dev] travis-ci error messages to the list related to coverity_scan

Hello, thanks for this work! It would be good to have a way that more developers can trigger a coverity scan, but the results are only visible to the developers that registered to coverity site, therefore I do not think alerts/notifications to public sr-dev mailing list are useful for the vast majority of members. Those devs associated in the coverity project get a notification when a new scan is uploaded. Another aspect is that I consider automatic scans to be inconvenient in this case, in many cases I upload scans myself and want to keep that scan until I solve some reported issues -- an automatic scan can overwrite the state of an ongoing analyzis. So a new scan should be triggered and uploaded only a specific developer wants to do analyzis and eventually after sync'ing with the other devs not to have a conflict. Should anyone have different opinions and see other benefits by doing it in another way, I am more than open to have the proposals discussed here. Cheers, Daniel On 17.12.17 14:49, Victor Seva wrote: -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com