We received an issue on GitHub with a failing build due to this error. The project in question was DevHub — a powerful web application similar to TweetDeck but for GitHub: an application where users can create columns with filters, manage notifications and keep up to date with repository activities.
Security has always been our top priority. Our new underlying infrastructure makes use of VM-backed container encapsulation, running every single build task in complete isolation, even from one another.
Build and Runtime Environments
We ensure the build environment perfectly mirrors the runtime environment. This allows you and your team to have the confidence that your final artifacts will work as expected when they’re invoked.
As of today, each discrete build task for any user or team, across any plan, is a unique VM that gets completely discarded when the build completes, leaving only the final built assets. This prevents any leakages and ensures solid, secure and consistent output every single time.
Previously, build scripts were executed as unprivileged user accounts. As of now, our builds execute with privileged user (root) access, while still maintaining our high standard of security.
This enables installing and building web applications with various powerful binaries — including Hugo, Jekyll, and Zola. Specify a shell script in the src of your build, and it will execute in the cloud as a root user.
Our developer community is our treasure. We are consistently on the lookout for opportunities to improve our developer experience and provide seamless upgrades requiring little to no action by our users.
We’d like to extend a word of thanks to the customers who reported these issues on our feedback channels and encouraged us to deliver a better overall product, including but not limited to: @timer150, @morajabi, @maximeheckel, @anthonyshort, and countless others.
We appreciate your feedback in our effort to make cloud computing accessible to all.