addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Continuous Delivery (OpenSpace)

How to deliver new features/bug fixed automatically in your company.

OpenSpace is a simple methodology for self-organizing conference tracks. It relies on participation by people who have a passion for the topics to be discussed. There is no preplanned list of topics, only time slots and a space in the main meeting room where interested participants propose topics and pick time slots

Join or login to comment.

    • Leo D.

      Thanks for the links/resources!

      August 13, 2014

    • Marcelo O.

      Nice! Thanks Deryl!!

      August 13, 2014

    • Leo D.

      Thanks, I especially liked the visualizations!

      August 13, 2014

  • Jignesh

    Actually I do own this book http://www.amazon.com/dp/0321601912?tag=contindelive-20

    But never explored- time to explore it more now.

    2 · August 13, 2014

    • Marcelo O.

      It's a great book, and I'm going through it myself. Again, I'm a new architect at my company and we're in charge of not only on designing the application but the delivery life-cycle and provide value add to the clients.

      August 13, 2014

    • Deryl S.

      The blog summary link I provided in my other comment really gives you a head start if you don't have time to read the book.

      1 · August 13, 2014

  • Brett G.

    Thanks for posting the notes and the informative content.

    3 · August 13, 2014

  • Jignesh

    Daryl and Marcelo,
    We need few more discussions on this topic.

    August 13, 2014

    • Marcelo O.

      It's a *large* topic to cover and we (3Ci) are just starting to explore it. I agree! I will see if we can have another meetup with this topic.

      August 13, 2014

  • Marcelo O.

    Great conversations and great take aways.

    August 13, 2014

  • Deryl S.

    It was great to see people interested in this topic as it's something I'm very passionate about!

    1 · August 12, 2014

  • Edson C.

    Great group of people, thanks to all who participated.

    2 · August 12, 2014

  • Jignesh

    Thanks Derly,

    I do like to know how frequently branches like development and production get merged. What is the best process to avoid any conflict?

    1 · August 12, 2014

    • Jignesh

      I came to place. But as usual the door closed and nobody opened it

      August 12, 2014

    • Marcelo O.

      I'm outside. Sorry

      August 12, 2014

  • Deryl S.

    Here are a list of questions I have that hopefully can be addressed:

    - When someone's feature is committed with a bug before yours is delivered, is your feature stuck until the one before yours is fixed in a new commit? Your feature then gets delivered with the bug fix?

    - How is front-end code delivered "continuously" when it depends on an API that is not finished?
    How does separation of concerns affect continuous delivery?

    - What feature toggle tools do you use? i.e. Liquibase, Togglz

    - Continuous delivery speaks of a versioning strategy that is assigned automatically at build time. How do you package all dependencies with the dynamically defined version?

    2 · August 12, 2014

    • Deryl S.

      - How are you handling database changes during automated deployments in a continuous delivery environment? Do you back up the database before migrating it? Different approaches for relational vs. NoSQL databases? i.e. tools like Flyway for relational

      - How do you handle ad-hoc changes that only need to be performed for the feature you are delivering and how do you commit/package/version them for deployment? i.e. LDAP modifications, ad-hoc data migrations, custom scripts

      - How do you version artifacts like property files for various environments?


      - How are user acceptance tests continuously delivered if they depend on completed features? Are they failing until fixed? Disabled until fixed? Is it a manual process to enable/disable them?

      - How do you handle a multi-module maven project with a flat folder structure but still allow developers to develop on SNAPSHOTs locally?

      - Is Gradle better suited for CD?

      2 · August 12, 2014

  • Marcelo O.

    Keep in mind that this is going to be an "open space". I would like anyone that is interested in this topic to join us.

    1 · August 11, 2014

  • Marcelo O.

    New venue, same low price :D

    May 23, 2014

  • Deryl S.

    Looking forward to this since I JUST finished the book Continuous Delivery written by Jez. Trying to implement this as well at work.

    January 21, 2014

    • Marcelo O.

      Bad-ass book @Deryl dude! Hope you come over. It's been a while! I'm hoping to have either a go-to-meeting or a Google hangout

      January 22, 2014

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy