build-london

View the Project on GitHub sevki/build-london

London Build Meetup

On 1st and 2nd of October 2019, Cloudflare, Bloomberg and Google hosted a Build Meetup at the Cloudflare offices in London.

The event was be themed around all things build and test. Developers and enthusiasts of Bazel, BuildStream, BuildXL, Dune, Pants and others were on site. A special area of interest are Cloud Build Systems (aka Remote Execution). It was fun! Thank you to all those that attended.

Social Media

If you would like to tweet about the event, please use the hashtag #buildmeetuplondon – we would love to see your photos of the event!

Schedule

08:20 - Registration & Breakfast

09:00 - Welcome & Announcements

09:10 - Build Systems a la carte - Andrey Mokhov (Jane Street) Slides

10:00 - Dune: the Build System for Ocaml - Jeremie Dimino (Jane Street) Slides

10:45 - Break

11:05 - Microsoft Remote Build Execution: Dev Speedup with Non-Hermetic Build Engines - Erik Mavrinac (Microsoft) Slides Repo

11:55 - Observing process lifetime and filesystem accesses reliably on macOS - Kristijan Simic (Microsoft) Slides Repo

12:40 - Lunch

14:00 - One minute Presubmits - Eric Burnett (Google) Slides

14:50 - Platforms & Toolchains - Gregory Estren (Google) Slides

15:35 - Break

15:55 - Buildstream - Benjamin Schubert (Bloomberg) & Tristan Maat (Codethink)

16:45 - Buildbox world - Jeremiah Bonney (Bloomberg) & Santiago Gil (Codethink) Slides

17:30 - Close

17:40 - Networking Drinks

On day two there will be plenty of time for collaboration, discussion and hacking. We’ll also be holding a round of lightning talks.

Lightning Talks

Package Manager Integration with Bazel - Andreas Herrmann Slides

Apt Lockfiles - William Manley Slides

Testing Bazel’s Remote Execution API - Laurence Urhegyi Slides

ostree - William Manley Slides

Remote Execution on Windows from Linux - Fredrik Medley (Veoneer) Slides

Contact Us

Any questions, issues, queries, complaints and compliments can be directed to [email protected].

Contributor Covenant Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

Examples of unacceptable behavior by participants include:

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

For answers to common questions about this code of conduct, see the FAQ