1 / 7

Controlling open-source licenses with Jenkins

Controlling open-source licenses with Jenkins. Rami Sass White Source w hitesourcesoftware.com. @ jenkinsconf. Open Source Risks. Legal Litigation Code/IP contamination Business M&A, reselling, OEM barriers Sales injunctions Technical Security vulnerabilities, bugs

moswen
Download Presentation

Controlling open-source licenses with Jenkins

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Controlling open-source licenses with Jenkins Rami Sass White Source whitesourcesoftware.com @jenkinsconf

  2. Open Source Risks • Legal • Litigation • Code/IP contamination • Business • M&A, reselling, OEM barriers • Sales injunctions • Technical • Security vulnerabilities, bugs • Ineffective updating

  3. White Source • Automates the entire DevOps lifecycle of Open Source components and their licenses • Preventive lifecycle management is better than post-hoc corrective approach • Easy to use, eliminates much burden from developers • Only solution that is inexpensive to buy, and affordable to operate

  4. Demo

  5. White Source • Modern, easy approach to open source management • Integrate with CI to unburden R&D • Automatically enforce policies in real time

  6. Questions

  7. Thank You To Our Sponsors

More Related