<story><title>Mind your Logs: How a build log from a Jenkins leaked everything</title><url>https://medium.com/@aseem.shrey/mind-your-logs-how-a-build-log-from-a-jenkins-leaked-everything-603cf07fa85</url></story><parent_chain><item><author>malux85</author><text>Why are these Jenkins servers exposed to the public internet?&lt;p&gt;Serves them right for such sloppy ops</text></item></parent_chain><comment><author>dirkf</author><text>It doesn&amp;#x27;t necessarily have to be the case.&lt;p&gt;I&amp;#x27;ve contributed a few small patches to some well-known open-source projects. In the months after that I&amp;#x27;ve received a few automated mails from some CI systems informing me about some (un)successful build. Probably because somewhere somebody integrated a new version of said open-source projects in their product and the system is configured to mail every committer the outcome of the CI pipeline, regardless of whether that committer is actually an employee...
Still sloppy ops though.</text></comment>
<story><title>Mind your Logs: How a build log from a Jenkins leaked everything</title><url>https://medium.com/@aseem.shrey/mind-your-logs-how-a-build-log-from-a-jenkins-leaked-everything-603cf07fa85</url></story><parent_chain><item><author>malux85</author><text>Why are these Jenkins servers exposed to the public internet?&lt;p&gt;Serves them right for such sloppy ops</text></item></parent_chain><comment><author>alfiedotwtf</author><text>You wouldn&amp;#x27;t believe how many there are, open to the public. Even more so are the ones that allow shell access  ️</text></comment>