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 demand it gives me a reason to come back at least.
On 6 Feb 2018 12:32, "Ian Moss" <he...@ianmoss.com> wrote: > Interesting topic. > > Were there pre-conditions as part of the auto deploy? i.e. all tests, or > some particular tests had to pass... did it run the full suit, or was there > there some detections over which particular tests covered this push to > master? > > I presume if there's a regular commit going on, then running the full > suite of tests would not be possible. > Sounds like an interesting challenge. > > Often thought it'd be great to have a tool, that given a particular > class/method within a project can identify all the tests using it. Maybe > there's something already out there for this? Only 1 coffee in to the day, > so unsure. > > I'm available to help team-based projects on a freelance basis at the > moment. Let me know if that's you? > > Cheers, > Ian. > > -- > Ian Moss > CTO-level 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 <sean.ke...@hotmail.com> > To: "North West Ruby User Group (NWRUG)" <nwrug-members@googlegroups.com> > 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: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 a system organised with kubernetes, and there was CI and tests > running on the live stack and everything. > > Anyway, it was really interesting and I thought it might make a cool > talk. > > I wasn't going to try to nominate anybody else until I could suggest an > idea for a talk I'd do, too, but I'm coming up with nothing for me so far! > > Anyway, seeing as I can never remember anyone's name, the gentleman in > question can always plead ignorance if he reads this and doesn't feel > inclined to sharing it with the group. :) > > Hey, > > That was me but I'm going to plead ignorance as far as giving a talk about > it goes; I don't think just a run through of it would be interesting to the > majority of people. I'm planning to do some blog posts about a few of the > things but it's just finding the time in work or the motivation out of it. > If/when I get those done, I'll let you know. > > Cheers, > Sean > > -- > You received this message because you are subscribed to the Google Groups > "North West Ruby User Group (NWRUG)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nwrug-members+unsubscr...@googlegroups.com. > To post to this group, send an email to nwrug-members@googlegroups.com. > Visit this group at https://groups.google.com/group/nwrug-members. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "North West Ruby User Group (NWRUG)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nwrug-members+unsubscr...@googlegroups.com. > To post to this group, send an email to nwrug-members@googlegroups.com. > Visit this group at https://groups.google.com/group/nwrug-members. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "North West Ruby User Group (NWRUG)" group. To unsubscribe from this group and stop receiving emails from it, send an email to nwrug-members+unsubscr...@googlegroups.com. To post to this group, send an email to nwrug-members@googlegroups.com. Visit this group at https://groups.google.com/group/nwrug-members. For more options, visit https://groups.google.com/d/optout.
