Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-15 Thread doug livesey
I've not replied because I've not really seen these things deployed at the scale you talk of so I'm not really qualified. But I think you make a fascinating point that I'd love to see other people push back on, so I'm just bumping the thread! :) For my (already admittedly underqualified) 2p, my obs

Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-09 Thread Lee Hambley
Hey all, It looks like someone was able to spare me a trip back to Manchester, and the discourse was good. I'd like to weigh in and propose a question… "why do we do CI/CD?" I've seen (and am currently enjoying the spoils of) companies pour hundreds of thousands of pounds into CI/CD setups on Do

Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-09 Thread doug livesey
That's all rather inspiring, thank you! I'll look forwards to your posts, Sean (and sorry again for trying to volunteer you!), if you get chance to make them. And thanks for that in-depth coverage, Paul, I shall go back and read it more slowly, now, with my mind's digestive juices switched on. Imme

[NWRUG] Re: This is a bit embarrassing...

2018-02-08 Thread John Cleary
On Sunday, 4 February 2018 14:15:38 UTC, doug livesey wrote: > I'm really sorry, I can never remember anybody's name. > There was a chap at the last NWRUG who was telling a bunch of us about how > his workplace had recently shifted to auto-deploying anything committed to > master. > It was a sys

Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-08 Thread Andrew Premdas
Many years ago around 2009-2010 (I think Lee might remember this) we did continuous delivery based on every commit to a Master branch. It was inspired by a talk I saw a year or so earlier by some Swedish guys who were doing live deploys to some big financial software written in Erlang. We used a Je

Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-07 Thread Paul Robinson
I'm not Sean, but at my place down at that Notonthehighstreet.com (known to those within as "NOTHS"), we've been doing continuous deployment for at least 3-4 years, and it's now on its 2nd or 3rd generation/iteration. So I'll answer these questions based on what we do, not on what Sean does, ob

Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-07 Thread Alex Lynham
February 2018 11:51 To: nwrug-members@googlegroups.com Subject: Re: [NWRUG] Re: This is a bit embarrassing... I'd be happy to give such a talk on k8s and such things, but I'm not living in MCR anymore and don't have a date that I'll be in the UK in mind yet, if there's d

Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-06 Thread Lee Hambley
consultancy services. Meet for a coffee? https://calendly.com/ > oceanician > http://twitter.com/oceanician // http://www.linkedin.com/in/alteris // > +447427242195 > > - Original message - > From: Sean Kenny > To: "North West Ruby User Group (NWRUG)" &

Re: [NWRUG] Re: This is a bit embarrassing...

2018-02-06 Thread Ian Moss
er.com/oceanician // http://www.linkedin.com/in/alteris // +447427242195 - Original message - From: Sean Kenny To: "North West Ruby User Group (NWRUG)" Subject: [NWRUG] Re: This is a bit embarrassing... Date: Tue, 6 Feb 2018 02:16:37 -0800 (PST) On Sunday, February 4, 2018 at 2:15:3

[NWRUG] Re: This is a bit embarrassing...

2018-02-06 Thread Sean Kenny
On Sunday, February 4, 2018 at 2:15:38 PM UTC, doug livesey wrote: > I'm really sorry, I can never remember anybody's name. > There was a chap at the last NWRUG who was telling a bunch of us about how > his workplace had recently shifted to auto-deploying anything committed to > master. > It was