Podcasts about continuous integration ci

In this Mob Mentality Show episode, we dive into the journey of Jeff “Cheezy” Morgan, a coach in Continuous Delivery (CD) and lean thinking. Known for his role in advocating for CD within companies, Jeff shares how his experiences with software development and his recent shift into the café business have shaped his philosophy on people and just-in-time. This discussion explores how Jeff's approach to Agile and CD evolved, his journey into Extreme Programming (XP), and how mob programming impacted his perspective on teamwork and Continuous Integration (CI).  **Jeff's Agile and CD Journey** We start with Jeff's introduction to Agile, discussing the early days of his career when dev practices didn't include CD and the impact of adopting CD in high-stakes projects like Y2K. Jeff describes how learning from Thoughtworks influenced his views on XP and CD, and how he became an advocate, eventually taking CD to different organizations. He also shares what it was like discussing with Woody Zuill and Llewellyn Falco and reflects on the transformative role mob programming has played in his career. **From Pairing to Mobbing**   For Jeff, mob programming was not initially appealing, but over time it became his preferred approach for helping teams. We explore how mobbing enhances CI, tightens communication, and fosters collective learning. Jeff explains how mobbing enables "just-in-time" discussions that align teams on what to build and how it allows real-time feedback on other team members' learning. Jeff also examines the transition from pairing to mobbing, the challenges of mob programming with CI/CD, and why mobbing helps him “get the whole system in the room” for tackling complex problems. **Quality Without QA?**   We dive into the controversial idea of achieving high quality without traditional Quality Assurance (QA). Jeff opens up about years spent wrestling with the role of QA in Agile/CD environments and shares experiments with “test-infected” developers—who took full ownership of quality. He reflects on the pitfalls of relying on “heavyweight” traditional QA processes and automated tests, which often create lean waste, add handoffs, and introduce brittle, flakey tests. Jeff and hosts Austin and Chris discuss whether “shift left” is merely a shift away from QA, the Deming Red Bead experiment's relevance, and whether there's a happy journey for QA professionals on CD teams. **Applying Lean to Cafés**   Outside the tech world, Jeff has found a second passion—running cafés. We discuss how owning two cafés influenced Jeff's perspective on Lean thinking and Agile principles. From supply chain issues during COVID to needing backup suppliers, Jeff discusses if “just-in-time” challenges in the café world mirror software development. He shares valuable insights about hiring, managing consistent delivery, and applying Lean principles to run a resilient business. Additionally, Jeff and Chris exchange stories on chip shortages and if Lean can help address real-world supply chain issues. **More from Jeff**   Finally, we tackle some big questions: What does DevOps mean in today's Agile world? Should “DevOps” be responsible for shielding organizations from developers? How does Test-Driven Development (TDD) factor into DevOps scripts, and can mobbing help break down silos that traditionally separated devs, ops, and QA? Join us for this wide-ranging conversation with Jeff “Cheezy” Morgan to uncover actionable insights for anyone involved in Agile, CD, DevOps, or Lean. Whether you're in software, QA, or running a small business, this episode is packed with valuable takeaways on quality, learning, and resilience.  Video and Show Notes: https://youtu.be/OJ5d6qLIQRY   

In this new episode of Technical Tips, Tommy explains how Continuous Integration (CI) helps developers merge code changes frequently, with automated builds and fast feedback loops. Learn how CI keeps your main branch stable and ready for faster releases, all while making your coding life easier. Listen to the full episode or read the transcript on the Semaphore blog.Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

Can you explain GitOps in simple terms? How does it fit into Continuous Integration (CI), Continuous Delivery and Continuous Deployment? And what are considerations when rolling out GitOps in an enterprise? To get answers to those questions we sat down with Christian Hernandez, Head of Community at Akuity, who has a fabulous analogy to explain GitOps that I am sure many of us will "borrow" from him. Christian also explains the ecosystem he works in such as ArgoCD, Kargo as well as OpenGitOps which aims to provide open-source standard and best practices to implementing GitOps.We closed the session with some advice around Application Dependency Management, External Secrets Operator and choosing the right Git Repo Structure.Here are some of the links we discussed:OpenGitOps: https://opengitops.dev/ArgoCD: https://argoproj.github.io/cd/Kargo: https://github.com/akuity/kargoArgoCon: https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/co-located-events/argocon/GitOpsCon: https://events.linuxfoundation.org/gitopscon-north-america/

Continuous Integration (CI) ist zwar ein Konzept aus der Softwareentwicklung, aber aus dem Bereich Data Science nicht mehr wegzudenken. Wir diskutieren wie wichtig CI für Data Scientists ist und wie es genutzt werden kann um Data Science Workflows zu verbessern. 

Continuous Integration (CI) pipelines enable software development teams to build and test code quickly and efficiently. However, the need for robust security measures becomes increasingly important. On this episode, we interview Solutions Engineer Adib Saikali about his experience with CI pipeline security. From protecting sensitive data to detecting and preventing malicious code, Adib provides valuable guidance for ensuring the security of your CI pipeline.Listen to the full episode or read the transcript at https://semaphoreci.com/blog/adib-saikaliLike this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

Год назад мы приступили к готовке Continuous Integration и Continuous Delivery. Но блюдо оказалось настолько сложным, что его приготовление заняло целый год. Но если DKT обещает в мае, мы свои обещания выполняет. Тайминг: 00:00:00 Вступление 00:01:16 Максим в гостях 00:02:00 Сходить посмотреть анонс - https://youtu.be/zfHez5sLsWQ 00:02:25 Agenda 00:06:07 Continuous Integration и Continuous Delivery 00:06:56 CI/CD Blueprint 00:07:19 Release lifecycle & SDLC 00:08:44 Release lifecycle  00:09:11 Не только Git'ом едины 00:11:07 Build & Test  00:12:30 Branching strategies: GitFlow 00:14:40 Зачем вообще нужны branching strategies?  00:17:34 Проблемы количества веток в GitFlow 00:19:27 Branching strategies: GitHub Flow 00:20:48 Кому подходит GitHub Flow?  00:22:05 Branching strategies: Trunk-Based 00:23:35 git cherrypick  00:24:53 Trunk-Based ближе всего к Continuous Integrations 00:26:00 Feature toggle (feature flags) 00:27:16 Начало CI/CD blueprint  00:28:03 Code review 00:31:56 Joma Tech: how we write/review code in big tech companies (1) 00:36:00 Semantic Versioning  00:38:50 Почему важно фиксировать версии 00:43:30 Что такое Continuous Integration  00:50:28 CI/CD blueprint: Continuous Integration (CI)  00:50:54 Локальный CI 00:52:00 Quality gate  00:52:43 git hooks 00:54:34 CI steps 00:54:50 Code analysis 00:56:40 Code linting 00:58:37 Unit testing  01:00:00 Сохранение артефакта 01:02:50 Continuous Delivery 01:05:11 CI/CD blueprint: Continuous Delivery (CD) 01:07:00 Infrastructure provisioning  01:08:56 CD Quality Gates  01:12:04 Плюсы Continuous Delivery 01:15:25 Continuous Deployment 01:17:26 Deployment strategies  01:18:17 Зачем нужна deployment strategy?  01:19:04 Deployment strategies: Recreate (Big bang) 01:22:10 Deployment strategies: Ramped (rolling update) 01:24:00 Deployment strategies: Blue/Green 01:28:29 Deployment strategies: Canary 01:31:24 Deployment strategies: A/B testing 01:34:27 Continuous Operations 01:36:24 Recap  01:39:32 Tooling: CNCF Landscape 01:42:12 CI/CD Metrics: DORA  01:45:15 CI/CD Metrics: Custom Ссылки: 1)https://www.youtube.com/watch?v=rR4n-0KYeKQ

Watch the live stream: Watch on YouTube About the show Sponsored by Microsoft for Startups Founders Hub. Special guest: Anne Barela Brian #1: The Adam Test : 12 Questions for New Dependencies Found through a discussion with Ryan Cheley, who will be on an upcoming episode of Test & Code, talking about Managing Software Teams. The Joel Test dates back to 2000, and some of it is a bit dated. I should probably do a Test & Code episode or pythontest article on my opinions of this at some point. Nice shameless plugs, don't you think? The Joel Test is 12 questions and is a “highly irresponsible, sloppy test to rate the quality of a software team.” “The Adam Test” is 12 questions “to decide whether a new package we're considering depending on is well-maintained.” He's calling it “The Well-Maintained Test”, but I like “The Adam Test” Here's the test: Is it described as “production ready”? Is there sufficient documentation? Is there a changelog? Is someone responding to bug reports? Are there sufficient tests? Are the tests running with the latest language version? like Python 3.10, of course Are the tests running with the latest integration version? Examples include Django, PostgreSQL, etc. Is there a Continuous Integration (CI) configuration? Is the CI passing? Does it seem relatively well used? Has there been a commit in the last year? Has there been a release in the last year? Article has a short discussion of each. What score is good? That's up to you to decide. But these questions are good to think about for your dependencies. I also think I'll use these questions for my own projects. I've got a README.md, but do I need more examples in it? Should I have RTD docs for it? Have I updated the test matrix to include the newest versions of Python, etc? Have I hooked up CI? Michael #2: Validate emails with email-validator When you think about validating emails, you probably think regex (or just nothing) Regex is fine but so is this email: jane_doe@domain_that_doesnt_exist.com Problem is (at the time of the recording), domain_that_doesnt_exist.com is not a website. What about unicode variations that are technically the same but visually different? If the passed email address is valid, the validate_email() method will return an object containing a normalized form of the passed email address. Anne #3: The Python on Microcontrollers Newsletter One of my main focuses at Adafruit since the pandemic started is as editor of the Python on Microcontrollers Newsletter. With a weekly distribution of almost 9,400 subscribers, it's the largest newsletter of it's kind. It mainly focuses on CircuitPython and MicroPython and also discusses Python on single board computers (SBC) like Raspberry Pi. News about Python with a small computer emphasis Folks may subscribe by going to https://www.adafruitdaily.com/ which is separate from adafruit.com. The information is not sold or used for marketing and it's easy to unsubscribe (no “do you really want to do this, please reconsider…) The challenge, like for Python Bytes and other publications, is to find content. I scour the internet, with a bit of a focus on Twitter as I have an active account there. We encourage others to put in issues and Pull Requests on the newsletter GitHub, email information to cpnews@adafruit.com and using hashtag CircuitPython or MicroPython on Twitter. Brian #4: Git Organized: A Better Git Flow Annie Sexton Found through Changelog episode 480: Get your reset on A possible and common git workflow Branch off of a main branch to a personal dev branch Commit and Push during development to save your work When ready to merge, make a PR Problems Commits are hard to follow and messy, not ever really intended to separate parts of the workflow or anything. Commits are therefore useless in helping someone code review large changes. Annie's workflow Branch off of a main branch to a personal dev branch Commit and Push during development to save your work. But don't worry to much about commit messages, “WIP” is sufficient. Or a note to yourself. When ready to merge git reset origin/main Re-commit all changes in a logical order that makes more sense than the way the work actually happened. These will be several commits, with descriptive messages. Even partial commits, if there are unrelated changes in a file, work with this process Push all the new commits. (Is --force going to be necessary?) Create a PR. Now there are a set of commits that are actually helpful to break up large PRs into small chunks that tell a story. I'm looking to try this soon to see how it goes Michael #5: CPython issues moving to GitHub soon Update by The Python Developer in Residence, Łukasz Langa The Steering Council is working on migrating the data that is currently residing in Roundup at https://bugs.python.org/ (BPO) into the GitHub issues of the CPython repository hosted there. Laid out in PEP 581 -- Using GitHub Issues for CPython The ultimate goal is to move user- and core developer-provided issue-reporting entirely to Github. Each issue that currently exists on BPO will include metadata indicating where it was moved on Github. New issues will only exist on Github. Feedback, please: At the current stage, we're asking you to take a look at the links and important dates below, and share any feedback you might have. Timeline: Friday, March 11th 2022: Github starts transfer of the issues in the temporary repository to github.com/python/cpython/ . The migration is estimated to take anywhere from 3 to 7 days, depending on the load on Github.com. Anne #6: MicroPython, CircuitPython and GitHub What are Microcontrollers and Single Board Computers (SBCs)? Why not use CPython on Microcontrollers? MicroPython was originally created by the Australian programmer and theoretical physicist Damien George, after a successful Kickstarter backed campaign in 2013. Originally it only ran on a number of boards and was based on Python 3.4. CircuitPython was forked from MicroPython in 2017 by Adafruit Industries. Both MicroPython and CircuitPython are Open Source under MIT Licenses so adoption and modification by anyone is easy. Why fork CircuitPython? 1) Make a requirement that CircuitPython boards can enumerate to computers as a USB thumb drive to add or change code files with any text editor. 2) Aim to make CircuitPython use CPython library syntax whenever possible. 3) Make it easy to use and understand for beginners yet powerful for more advanced users. All CircuitPython code is on GitHub. GitHub Actions is used on repos like the Adafruit Learning System code to automate CI with Pylint, Black, and ensuring code has proper SPDX author and license tags, which is a new addition this year. Currently there are 283 microcontroller boards compatible with CircuitPython and 87 single board computers can use CircuitPython libraries in CPython via the Adafruit Blinka abstraction layer. Code portability between boards requires little if any changes. There are 346 CircuitPython libraries (all on PyPI / pip as well as GitHub) covering a wide range of hardware and real world needs. From blinking LEDs to using ulab (microlab), a subset of numpy, for data crunching. I just counted and there are exactly 1,000 Adafruit Learning System guides referencing CircuitPython, all free and open source/MIT licensed. https://learn.adafruit.com/ Extras Brian: Quick read: The Thirty Minute Rule, by Daniel Roy Greenfield summary: Stuck on a software problem for 30 min? Ask for help. Michael: The CircuitPython Show by Paul Cutler Follow up from my Python 3 == Active Python 3? James wrote: In episode #273, you guys were discussing supporting "Python 3" to mean any currently supported version of Python rather than "Python 3.7+" or similar. That's a really bad idea. There are still tons of people using unsupported versions of Python, and they're not all invalid use cases. For example, I am one of the upstream maintainers for cloud-init, and I was only recently able to remove Python 3.5 in order to make 3.6 our minimum supported version (which will continue for the next year). The reason is that our main consumers are downstream distro packagers (ubuntu, red hat, fedora, etc), and it's not uncommon for software released into long-term supported OS releases to be supported for 5-10 years or more. If I fire up an Ubuntu Trusty container, which still receives extended support until 2024, I get Python 3.4. So even though 3.4 is unsupported by Python upstream, it is still absolutely in use and supported by OS manufacturers. Joke: A case of the Mondays

Automation is a key component of most software development initiatives. It's not just for testing, it also figures into the build process, Continuous Integration (CI), and Continuous Delivery (CD). To that end, having a stable automation framework makes a lot of sense but what exactly goes into making that framework? Today, Matthew Heusser and Michael Larsen have a chat with Chris Loder, the "Rogue Automator" about where to start, what to include, and four specific areas every good automation framework must have to succeed.

Jerzy Wickowski opowiada o Continuous Integration (CI), Continuous Delivery (CD) oraz Continuous Deployment (CD). Temat jest ściśle powiązany z DevOps i niekoniecznie niezbędny dla osoby wchodzącej do branży IT. Jak się jednak okazuje, może to być idealny sposób na wyróżnienie się na tle konkurencji.Pełen opis odcinka: https://devmentor.pl/b/czym-jest-ci-cd || devmentor.pl/rozmowa ⬅ Chcesz przebranżowić się do IT i poznać rozwiązania, które innym pozwoliły skutecznie znaleźć pracę? Jestem doświadczonym developerem oraz mentorem programowania – chętnie odpowiem na Twoje pytania o naukę programowania oraz świat IT. Umów się na bezpłatną, niezobowiązującą rozmowę! ~ Mateusz Bogolubow, twórca podcastu Pierwsze kroki w IT || devmentor.pl/podcast ⬅ Oficjalna strona podcastu

Are you now working with source code? Whether that's Application Code, Infrastructure as Code, Database Schemas or Data Science workbooks as code, you may have heard of a term 'Continuous Integration' (CI). This is the process of regularly merging code, and running a series of automated builds/tests/checks to ensure that quality remains high in your production codebase. Find out more in this video.

Follow us on Twitter: https://www.twitter.com/jaredpotter •• https://www.twitter.com/juanlizarazog Why is it important to learn, understand, and practice continuous integration (CI) in 2021+? Where do I start with CI? In our latest episode, Juan Lizarazo and Jared Potter discuss getting started with CI using the best, most available, and often free Continuous Integration (CI) tools & platforms! Learning to understand CI will improve your software development efficiency to build even faster! Most importantly, grasping CI concepts will undoubtedly impress in your next technical interviews! --- Support this podcast: https://anchor.fm/devbootcamplife/support

Continuous Integration (CI) is slowly becoming one of the main pillars for software development. As our software becomes more complex we add more and more tooling around it to automate, so we can focus on whats important - writing code. CI is what runs most of that tooling and keeps it out of the way.. until we need break something and it needs our attention. It gives us the confidence to deploy, again and again so that we move faster in this rapidly changing world.

The Angular Show panelists (Aaron Frost, Brian Love, Alisa Nicoll, and Shai Reznik) chat with the co-founders of Narwhal Jeff Cross and Victor Savkin about Nx and Nx Cloud. But first, we check in with Jeff, who you may not know, has and cuddles with pigs, and Victor, who is a new father.Nx Cloud is a way for you to enable distributed computation cache such that you, your team, and your Continuous Integration (CI) can share build artifacts. Practically speaking, this results in saving you and your organization time when building and testing your application.You might be wondering, what exactly is computation cache? Victor breaks this down for us and shares how Nx tackles this, and further, how we can use Nx cloud to distribute the computation cache across a team, including CI.To get started, you'll need to be using Nx, which not only tackles computation cache, but is a tool for implementing a monorepo strategy. Then, set up Nx Cloud with an access token in your config for distributing the cache.

We've talked about frames adding up to worldviews adding up to cultures, but it all feels pretty vague in its possible importance. We need some informal sense of how this works in practice. In the immortal words of Brian Marick, "an example would be handy right about now." Continuous Integration (CI) is the practice of frequently cycling code through the source vault. People practicing CI do this several times a day. In "git" terms, they both pull/merge/push, depending on language & task, once every 15-90 minutes. Episode 32 is live! If you are interested in becoming a part of the conversation, Click here to join the Change-Harvesting Camerata Today! --- If you have any feedback you can always tweet @GeePawHill on Twitter, or drop a voice message via the voice messages link here on Anchor. You can also read the full transcription of this podcast over on GeePawHill.org. --- Send in a voice message: https://anchor.fm/geepawhill/message

Vem comigo saber como deixar seu Kubuntu mais atualizado do que o KDE Neon! Whaaaaatttttt????? Kubuntu CI https://phabricator.kde.org/w/kubuntu/kci/ ---$$$--- ÚLTIMOS ÁLBUMS DO VARTROY ---$$$--- https://syl.vartroy.com https://whatif.vartroy.com https://daydreams.vartroy.com ---!!!--- NOVIDADE ---!!!--- O Podcast da Vartroy Tecnologia está disponível nas principais plataformas de podcast. Procure por "Vartroy Cast" no Spotify, Google Podcasts, Apple Podcasts, RadioPublic, Breaker, Stitcher e PocketCasts. --------------- VARTROY TECNOLOGIA --------------- Soluções inovadoras com Linux, software livre e open source - Consultoria - Terceirização de TI - Suporte e Manutenção - Desenvolvimento de sites - Tradução, revisão e versão - Interpretação - http://tecnologia.vartroy.com - tecnologia@vartroy.com - Ribeirão Preto / SP --------------- CONHEÇA TAMBÉM --------------- Vartroy Music Project - http://music.vartroy.com - https://www.youtube.com/user/vartroy - https://soundcloud.com/vartroy - https://vartroy.bandcamp.com - https://www.facebook.com/vartroyband Nosso blog de tecnologia - http://tec.vartroy.com.br --------------- SIGA-NOS --------------- - Facebook: https://www.facebook.com/vartroytec/ - Twitter: https://twitter.com/GarciaVartroy

Dreht die App-Pipeline auf! Willkommen zu unserer vierten (und vorerst letzten) Episode unserer kleinen „Mobile-Serie“ innerhalb des Podcasts - Daniel und Ron werden diesmal noch technischer. Daniel berichtet davon, wie Continuous Integration (CI) und Continuous Delivery (CD) bei XING innerhalb großer, verteilter App-Development-Teams gehandhabt werden. Verschiedenste OpenSource-Tools werden vorgestellt und der Prozess vom eingecheckten Code bis hin zur ausgelieferten App im Store erklärt. Der Einfluss von Beta-Testern und die Relevanz von Staged Rollouts werden genauso beleuchtet wie die Neuerungen im Release Prozess für Android P. Das Euch bereits bekannte OpenSTF Framework für Android findet auch hier wieder Erwähnung... Ihr dürft also gespannt sein - und jetzt viel Spaß mit dieser bis zum Bersten vollgepackten Folge! Sprecher: Ron Werner: https://www.xing.com/profile/Ron_Werner Twitter: https://twitter.com/ron_werner Daniel Knott: https://www.xing.com/profile/Daniel_Knott Twitter: https://twitter.com/dnlkntt Ressourcen online/erwähnte Frameworks: https://git-scm.com/ https://jenkins.io/ https://www.jetbrains.com/teamcity/ https://fastlane.tools/ https://openstf.io/ https://hockeyapp.net/ https://get.fabric.io/ https://developer.apple.com/testflight/ https://github.com/danger/danger https://www.graylog.org/ Über QualityMinds: www.qualityminds.de https://twitter.com/qualitymindsde Feedback & Themenwünsche an: christian.brandes@qualityminds.de

Brian talks with Anders Wallgren (@anders_wallgren, CTO of @ElectricCloud) about evolving technology and organizational culture, how to think about monolithic applications in today’s business context, the challenges of microservices, lessons learned from good CI practices, and emerging patterns to evolve existing applications. Show Links: Get a free eBook from O'Reilly media or use promo code PCBW for a discount - 40% off Print Books and 50% off eBooks and videos Electric Cloud website Electric Cloud blog (Anders' writings) Electric Cloud podcast (C9D9)
 Show Notes: Topic 1 - Welcome to the show. We had Sam Fell on about a year ago (Eps. #219) at DevOps Enterprise Summit 2015, but it’s good to reconnect with the folks at Electric Cloud. Give us some of your background and focus at Electric Cloud. Topic 2 - I’ve been reading several of your blogs lately about monoliths and microservices and how companies manage transitions. Let’s dig into that a little bit, especially how you frame the evolution process. Topic 3 - I feel like people can talk about DevOps and transformation and lots of other stuff, but if companies can’t do Continuous Integration (CI) well, then a lot of this stuff won’t ever happen. From a technology standpoint, is that the place for companies to start? Topic 4 - We hear many people talk about using the Strangler Pattern for breaking up monoliths, or re-architecting them. Are there other well-known ways to manage these transitions? Topic 5 - Obviously moving to microservices, or just building microservices makes your company a $Billion dollar unicorn, but what are some of the downsides? Not every company does very well as managing high levels of change and distributed-ness. Topic 6 - Can you give us a few examples of companies that have successfully managed a monolith to microservices migration? Feedback? Email:show at thecloudcast dot net Twitter:@thecloudcastnet YouTube:Cloudcast Channel

Check out and sign up for iOS Remote Conf! April 13-15th, 2016.   01:22 - Dominic Jodoin Introduction Twitter GitHub Blog 01:46 - Emma Trimble Introduction Twitter 02:03 - Travis CI Background and Origin @travisci Continuous Integration (CI) 06:27 - Travis CI vs Other CI Solutions CircleCI Jenkins 10:44 - Travis and Open Source Getting Set Up YAML 14:47 - iOS and Travis CI fastlane 16:04 - Testing and The Backend 21:17 - CocoaPods 22:41 - Support Swift 24:53 - Pricing and Cost 27:33 - GitHub Integration 29:27 - Setup and Tool Support Mercurial Picks Smoked Gouda Cheese (Jaim) Smooch (Dominic) Making voice calls in Slack (Emma) The Most Important Object In Computer Graphics History Is This Teapot (Andrew) Big John's Cajun Cheese (Andrew) 2016 Chocolate and Cheese Festival @ The Natural History Museum of Utah (Andrew)

Check out and sign up for iOS Remote Conf! April 13-15th, 2016.   01:22 - Dominic Jodoin Introduction Twitter GitHub Blog 01:46 - Emma Trimble Introduction Twitter 02:03 - Travis CI Background and Origin @travisci Continuous Integration (CI) 06:27 - Travis CI vs Other CI Solutions CircleCI Jenkins 10:44 - Travis and Open Source Getting Set Up YAML 14:47 - iOS and Travis CI fastlane 16:04 - Testing and The Backend 21:17 - CocoaPods 22:41 - Support Swift 24:53 - Pricing and Cost 27:33 - GitHub Integration 29:27 - Setup and Tool Support Mercurial Picks Smoked Gouda Cheese (Jaim) Smooch (Dominic) Making voice calls in Slack (Emma) The Most Important Object In Computer Graphics History Is This Teapot (Andrew) Big John's Cajun Cheese (Andrew) 2016 Chocolate and Cheese Festival @ The Natural History Museum of Utah (Andrew)

Kohsuke Kawaguchi (@kohsukekawa) creator of Jenkins and CTO of Cloud Bees (@CloudBees) – (not Code Bees, lol) – joins us this week on The Hot Aisle to talk about Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment (The other CD) – and why working in a circle is a good thing – with the right […]

Lead Agile coach at Western Digital Steve Sanoff discusses some of the technical aspects of his work coaching in the content solutions department of the company. He has his hands full with six teams operating under a model similar to Spotify's leveraging Continuous Integration (CI), two-week Sprints and a quick two-month release cycle. Steve presented on "The Funny Thing About Not Being Agile" at AgileCamp. The presentation touched on how the stupid things that people do when learning how to do and be Agile can be funny in retrospect. He also shared stories that coaches might be able to use in the field to tactfully show a client that someone else had a similar bonehead idea and the results were later laughable.

In the first "Fragment" installment we're going to talk about Continuous Integration (CI) and Collective Code Ownership (CCO). Donn talks about what CI is, why its important and how it benefits you and your team. He then dives right into CCO and how it can be facilitated through testing.

Check out RailsClips on Kickstarter!!   01:56 - Testing and Test-Driven Development (TDD) The iPhreaks Show Episode #92: Unit Testing with NatashaTheRobot 03:23 - Panel Experiences with TDD Unit Testing The Difference Between Faking, Mocking, and Stubbing 08:10 - Value Objects 09:08 - How To Do TDD “Red, Green, Refactor” BDD (Behavior-Driven Development) The Cucumber Book: Behaviour-Driven Development for Testers and Developers  by Matt Wynne and Aslak Hellesøy The RSpec Book: Behaviour-Driven Development with RSpec, Cucumber, and Friends  by David Chelimsky, Dave Astels, Zach Dennis, Aslak Hellesøy, Bryan Helmkamp, Dan North 11:28 - Jaim’s TDD Process 13:44 - Value and Getting Started with Testing Ruby Rogues Episode #178: Refactoring Ruby with Martin Fowler 21:58 - Writing Tests First “If Code is Easy to Test, It’s Easy to Change.” 27:18 - Testing on a Team Automation guard (Ruby) clang Continuous Integration (CI) 32:47 - Higher Level Testing 36:54 - KIF 38:00 - Other Ways of Testing UIs 39:44 - Who Writes the Tests? 44:06 - Test Data and Environments Test Time => Feedback 46:50 - Lower-level to Higher-level Tests Transition Value ROI (Return on Investment) 51:51 - Recording User Interactions Picks John Reid: UIViewController TDD [Screencast] (Jaim) Test-Driven iOS Development (Developer's Library) by Graham Lee (Jaim) WatchKit FAQ (Alondo) This Idea Must Die: Scientific Theories That Are Blocking Progress (Edge Question Series) by John Brockman (Alondo) Martin Fowler: The Test Pyramid (Pete) Working Effectively with Unit Tests by Jay Fields (Pete) Avery Brewing IPA (Pete) A Wizard of Earthsea by Ursula K. Le Guin (Chuck) 80/20 Sales and Marketing: The Definitive Guide to Working Less and Making More by Perry Marshall (Chuck) Miracles and Massacres: True and Untold Stories of the Making of America by Glenn Beck (Chuck)

Check out RailsClips on Kickstarter!!   01:56 - Testing and Test-Driven Development (TDD) The iPhreaks Show Episode #92: Unit Testing with NatashaTheRobot 03:23 - Panel Experiences with TDD Unit Testing The Difference Between Faking, Mocking, and Stubbing 08:10 - Value Objects 09:08 - How To Do TDD “Red, Green, Refactor” BDD (Behavior-Driven Development) The Cucumber Book: Behaviour-Driven Development for Testers and Developers  by Matt Wynne and Aslak Hellesøy The RSpec Book: Behaviour-Driven Development with RSpec, Cucumber, and Friends  by David Chelimsky, Dave Astels, Zach Dennis, Aslak Hellesøy, Bryan Helmkamp, Dan North 11:28 - Jaim’s TDD Process 13:44 - Value and Getting Started with Testing Ruby Rogues Episode #178: Refactoring Ruby with Martin Fowler 21:58 - Writing Tests First “If Code is Easy to Test, It’s Easy to Change.” 27:18 - Testing on a Team Automation guard (Ruby) clang Continuous Integration (CI) 32:47 - Higher Level Testing 36:54 - KIF 38:00 - Other Ways of Testing UIs 39:44 - Who Writes the Tests? 44:06 - Test Data and Environments Test Time => Feedback 46:50 - Lower-level to Higher-level Tests Transition Value ROI (Return on Investment) 51:51 - Recording User Interactions Picks John Reid: UIViewController TDD [Screencast] (Jaim) Test-Driven iOS Development (Developer's Library) by Graham Lee (Jaim) WatchKit FAQ (Alondo) This Idea Must Die: Scientific Theories That Are Blocking Progress (Edge Question Series) by John Brockman (Alondo) Martin Fowler: The Test Pyramid (Pete) Working Effectively with Unit Tests by Jay Fields (Pete) Avery Brewing IPA (Pete) A Wizard of Earthsea by Ursula K. Le Guin (Chuck) 80/20 Sales and Marketing: The Definitive Guide to Working Less and Making More by Perry Marshall (Chuck) Miracles and Massacres: True and Untold Stories of the Making of America by Glenn Beck (Chuck)

A frank discussion of Continuous Integration

A frank discussion of Continuous Integration