Podcasts about cloudbees

“Now more than ever, engineering leaders are being asked to be more transparent with how their work is getting done. Every single thing that an engineering team works on needs to benefit the business.” Laura Tacho is the CTO of DX and a leading voice in the world of developer experience and productivity. In this episode, we explore the ever important role of aligning developer experience with business goals and discuss the DX Core 4, a new developer productivity framework recently published by DX. Laura shares how engineering leaders can leverage intuition for data-driven decisions and effectively communicate the impact of engineering initiatives in business language. We discuss the importance of balancing business goals with engineering needs and delve into the process of building a strong business case for improving developer experience. Discover the new DX Core 4 framework as Laura breaks down its four dimensions, key metrics, and actionable strategies for measuring and enhancing developer productivity. Learn how DX Core 4 complements existing frameworks, such as DORA, SPACE, and DevEx, and why it suggests “diffs per engineer” as a valuable metric to measure. Understand the Developer Experience Index (DXI) and why internal developer platforms and AI play crucial roles in improving developer experience. Tune in to learn new valuable insights on developer experience and how to measure, communicate, and improve developer productivity effectively.   Listen out for: Career Turning Points - [00:02:13] Following Your Intuition - [00:05:36] Business Oriented Engineering Leaders - [00:08:06] Explaining Tech Debt - [00:12:01] Balancing Between Engineering and Business Focus - [00:16:53] Building a Case for Improving Developer Experience - [00:21:00] DX Core 4 - [00:22:46] DX Core 4 vs Others (DORA, SPACE, DevEx) - [00:25:19] The DX Core 4 Dimensions - [00:26:49] Diffs per Engineer - [00:30:32] Impact Dimension - [00:33:27] Measuring DX Core 4 - [00:34:59] Developer Experience Index (DXI) - [00:38:19] Impact of Implementing DX Core 4 - [00:41:54] Best Strategy to Improve Developer Experience - [00:44:26] Internal Developer Platform & AI - [00:47:52] The Importance of Talking to the Developers - [00:51:40] 3 Tech Lead Wisdom - [00:54:18] _____ Laura Tacho's BioLaura Tacho is CTO at DX, a developer experience company. She's a technology leader with a successful track record leading engineering and product development teams at companies like CloudBees, Aula Education, and Nova Credit. She's been building developer tools and working on improving developer productivity for over 10 years, all the way from the heyday of IaaS and PaaS on cloud, through Docker and containers, CI/CD, and now as part of DX. She's also an executive coach for engineering leaders and an expert in building world-class engineering organisations that consistently deliver outstanding results. Laura has coached CTOs and other engineering leaders from startups to the Fortune 500, and also facilitates a popular course on metrics and engineering team performance. Follow Laura: Website – lauratacho.com LinkedIn – linkedin.com/in/lauratacho DX Core 4 – getdx.com/research/measuring-developer-productivity-with-the-dx-core-4 Developer Productivity Metrics Course - lauratacho.com/developer-productivity-metrics-course _____ Our Sponsors Enjoy an exceptional developer experience with JetBrains. Whatever programming language and technology you use, JetBrains IDEs provide the tools you need to go beyond simple code editing and excel as a developer.Check out FREE coding software options and special offers on jetbrains.com/store/#discounts.Make it happen. With code. Manning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats. Like this episode?Show notes & transcript: techleadjournal.dev/episodes/198.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Fun fact #1:   90% of software developed today comprises third-party apps. Fun fact #2:  48% of organizations have over one hundred tools in the toolchain. What could go wrong? Today, we sat down with Ben Chicoski from CloudBees. He discusses the evolution of software development, emphasizing the importance of testing in the software delivery lifecycle. CloudBees acquired Launchable to use AI to analyze test patterns and results to surface only important tests. He highlights that up to 80% of tests are unnecessary, consuming significant developer time.  CloudBees leverages AI and machine learning to optimize testing, reduce waste, and improve efficiency.  The conversation also touches on the importance of continuous improvement, trustworthy pipelines, and the future challenges and opportunities in federal software development. This discussion includes release orchestration and how it addresses the unintended consequences of increased development speed. https://content.leadquizzes.com/lp/fk1JL_FgeQ Connect to John Gilroy on LinkedIn   https://www.linkedin.com/in/john-gilroy/ Want to listen to other episodes? www.Federaltechpodcast.com

Our big story this week is from AMD. They're opening up their wallet to the tune of nearly $5 billion to buy ZT Systems. The two companies have had a preexisting partnership, with ZT having collaborated on the EPYC processor lines. ZT's biggest customers are AWS and Azure, as ZT specializes in hyperscale AI systems that are bought by the rack. This move follows a very recent acquisition of Silo AI, which we covered on the Rundown, as well as their last big acquisition of Xilinx. There's a lot to unpack here and the Futurum Group has had some amazing coverage of this deal so far. Stephen, let's start with you. What does ZT Systems have that makes them so attractive to AMD. Time Stamps: 0:00 - Welcome to the Rundown 1:48 - Morpheus Data Acquired by HPE 5:31 - Launchable Acquired by CloudBees 8:26 - Kioxia Reveals Broadband SSD 12:43 - DigiCert to Acquire Vercara to Expand Security Portfolio 16:25 - Western Digital Races Past NetApp with All-Flash OpenFlex 20:11 - Massive Data Leak From Plaintext Passwords 24:34 - ZT Systems to be Acquired by AMD 40:15 - The Weeks Ahead 42:19 - Thanks for Watching Hosts: Tom Hollingsworth: https://www.twitter.com/NetworkingNerd Stephen Foskett: https://www.twitter.com/SFoskett Follow Gestalt IT Website: https://www.GestaltIT.com/ Twitter: https://www.twitter.com/GestaltIT LinkedIn: https://www.linkedin.com/company/Gestalt-IT Tags: #Rundown, #CyberSecurity, #EPYC, @AMD, @ZTSystems, @WesternDigital, @NetApp, @DigiCert, @Vercara, @Kioxia, @Launchable, @CloudBees, @MorpheusData, @HPE, @GestaltIT, @TechFieldDay, @TheFuturmGroup, @Sfoskett, @NetworkingNerd,

This week on the Revenue Insights Podcast, we are joined by Anthony Palladino, Chief Revenue Officer, Blake Kelly, Head of Enablement and Partnerships and Kirsten Vonck, Head of Customer Success at Mabl. In this episode, Lee, Anthony, Blake and Kirsten explore how the Value Hypothesis framework goes beyond basic discovery to drive sales success and improve customer lifecycle management. They delve into strategies for building trust, creating compelling value propositions, and fostering consultative relationships. They further delve into the importance of understanding customer environments, maintaining credibility, and continuously iterating on account plans. Additionally, they share insights on leveraging AI and other technologies to enhance the sales process and deliver consistent value to clients. Anthony is a growth leader with a track record of driving significant revenue increases and building robust customer-facing organizations. At Splunk, he led the Americas Field Organization from pre-IPO to $1 billion in revenue, and as Chief Revenue Officer at Aisera, he increased revenue eightfold. Before joining Mabl, where he will drive global adoption of their low-code intelligent test automation, he quadrupled revenue as Senior Vice President at CloudBees. Blake is a high-performing professional with over a decade of experience in customer-facing roles, who founded the Postman GTM Enablement motion. He is now leveraging his extensive expertise to empower Mabl's Go-To-Market team. Kirsten is an Experienced Customer Success Leader with a demonstrated history of working in the SaaS industry with a specific concentration in cloud computing and QA automation.

This podcast interview focuses on the entrepreneurial journey to solve the non-trivial testing problems of some companies that we all blindly rely on . My guest is Harpreet Singh, Co-CEO of Launchable. Harpreet is an entrepreneur, innovator, developer, creative product leader, and seasoned DevOps leader who has dedicated his life to building new solutions for software teams. He's got extensive product marketing & Product management experience at Sun Microsystems.  Then helped CloudBees find product market fit and create a business based on OSS that scaled to multi-millions in ARR. Then moved to Atlassian where be became the GM for Atlassian Bitbucket, where he helped set the blueprint of what became the strategy at Atlassian to embrace DevOps tools in the market. In September 2019 he co-founded Launchable and shares the CEO role.   Their mission: Help dev teams launch fearlessly. Their point of view: 80% of software tests are pointless. We'll help you see the 20% that matters most. And this inspired me, and hence I invited Harpreet to my podcast. We explore what's broken around software testing these days. Harpreet provides his vision of how to address this. He elaborates on the journey of building an AI-powered software delivery platform and shares his most valuable go-to-market lessons - particularly why he didn't opt for a product-led growth motion and how he avoided getting stuck in red oceans. Last but not least, he shares his advice to peer SaaS CEOs on scaling their businesses while staying true to their core mission. Here's one of his quotes I spent a year and a half at Atlassian. They are the Gurus of product lead growth. So I got to see that close enough. And I came in and said we should probably do this. And I came to the realization that it's not one size fits all. Different teams have different needs, and the kinds we are serving have very different needs, then this product led growth. During this interview, you will learn four things: His lessons on how to simplify customer communication so it resonates optimally.  His advise on how to go beyond the obvious and find the biggest possible problem to solve for your ideal customers. How to choose your Go-to-Market model and what specifics to look for  How he landed BMW as one of his early customers and what that taught him. For more information about the guest from this week: Harpreet Singh Website: Launchable Subscribe to the Daily SaaS Reflection Get my free, 1 min daily reflection on shaping a B2B SaaS business no one can ignore. Subscribe here Yes, it's actually daily. And yes, people actually stay subscribed (Just see what peer B2B SaaS CEOs say) My promise: It's short. To the point. Inspiring. And valuable. Learn more about your ad choices. Visit megaphone.fm/adchoices

Shiv our host is in conversation with Harpreet SIngh, CO-founder and co-CEO of Launchale Inc. Harpreet has been associated with conceiving and launching many innovative products that have become a standard among developer community. In today's conversation he talks aboutHow he started his career in India and then moved to the US. He emphasizes the importance of continuous learning and self-improvement. He mentions his growth mindset and his habit of reading and taking courses to stay updated.Harpreet acknowledges the challenge of scaling himself as a leader alongside the company. He talks about managing time for both work and personal growth. He highlights the importance of clear communication and context setting to empower his team and free up his time. He also mentions using a prioritization technique where he identifies the top three important tasks for both work and personal life. Harpreet acknowledges the resistance developers often have towards documentation. He discusses how he built his team by looking for individuals who value clear communication and writing skills. He describes how he identified a niche in the developer experience (DevEx) domain. He noticed that even after implementing CI/CD practices, companies weren't seeing the desired benefits quickly enough. This led him to explore how AI and machine learning could improve software delivery pipelines.Launchable's product uses machine learning to predict which tests are likely to fail based on code changes. Launchable is now expanding its offering to include intelligent test failure diagnostics using AI and machine learning.Harpreet acknowledges that coding style can influence the likelihood of errors. Launchable considers this to some extent, but the focus is on broader patterns and historical data to predict test failures.He emphasizes the importance of lifelong learning for personal and professional growth.He also talks about careers in testing and tech in general: Harpreet is an entrepreneur, innovator, developer, and creative product leader who has dedicated his life to building new solutions for software teams. His latest iteration is Launchable Inc, an AI/ML company to help developers and QA. A seasoned DevOps leader, Harpreet has been building products for developers for the last 25+ years.Previously, he was GM for Atlassian Bitbucket and VP of Product at CloudBees. At CloudBees he helped create the Jenkins business that scaled to multi-millions in ARR.He has an MBA from Santa Clara University, an MS in CS from the University of Cincinnati, and a Bachelors in Computer Engineering from Pune University, India.

Durante una sua visita a Milano, abbiamo fatto due chiacchiere con Sacha Labourey, CEO e co-fondatore di CloudBees, una delle principali realtà nell'ambito del software development in Cloud. Il mondo del Cloud sta cambiando. "Il cloud ci ha aperto le porte a capacità di elaborazione e archiviazione praticamente illimitate, su richiesta, con costi basati sull'effettivo utilizzo. Questo ha democratizzato l'accesso a infrastrutture sofisticate, una volta prerogativa esclusiva delle grandi aziende", sostiene Sacha. L'avvento dell'intelligenza artificiale, in particolare dei Large Language Models (LLM), nel cloud, segna un ulteriore passo avanti, offrendo livelli di sofisticazione e potenza inimmaginabili fino a pochi anni fa.Lo sviluppo di applicazioni cloud native rappresenta un vero e proprio acceleratore per le imprese, consentendo loro di offrire servizi innovativi a costi contenuti. "Stiamo assistendo a un cambiamento radicale, con un numero crescente di applicazioni che verranno eseguite nel cloud. Questo rappresenta una sfida, ma anche un'opportunità immensa per le aziende di tutte le dimensioni," afferma Sacha.L'adozione di metodologie DevOps e DevSecOps ha trasformato i cicli di sviluppo software. "La capacità di rilasciare aggiornamenti più frequentemente ha reso le aziende più affidabili e reattive. Questo è fondamentale in mercati dinamici, dove la capacità di adattarsi rapidamente può determinare il successo o il fallimento," osserva Sacha.La chiacchierata con Sacha Labourey getta luce su un futuro tecnologico in rapida evoluzione, dove il cloud si conferma come un potente catalizzatore di cambiamento. Le sue parole sono un monito e al tempo stesso un invito alle imprese a cogliere le opportunità offerte da questa rivoluzione digitale.Buon ascolto!

Laura Tacho, CTO @ DX, joins us to discuss why changing what you measure doesn't necessarily lead to improved productivity (and what to do about it)! How to define and measure productivity in your eng org is one of the hottest topics for eng leaders… We cover best practices for identifying what productivity looks like in your org, what motivates your team to reach those goals, how to harness behavioral psychology, and antipatterns to avoid when you focus on productivity. Plus Laura shares some of her favorite practices to identify your skill gaps, and how define what success looks like for yourself and your teams on your productivity journey.ABOUT LAURA TACHOLaura Tacho is CTO at DX, a developer experience company. She previously led teams at companies like CloudBees, Aula Education, and Nova Credit. She's an expert in building world-class engineering organizations that consistently deliver outstanding results. Laura has coached CTOs and other engineering leaders from startups to the Fortune 500, and also facilitates a popular course on metrics and engineering team performance."That is just a ripe environment for the rapid degradation of trust within an organization and has immeasurable consequences when it comes to degrading the culture of a team. I think the temptation is there, understandably, and I think from good intentions of, ‘I want to try to measure unobtrusively. I want to get this data about my team without them knowing about it or minimally knowing about it so that I'm not bothering them.' That is a trap because we don't need to treat people the same way we treat distributed systems with dashboards and dashboards of telemetry data. People can talk. Just ask them.”- Laura Tacho   This episode is brought to you by incident.ioincident.io is trusted by hundreds of tech-led companies across the globe, including Etsy, monday.com, Skyscanner and more to seamlessly orchestrate incident response from start to finish. Intuitively designed, and with powerful and flexible built-in workflow automation, companies use incident.io to supercharge incident response and up-level the entire organization.Learn more about how you can better identify, learn from, and respond to incidents at incident.ioInterested in joining an ELC Peer Group?ELCs Peer Groups provide a virtual, curated, and ongoing peer learning opportunity to help you navigate the unknown, uncover solutions and accelerate your learning with a small group of trusted peers.Apply to join a peer group HERE: sfelc.com/peerGroupsSHOW NOTES:Why people care so much about measuring productivity in engineering (3:25)Antipatterns to avoid when tightening focus on productivity (5:08)The role of behavioral psychology with engineering productivity (7:04)What the ideal consulting relationship looks like structurally (8:58)Ensure you're incentivizing the behavior you want to achieve (12:20)How to cultivate the skill of influencing without feeling too “salesy” (13:59)Understanding the different facets / types of motivation (17:08)Strategies for developing resiliency in “do more with less” environments (19:14)Behaviors that prevent eng orgs & leaders from achieving their goals (23:55)How to identify areas of personal development & closing the skill gap (27:00)Areas that are the most ripe for setting the right expectations / outcomes (29:40)Best practices for eng leaders to gain clarity & define what success looks like (32:01)Rapid fire questions (35:52)LINKS AND RESOURCESRemarkably Bright Creatures -Shelby Van Pelt's exploration of friendship, reckoning, and hope, tracing a widow's unlikely connection with a giant Pacific octopus.This Podcast Will Kill You - Grad students studying disease ecology, Erin and Erin found themselves disenchanted with the insular world of academia. They wanted a way to share their love of epidemics and weird medical mysteries with the world, not just colleagues.lauratacho.com - Laura's website where you can find more information about her courses, coaching, and management program.This episode wouldn't have been possible without the help of our incredible production team:Patrick Gallagher - Producer & Co-HostJerry Li - Co-HostNoah Olberding - Associate Producer, Audio & Video Editor https://www.linkedin.com/in/noah-olberding/Dan Overheim - Audio Engineer, Dan's also an avid 3D printer - https://www.bnd3d.com/Ellie Coggins Angus - Copywriter, Check out her other work at https://elliecoggins.com/about/

Quoi de neuf dans l'univers du CI/CD ? Echange avec Sacha Labourey de CloudBeesHébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

An airhacks.fm conversation with Paul Sandoz (@paulsandoz) about: bbc micro, Archimedes was the start of ARM, the Elite game, writing a painting application, graphics protocol emulation, studying cybernetics, remote control of production factories, developing a VR headset, using Silicon Graphics machines, building a 3D engine, working on Sun Microsystems on the CDE environment, switching to XML technology group at Sun Microsystems, Apache Jelly, SOAP was the past of least resistance, the WS-* specifications, Roy Fielding and Representational State Transfer (REST) architecture style, starting to work on JAX-RS, the Convention over Configuration trade-offs, joining CloudBees to work Kohsuke Kawaguchi "#143 How Hudson and Jenkins happened", starting at Oracle's Java team to work on project Jigsaw and Streams Paul Sandoz on twitter: @paulsandoz

Welcome to another episode of Category Visionaries — the show that explores GTM stories from the tech's most innovative B2B founders. In today's episode, we're speaking with Harpreet Singh, Co-Founder and Co-CEO of Launchable, a software testing platform that has raised over $12 Million in funding. Launchable is at the forefront of revolutionizing software testing by significantly reducing testing times through predictive test selection, leveraging machine learning to enhance development efficiency.   Here are the most interesting points from our conversation: Harpreet's Transition from Big Companies to Startups: After spending a decade at Sun Microsystems, Harpreet discovered his preference for the dynamic startup environment, leading to roles at CloudBees and Atlassian before launching his venture, highlighting the journey from an engineer to an entrepreneur. Admiration for People-focused Leadership: Harpreet respects founders who prioritize building a great culture and listening to their team. He aims to replicate these values at Launchable, demonstrating the impact of leadership style on company culture and growth. The Co-CEO Model's Success: Drawing inspiration from Atlassian, Harpreet and his co-founder adopted the Co-CEO model, finding it beneficial for making balanced decisions and dividing responsibilities based on strengths, which has contributed significantly to Launchable's strategic development. Innovative Solution to a Common Problem: Launchable addresses the inefficiency in software testing by introducing predictive test selection. This solution, which reduces testing times by up to 80%, showcases the company's commitment to enhancing the software development lifecycle. Strategic Early Customer Engagement: Securing BMW as an early customer through a product advisor program was pivotal. It not only validated Launchable's market fit but also demonstrated the potential for startups to engage with large enterprises effectively. Vision for the Future and Category Creation: Harpreet shares his vision for Launchable's future, focusing on expanding the scope of their solution to encompass broader issues in the bug and issue triaging space. This ambition illustrates the company's goal to define a new subcategory within software testing, emphasizing test failure intelligence and management.

Anthony Palladino is the Chief Revenue Officer at mabl. mabl is the enterprise SaaS leader of intelligent, low-code test automation that empowers high-velocity software teams to embed automated end-to-end tests into the entire development lifecycle.Prior to mabl, Anthony spent five years at Splunk from pre-IPO through $1 billion in revenue as the leader of their Americas Field Organization. As Chief Revenue Officer at Aisera, the industry's first AI Service Management solution, he helped define the company's product market fit, built and ramped their customer-facing functions, and increased revenue eightfold. Prior to Aisera, Anthony was the Senior Vice President at CloudBees overseeing global field operations. In just over three years, CloudBees quadrupled its revenue. A holistic growth leader with experience in building customer-facing organizations, go-to-market strategies, and diverse partner networks.In this conversation with John McMahon, Anthony discusses the importance of focusing on the little things in sales to drive big results. He emphasizes the need for disciplined execution, maintaining urgency with customers, and developing compelling energy in sales conversations. By identifying the deltas and addressing them, sales teams can build good habits and drive successful outcomes. Palladino also highlights the significance of documenting fit and gaining consensus in sales conversations.HERE ARE SOME KEY SECTIONS TO CHECK OUT:[00:02:03] Overview of Mabl and its impact on revenue, profitability, and risk[00:05:26] Top priorities for exploring with the salesforce[00:08:02] Importance of focusing on the little things that make a big difference[00:11:01] Example of using a sequence to drive pipeline generation[00:20:26] Importance of identifying and teaching people the knowledge areas[00:32:59] Creating compelled energy to compel customers to move forward[00:39:18] Importance of documenting the fit and gaining consensus in the first meeting[00:44:46] The components of compelled energy and the exit criteria for the first meeting[00:50:41] Importance of documenting customer requirements and identifying champions[00:55:24] The challenges of being a CRO and the importance of hiring well[00:58:00] Building a leadership team and establishing a common goalHIGHLIGHT QUOTES[00:53:41] "Who do we think is the champion? Right? And it's probably who do we think is the champion? Because an understanding if you're new to the organization, there's probably not a firm notion of what a champion is. And, you know, the definition we have is person with political respect and or technical authority who fights for us when we're not there and I have the and or in their job, because I think in a lot of cases with consensus, certain environments, those 2 things are very distinct today in some cases." - Anthony Palladino[00:57:59] “I think establishing a leadership team that is with each other. They're supporting each other. They're with each other. You're sharing that common goal to the mission. And but doing it, you know, as people and really creating that that's that's I think it doesn't come easy because you have to create a special relationship.” - Anthony Palladino Learn more about Anthony through this link:LinkedIn: https://www.linkedin.com/in/anthonypalladino/Check out John McMahon's book here: https://www.amazon.com/Qualified-Sales-Leader-Proven-Lessons/dp/0578895064

It seems like everybody in federal information technology was at the AWS Washington, DC event a couple of weeks ago.  We didn't manage to interview Tyler Johnson from the floor, so we got him on a Zoom call to explain how his company can help federal leaders achieve the goals for their agency. Tyler Johnson says that CloudBees can take all the point providers at the AWS event and wrangle them into one continuous build.  This allows a kind of unified test and deployment for software pipelines. Ok, let's make this simple.   A bee goes from flower to flower and gathers pollen.  CloudBees gives federal agencies the ability to gather data from a wide variety of sources.  During the interview Tyler Johnson presented a scenario many federal techs leaders face.  They must submit projects to a release board.  If one uses traditional methods, it would be difficult to adjust artifacts or move them to different parts of the development cycle.  Because today's systems are so complex, it is a major task to coordinate this test and deploy pipeline. The trending phrase used today to manage this is called “release orchestration.”  This is important in the agile software development approach where you may have different work streams and many microservices to coordinate.  Listen to the interview to understand how CloudBees can give you a bird's eye view of managing releases of software to be able to accomplish the noble goal of continuous improvement.   Follow John Gilroy on Twitter @RayGilray Follow John Gilroy on LinkedIn  https://www.linkedin.com/in/john-gilroy/ Listen to past episodes of Federal Tech Podcast  www.federaltechpodcast.com  

An airhacks.fm conversation with Dave Johnson (@snoopdave) about: PDP-8 with a paper tape reader, airhacks.tv questions and answers, TRS-80, playing asteroids, asteroids, Defender and Battlezone were based on vector graphics, learning Pascal and C, Data General Eclipse MV/8000, Geographic Resources Analysis Support System (GRASS GIS), working for University of Kingston, working on jfactory for Rouge Wave, HAHT Software, The Soul of a New Machine, distributed Visual Basic application server, using xdoclet to generate EJB, using castor for persistence, Apache Roller started as sample application, Sun hires dave, working on Lotus Notes social, starting at wayin, Roller supports Pingback, Lotus is using roller, using Rightscale to deploy Java software to AWS, using Jenkins and CloudFormation, episode with Scott McNealy "#19 SUN, JavaSoft, Java, Oracle", Roller uses Apache Velocity, working on RSS parser Rome, switching from MongoDB to Apache Cassandra, UserGrid data store, Oracle acquires apiary , starting at CloudBees, episode with Kohsuke Kawaguchi "#143 How Hudson and Jenkins happened", starting at Apollo, several thousand blogs on roller Dave Johnson on twitter: @snoopdave

On this episode, we were joined by Jeanne Talbot, a customer marketing and communications leader that has worked at companies like CloudBees, Lexmark International and Intel. She has a unique perspective due to her background in PR and customer marketing and came on the show to share some creative ways to build relationships that can...

A “Meet The Team” FFP interview with Stellate's Head of Customer Success Marko Locher. Marko is an experienced Customer Success professional with a history of working in developer tooling and startups. He spent the last couple of years learning all about and helping people with Continuous Integration and Delivery at companies like CloudBees and CodeShip. In his spare time, Marko enjoys skiing and sailing, among a lot of other outdoor activities. You can also find him reading the newest Expanse novel at Vienna's Donaukanal, or enjoying a coffee in one of the city's many cafes. Hear Marko's perspective on: Support and Customer Success Origins Austrian Stereotypes Quality Customer Support Responsive Organisations Documentation Great Customer Success Teams Avoidable Internal Struggles Getting Into Customer Success CodeShip CloudBees Acquisition Getting Into Startups Future Startup Plans Berlin Experience Stellate's Founder Support Voicing Ideas Avoidable Startup Nightmares Burnout Hustle Culture Sailing Instructor Life COVID Years Remote Office Environment Unhealthy Habits Decompress Strategies Joining Stellate Getting Into GraphQL GraphQL's Possible Future GraphQL Community Excitement About Stellate European Startup Ecosystem Austrian Startup Mindset Twitter: @mlocher LinkedIn: https://www.linkedin.com/in/markolocher/

Kohsuke Kawaguchi, the creator of Jenkins, pulls back the curtain on building tech companies in Japan. He shares his lessons from Cloudbees and how building two very different engineering organizations from the ground up showed him the importance of diversity in engineering teams. Deep dive into the topics discussed in this episode at go.developingleadership.co/ep29 Join the discussion and follow us on twitter @ devleadership_ Developing Leadership is a podcast presented by Athenian. We are introducing the world of engineering to metrics and data that improve processes and help teams. If you want to learn more about data-enabled engineering, go to athenian.com

Welcome onboard on our 4th episode of DevOps World Radio with Kohsuke Kawaguchi, Sacha Labourey and Ian O'Brien. On this episode, we are going to talk about DevOps implementations, the successes and the challenges through the eyes of two industry veterans - Kohsuke and Sacha. And Ian tells us about what role data, ML and AI can play in helping practitioners do DevOps better. Everybody that's out there thinking they are doing DevOps really well or planning to do DevOps, or anywhere along the journey - sometimes you get 5-10 years into it and you go, we are the best in the world, we are just awesome at this, we are killing it at DevOps. But then the inside truth is always somewhere in between or not close to that statement. There might still be a long way to go and a lot of things that need to happen before you get really successful at it in both a practical and strategic sense. And that's ok! Being able to admit that there is a long way to go and finding ways to improve it, that's something we are going to have in this discussion and who better to discuss this than the two people who have been doing this for 25 years+. We are so excited to have two legendary personalities, who have probably seen some of the largest, most successful and probably some of the most challenging DevOps implementations in the market - Founder of Hudson Project and Jenkins, Kohsuke Kawaguchi and Founder and CSO of CloudBees, Sacha Labourey. 

A Future Founder Promise podcast clip from the full interview with the former VP of engineering and engineering leadership coach Laura Tacho. Laura helps with building high-performing dev teams. Previously she was leading engineering teams at Codeship and CloudBees. She partners with software engineering managers and executives to level up their leadership skills through courses, coaching and her engineering management program. You can find more information about her services here: lauratacho.com Hear Laura's perspective on: Obvious coaching benefits Coaching misconceptions Maintaining excellence Finding coaches "Chemistry Test" Practice space Winging leadership Skiing instructor training and much more… We are currently hiring for a lot of new positions at Stellate. If you got interested in potentially working with us, please take a look at our hiring page.

On this episode of The Marketer's Journey, I interview Shawn Ahmed, the CMO of CloudBees, a platform which provides the leading DevOps solutions for large and compliance-first organizations. We discuss how Shawn has helped to scale the company from 18 to 60 employees, the concept of using a “pod” when organizing your go-to market strategy, and the need for segmentation at different parts of the sales funnel.Check out this and other episodes of The Marketer's Journey on Apple Podcasts, Spotify, Stitcher, and Google Podcasts!Key takeaways from this episode:Take risks. Shawn mentioned that throughout his career, he's learned the most by taking big risks, such as moving from a CEO role to come on as CloudBees CMO. He believes that to really understand a business, you need to experience all elements of it rather than pigeonholing yourself to one area or specialty.Focus on segmentation. As a marketer, Shawn understands the value of really knowing your audience and what motivates them. This is why he places a strong emphasis on segmentation and identifying different strategies for different parts of the sales funnel.Personalization is key. Any good marketing strategy should be tailored to its audience, but Shawn reminds us that this is especially important at the top of the funnel because capturing initial interest is the most difficult aspect of the journey. As you move further down the funnel, personalization is not always as vital.Learn more about CloudBees here: https://www.cloudbees.com/ Learn more about Shawn here: https://www.linkedin.com/in/shawnahmed/

A Future Founder Promise podcast clip from the full interview with the former VP of engineering and engineering leadership coach Laura Tacho. Laura helps with building high-performing dev teams. Previously she was leading engineering teams at Codeship and CloudBees. She partners with software engineering managers and executives to level up their leadership skills through courses, coaching and her engineering management program. You can find more information about her services here: lauratacho.com Hear Laura's perspective on: What is coaching? Coaching stigma "Next level of greatness" Outside perspectives Common leadership problems "Coaching for everyone " Addressing fears Building trust Conflict aversion and much more… We are currently hiring for a lot of new positions at Stellate. If you got interested in potentially working with us, please take a look at our hiring page.

A Future Founder Promise podcast clip from the full interview with the former VP of engineering and engineering leadership coach Laura Tacho. Laura helps with building high-performing dev teams. Previously she was leading engineering teams at Codeship and CloudBees. She partners with software engineering managers and executives to level up their leadership skills through courses, coaching and her engineering management program. You can find more information about her services here: lauratacho.com Hear Laura's perspective on: DX responsibility Owning developer experience Autonomous teams Tips for ICs Developer productivity Relevant metrics SPACE framework Applied FOMO People-Process-Platform Small changes and much more… We are currently hiring for a lot of new positions at Stellate. If you got interested in potentially working with us, please take a look at our hiring page.

A Future Founder Promise podcast clip from the full interview with the former VP of engineering and engineering leadership coach Laura Tacho. Laura helps with building high-performing dev teams. Previously she was leading engineering teams at Codeship and CloudBees. She partners with software engineering managers and executives to level up their leadership skills through courses, coaching and her engineering management program. You can find more information about her services here: lauratacho.com Hear Laura's perspective on: DORA Metrics Assessing engineering orgs Productivity proxies The SPACE framework Developer experience focus Executive pressure Providing customer value Closing loops and much more… We are currently hiring for a lot of new positions at Stellate. If you got interested in potentially working with us, please take a look at our hiring page.

A Future Founder Promise podcast clip from the full interview with the former VP of engineering and engineering leadership coach Laura Tacho. Laura helps with building high-performing dev teams. Previously she was leading engineering teams at Codeship and CloudBees. She partners with software engineering managers and executives to level up their leadership skills through courses, coaching and her engineering management program. You can find more information about her services here: lauratacho.com Hear Laura's perspective on: Measuring developer productivity Productivity definitions DX Automatically generated metrics Productivity vs effectiveness Survey metrics "Elite teams" Telemetry data DORA metrics Continuous delivery Developer tooling bubble and much more… We are currently hiring for a lot of new positions at Stellate. If you got interested in potentially working with us, please take a look at our hiring page.

A FFP interview with the former VP of engineering and engineering leadership coach Laura Tacho. Laura helps with building high-performing dev teams. Previously she was leading engineering teams at Codeship and CloudBees. She partners with software engineering managers and executives to level up their leadership skills through courses, coaching and her engineering management program. You can find more information about her services here: lauratacho.com Hear Laura's perspective on: Coaching developers Managing teams Automated data collection vs survey data DX Having a strictly neutral position Measuring productivity Localising leadership pressure Dealing with non-technical leaders "Elite" teams Why coaching is important and much more… We are currently hiring for a lot of new positions at Stellate. If you got interested in potentially working with us, please take a look at our hiring page.

Join this episode fo In the Nic of Time with special guest Prakash Sethuraman, CISO of CloudBees as they talk about the security challenges in DevOps, how to find the balance between velocity and security, and Continuous ATO.

Congrats, you found a new job! You may even want to stomp out of the office in a dramatic exit. However, that might tarnish your personal brand and the relationships you've built.  In this episode, we sit down with Karla Porter, Sr. Talent Acquisition Partner at CloudBees, where she answers common questions about how to quit a job the right way. Take a listen to find out how you can leave your job on a good note and maintain positive relationships with your (soon to be) previous coworkers. 

Product-led growth (PLG) has become one of the most effective ways to grow in SaaS and tech. More and more companies are relying on their products as the main driver to gain customers. But using your product to acquire customers doesn't mean you should neglect sales and marketing. In fact, these three growth models work best when you align them to create a seamless customer experience. In this episode of the Product Led Revenue podcast, our host Breezy Beaumont welcomes Moritz Plassnig, the Chief Growth Officer at Immuta and former Founder & CEO of Codeship, a company acquired by CloudBees in 2018. Breezy and Moritz get into what makes the product-led growth strategy so effective, how to decide which type of growth model is right for your company and how to align sales and marketing in your business. 

Antonio et Guillaume discutent de nouvelle crèmerie, des fêtes de fin d'années, des cadeaux du père Noël, et... de log4j, le feuilleton de fin d'année ! Enregistré le 20 décembre 2021 Téléchargement de l'épisode [LesCastCodeurs-Episode-269.mp3](https://traffic.libsyn.com/lescastcodeurs/LesCastCodeurs-Episode-269.mp3) ## News [Décès de Stéphane Maldini](https://twitter.com/glaforge/status/1470729181050937346) (14 Dec 2021) * Une triste nouvelle pour commencer l'épisode avec l'annonce du décès soudain de Stéphane Maldini * Un acteur de l'écosystème Grails à la fin des années 2000, gràce à de nombreux plugins * Mais plus connu pour avoir co-fondé le project Reactor, et popularisé le Reactive Programming au sein de la communauté Java * Egalement à l'origine de R2DBC pour rendre l'accès aux bases de données plus réactif * Après de nombreuses années chez Pivotal, il avait rejoint plus récemment Netflix, et c'est peut-être en partie grâce à lui que vous pouviez matter plein de séries ! [CloudBees clot un tour de table de 150 millions de dollars valorisant l'entreprise à 1 milliards de dollars](https://twitter.com/cloudbees/status/1468943708330643457?s=21) [Le feuilleton Log4J2](https://www.lunasec.io/docs/blog/log4j-zero-day/) (9 Dec 2021) * Grosse faille de sécurité liée à l'utilisation des versions

Antonio et Guillaume discutent de nouvelle crèmerie, des fêtes de fin d'années, des cadeaux du père Noël, et… de log4j, le feuilleton de fin d'année ! Enregistré le 20 décembre 2021 Téléchargement de l'épisode LesCastCodeurs-Episode–269.mp3 News Décès de Stéphane Maldini (14 Dec 2021) Une triste nouvelle pour commencer l'épisode avec l'annonce du décès soudain de Stéphane Maldini Un acteur de l'écosystème Grails à la fin des années 2000, gràce à de nombreux plugins Mais plus connu pour avoir co-fondé le project Reactor, et popularisé le Reactive Programming au sein de la communauté Java Egalement à l'origine de R2DBC pour rendre l'accès aux bases de données plus réactif Après de nombreuses années chez Pivotal, il avait rejoint plus récemment Netflix, et c'est peut-être en partie grâce à lui que vous pouviez matter plein de séries ! CloudBees clot un tour de table de 150 millions de dollars valorisant l'entreprise à 1 milliards de dollars Le feuilleton Log4J2 (9 Dec 2021) Grosse faille de sécurité liée à l'utilisation des versions

Almost two years into the pandemic, we've become used to hybrid working but it's often hit and miss in terms of how well it works. In this episode, Isabel talks to Sacha Labourey, co-founder and chief strategy officer of all-remote tech company CloudBees, about what keeps his staff engaged and happy. One tip for managers is that overcommunicating with your team is the key to making things better when you are often - or always - apart. Isabel also speaks to the FT's New York correspondent Joshua Chaffin about the return to the office in NYC. The insider view? Turns out it is lonely at the top for CEOs holed up in their corner offices while the employees stay at home. We would love to hear from you: email us at workingit@ft.com or Isabel directly at isabel.berwick@ft.com. Follow @isabelberwick on Twitter or Instagram.Mentioned in the podcast: Find out more about CloudBees and its ‘distributed work' https://www.cloudbees.com/careersJoshua's story on lonely CEOs in New York https://www.ft.com/content/4743268e-e903-4822-acba-c22495367bbfJoshua's article on why commuters won't be lured back to offices https://www.ft.com/content/d17d6e2b-c29b-4505-81f4-b3a416f55ca2And… What went wrong at all-remote company Basecamp https://www.cnbc.com/2021/05/05/banning-political-discussions-at-work-isnt-that-simple-experts-say.htmlPresented by Isabel Berwick. Editorial direction from Renée Kaplan. Assistant producer is Persis Love. Sound design is by Breen Turner, with original music from Metaphor Music. Produced by Novel. See acast.com/privacy for privacy and opt-out information.

In this episode, Gerhard is joined by Cyrille Le Clerc, Product Manager Lead on Observability at Elastic, and Oleg Nenashev, Principal Engineer at CloudBees. It all started with Oleg's tweet back in July, in which he was promoting Akihiro Kiuchi's work on Jenkins monitoring with OpenTelemetry. This was done in the context of Google's Summer of Code - a link to Akihiro's demo is in the show notes. As you may remember from episode 20, instrumenting our changelog.com pipeline is on Gerhard's mind, and this conversation helped him clarify a few things. If you are thinking of instrumenting your CI/CD pipeline with OpenTelemetry, this episode is for you.

In this episode, Gerhard is joined by Cyrille Le Clerc, Product Manager Lead on Observability at Elastic, and Oleg Nenashev, Principal Engineer at CloudBees. It all started with Oleg's tweet back in July, in which he was promoting Akihiro Kiuchi's work on Jenkins monitoring with OpenTelemetry. This was done in the context of Google's Summer of Code - a link to Akihiro's demo is in the show notes. As you may remember from episode 20, instrumenting our changelog.com pipeline is on Gerhard's mind, and this conversation helped him clarify a few things. If you are thinking of instrumenting your CI/CD pipeline with OpenTelemetry, this episode is for you.

In this Venture Talks # 4 "Open Source Software: Why Now?", I had the immense privilege of receiving this ✨ amazing panel with Megan Reynolds, VC at Crane Venture Partners, Sacha Labourey, Co-Founder, ex-CEO & now CSO at CloudBees, Emile Vauge, Co-Founder & CEO at Traefik Labs and John Lafleur, Co-Founder at Airbyte. - - - [PROMO CODE] This episode is an excerpt from the episode that you can find in full with the full shownotes for our premium members on VentureNotes.co. Being a premium member of “Venture Notes” means 1) full episodes + detailed shownotes, 2) invitations to live podcasts and events, 3) a private chat reserved for the premium members community, 4) a monthly online get-together reserved for premium members, 5) perks and 6) possibly an investment syndicate! To thank you for listening to this episode, we offer you 20% OFF on the 12 month premium plan (€ 72 instead of € 90) valid until October 31, 2021 - - - The 3 entrepreneurs have collectively raised over US$100M in venture capital funding and Megan only does investments in enterprise and OSS companies, so the discussion was enlightening. We discussed from founders and investors perspectives about OSS in particular costs, freedom & flexibility vs. centralized governance, how open source helps attract talent and its community aspect, why open source could become the model for innovation, the risks, how to choose an open source project to integrate into one company's development... .. and a few more topics! I really thank Megan, Sacha, Emile and John and I am sure you will love this episode. Enjoy the episode! - - - The "Runway Series Originals", "AMA VC", "Human Factor", "No-Code VC / Fit" & "Venture Talks" podcasts are produced by UPCOMINGVC® (www.upcoming.vc), created and hosted by Raphael Grieco.

Prakash Sethuraman joins the show this week to highlight his career, leadership and the path to securing the cloud. Prakash gives some significant insights into how the cloud evolves security and so much more.   https://www.linkedin.com/in/prakashsethuraman/     CISO Talk is supported by these great partners please make sure to check them out: KnowBe4: https://info.knowbe4.com/phishing-security-test-cyberhub  Attivo Networks: www.attivonetworks.com **** Find James Azar Host of CyberHub Podcast, CISO Talk, Goodbye Privacy, Tech Town Square, and Other Side of Cyber James on Linkedin: https://www.linkedin.com/in/james-j-azar/ James on Parler: @realjamesazar Telegram: CyberHub Podcast Locals: https://cyberhubpodcast.locals.com ****** Sign up for our newsletter with the best of CyberHub Podcast delivered to your inbox once a month: http://bit.ly/cyberhubengage-newsletter   ****** Website: https://www.cyberhubpodcast.com Youtube: https://www.youtube.com/channel/UCPoU8iZfKFIsJ1gk0UrvGFw Facebook: https://www.facebook.com/CyberHubpodcast/ Linkedin: https://www.linkedin.com/company/cyberhubpodcast/ Twitter: https://twitter.com/cyberhubpodcast Instagram: https://www.instagram.com/cyberhubpodcast Listen Here: https://linktr.ee/CISOtalk   The Hub of the Infosec Community. Our mission is to provide substantive and quality content that's more than headlines or sales pitches. We want to be a valuable source to assist those cybersecurity practitioners in their mission to keep their organizations secure.

As continuous integration and delivery provider CloudBees prepares for its annual DevOps World conferences, the company also is gearing up for a new phase of growth with a greater focus on security, AI and making DevOps easier.DevOps World will run September 28-30. Last year, the event drew around 30,000 virtual attendees. This year the event is again virtual and is also free. With a tagline of “building the future of software delivery together,” the focus of DevOps World will be to reach out to the entire DevOps ecosystem to share knowledge on the tools, techniques and best practices currently in use and those anticipated for the future.In this latest episode of The New Stack Makers podcast we interview Sacha Labourey, co-founder and chief strategy officer of CloudBees, about both DevOps World and the future of the company. TNS Publisher Alex Williams hosted this episode, with the help of TNS News Editor Darryl K. Taft.

When it comes to at-scale software development, is continuous delivery and release automation (CDRA) the next step in the evolution of continuous integration/continuous delivery (CI/CD)?Forrester Research thinks so. The analysis firm describes CDRA as a way for organizations to deliver better-quality software faster and more securely, by automating digital pipelines and improving end-to-end management and visibility.In this edition of The New Stack Makers podcast,  Anders Wallgren, CloudBees vice president of technology strategy, discusses CDRA, supporting tools and the goals and challenges DevOps teams have when delivering software today. CI/CD systems provider CloudBees was named a leading CDRA vendor in the report "The Forrester Wave: Continuous Delivery And Release Automation, Q2 2020."The episode was hosted by Alex Williams, founder and publisher of The New Stack, and co-hosted by Joab Jackson, TNS managing editor.

For tech leaders heavily involved in the software development and deployment processes, ranging from embedded software to more user-facing applications, you'll love this. Anders Wallgren, the Vice President of Technology Strategy at CloudBees joined us to share a few things. Nope! Correction. Shared LOADS of things about the benefit and importance of having a smooth end-to-end development process. Being a software developer in the past (I'm a geek that managed to de-geek), I know the pains and benefits of getting this right. The investment in automation and auditing-as-you-go saves many headaches and Kerr-chings (money) over and over again. The system that Anders and CloudBees have created is just awesome. Especially for high compliance industries. Key takeaways from the podcast are: • How automation can become your implicit auditing • How tech leaders can enable companies to balance governance and developer freedom with a win/win scenario • The benefits of taking two steps back to make huge leaps forward in the efficiency of your value delivery Our Guest: Anders Wallgren LinkedIn: https://www.linkedin.com/in/anderswallgren/ Website: https://www.cloudbees.com/ Twitter: https://twitter.com/anders_wallgren Intro and background music: Craig MacArthur - Power Shutoff (https://www.youtube.com/watch?v=x74iB_jtauw)

The definitions of progressive delivery can vary, while many, if not most, would agree it represents an evolution of CI/CD. In this The New Stack Makers podcast The New Stack's Alex Williams, publisher and founder, and B. Cameron Gain, correspondent, of The New Stack, cover why progressive delivery will play a large role in the future of DevOps. Nick Rendall, senior product marketing manager, CloudBees, is the featured guest.While progressive delivery is universally accepted as important for DevOps and software development, delivery and post-deployment management, how best to implement it remains a challenge for many organizations. “Everyone understands that progressive delivery is a good thing, and now it's like, ‘okay, great, but how do we really do it and let's take this concept and let's really build it out into our big enterprise organizations,” said Rendall.

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Anders Wallgren of CloudBees about the human side of software development, ways to improve collaboration and why the future is in features. Read a transcript of this interview: https://bit.ly/2TjZRgn Subscribe to our newsletters: - The InfoQ weekly newsletter: bit.ly/24x3IVq - The Software Architects' Newsletter [monthly]: www.infoq.com/software-architects-newsletter/ Upcoming Virtual Events - events.infoq.com/ InfoQ Live: live.infoq.com/ - June 22, 2021 - July 20, 2021 - August 17, 2021 Follow InfoQ: - Twitter: twitter.com/InfoQ - LinkedIn: www.linkedin.com/company/infoq - Facebook: bit.ly/2jmlyG8 - Instagram: @infoqdotcom - Youtube: www.youtube.com/infoq

An airhacks.fm conversation with Kohsuke Kawaguchi (@kohsukekawa) about: running Family BASIC on Nintendo, learning C++, building abstractions, growing up in Tokyo, a Japanese keyboard, selling shareware programs in high school, writing a Text file viewer, earning 5k per month as a kid, PCs stores in Tokyo, learning chinese, Japanese vs. Chinese characters, building software at university, building an XML editor for XSL, reverse transformation from XHTML to XML, XML schema was lacking mathematical elegance, starting at Sun Microsystems in California, Sun didn't liked SOAP, starting at J2EE / Java EE team, working with James Clark on RelaxNG at Sun Microsystems, implementing Java Architecture for XML Binding / JAXB, Java Project Adelard, Java and XML the evil book at JavaOne, YAML vs. XML, using JAXB for generating JSON, working long hours in Tokyo, working times at Sun Microsystems were almost vacations, being a build breaker, getting the idea for Hudson, Hudson started as a leisure project, Hudson - an executable WAR, Hudson was based on the winstone servlet engine, winstone is embeddable, Hudson installation and administration was easy, software was like another person in the team, Hudson was like a British buttler, writing args4j, writing hk2, exploring native Java integration capabilities, working partially at Glassfish team, being part of Oracle, the forgotten developer at Oracle, forking Hudson to Jenkins, large corporations are not always rational, leaving Oracle and joining CloudBees, becoming a CEO of launchable, starting launchable, the confidence in code changes, using ML to sort tests, GraalVM can run Python, Ruby is popular in Japan, Kohsuke Kawaguchi on twitter: @kohsukekawa, Kohsuke on Wikipedia, and Kohsuke's website

“By and large, the way people put together the delivery process is by gut and instinct. The next step up from there is to use the data that comes out of your system to help you make the right decisions. When I say data-driven DevOps, don't rely on this human experience, and let the system tell you. We should be able to find that kind of information from data." Kohsuke Kawaguchi is widely known as the creator of Jenkins and currently is the co-CEO & co-founder of Launchable. In this episode, Kohsuke shared about data-driven DevOps, developers productivity, the future of software testing, and why he created Launchable to help us move closer to achieve those. And in the beginning of the episode, Kohsuke shared his story on how he created Hudson during his time at Sun Microsystems, which eventually led to become Jenkins, the most popular open-source CI/CD tool used by millions. Listen out for: Career Journey - [00:05:24] Hudson/Jenkins Story - [00:07:30] Current CI/CD Landscape - [00:12:18] Developer Productivity - [00:15:04] Improving Our Productivity - [00:17:06] Launchable - [00:21:06] Launchable Customer Story - [00:33:54] Future of Software Testing - [00:37:13] Data-Driven DevOps - [00:40:41] Running Launchable - [00:44:09] 3 Tech Lead Wisdom - [00:45:14] _____ Kohsuke Kawaguchi's Bio Kohsuke is the co-CEO & co-founder of Launchable. He is passionate about developer productivity. He created Jenkins, the most popular open-source CI/CD system used by millions. As CTO of CloudBees, he helped CloudBees go from

Antonio et Emmanuel discutent entre autre de JavaDoc, Quarkus, Crypto dans le CI, bootstrap 5, Grafana, cloud de confiance sans oublier les crowdcasts sur Cypress et sur hack.commit.push du 29 mai. Enregistré le 21 mai 2021 Téléchargement de l'épisode [LesCastCodeurs-Episode-256.mp3](https://traffic.libsyn.com/lescastcodeurs/LesCastCodeurs-Episode-256.mp3) ## News ### Langages [Un JEP pour améliorer la JavaDoc](https://openjdk.java.net/jeps/413) * On va pouvoir référencer par exemple des morceaux de code dans un autre fichier, dans un test, et l’intégrer dans la JavaDoc d’une méthode, d’une classe. Ca permettra d’avoir de la doc vraiment à jour au niveau des bouts de code, vu que ce sera toujours le vrai code qui tourne qui sera inséré dans la JavaDoc. * Il pourra y avoir également de la coloration syntaxique * de définir des régions qui doivent être surlignées pour être bien visibles * Il sera possible de modifier certaines parties d’un snippet de code, par exemple pour cacher une chaine de caractère de test dont on se moque de la valeur quand on explique ce bout de code * Possibilité de rajouter des liens hypertextes sur certains bouts de code, pour pointer par exemple vers la JavaDoc d’une méthode utilisée dans ce bout de code * Pourvu qu’ils reprennent le plus possible la syntaxe asciidoctor qui a déjà résolu ce problème [Asciidoclet](https://github.com/asciidoctor/asciidoclet) [Discussion sur le raisons du besoin derrière Loom](https://inside.java/2021/05/10/networking-io-with-virtual-threads/) * Article qui reste d.un premier niveau, il faut creuser,les bénéfices réels * IO et synchro bloque un thread. Limite scalabilité. Le code asynchrone est plus dur à comprendre. * Virtual threads don’t bien pour des taches qui passent beaucoup de temps à attendre * Les API IO blocantes parkent le virtual thread quand elles sont en attente * Un poller (boucle d’evenement) regarde les IO et leur état et unpark les virtualthread correspondant * Mechanisme similaire aux frameworks non blocs to de type vert.x mais avec une API bloxante ### Librairies [Quarkus 2.0 alpha 1, 2 et 3 sont sortis](https://quarkus.io/blog/quarkus-2-0-0-alpha1-released/) * Quarkus 2 parce que vert.x 4 et MicroProfile 4, pas de “gros” breaking changes mais quelques uns surtout pour les extensions * Continuous Testing: dans la console, on voit les tests qui plantent. Et quand on fait un code change, uniquement les tests qui sont impactés sont joués (flow analysis). * Lance aussi dans un container dédié les dépendances (e.g. une base de donnée pour les tests utilisant Hibernate). LE container pour les tests en continu est différent de celui pour le quarkus:dev qui tourner (pas de pollution). * JDK 11 minimum [Micronaut 2.5 est sorti ](https://docs.micronaut.io/latest/guide/#whatsNew) * support for @java 16 and @graalvm 21.1 on Micronaut Launch, * huge improvements to Micronaut Data from @DenisStepanov, * improved @OracleCloud integration * and many other small improvements ### Infrastructure [Les cryptomineurs tuent les CI gratuite](https://layerci.com/blog/crypto-miners-are-killing-free-ci/) * Les mineurs de crypto monnaies abusent des services de CI qui offre des capacités de build gratuites * Une des nouvelles astuces c’est d’utiliser les outils comme Pupetteer pour automatiser l’utilisation d’un navigateur web, pour miner de la crypto monnaie dans le navigateur qui tourne en headless sur la machine de CI * A la grande époque de OpenShift online et OpenShift.io, on a beaucoup appris sur le detection des Bitcoin miners :) * on a eu le soucis sur Codeship (la CI SaaS de CloudBees). Ils ont passé un max de temps à virer et proteger les builds. J’ai vu que GitHub avait eu aussi le soucis [Les 19 étapes facile pour écrire un dockerfile](https://jkutner.github.io/2021/04/26/write-good-dockerfile.html) * En vérifiant l’ordre de ses commandes, en limitant le scope de Copy, d’aligner les RUN d’installation de package, d’utiliser des images officielles, voire de se créer ses images de base, d’utiliser des tags spécifiques pour des images plus reproductibles, effacer le cache du package manager, de builder dans une image offrant un environnement cohérent, de récupérer ses dépendance dans une étape à part, de faire du multi-stage build... Ou d’utiliser les Cloud Native Buildpacks! (sur lesquels Joe bosse) * Article qui nous explique la complexité et les trade off impossibles. Et donc que buildpack c’est indispensable [Comparaison Apache Kafka et Apache Pulsar](https://blog.bigdataboutique.com/2021/03/apache-kafka-vs-apache-pulsar-video-fd3fi2) * pulsar a des brokers sans etat et deriere il y a des bookkeepers (qui stockent les data). * Cela permet plus de flexiblités pour augmenter ou descendre le nbombre de brokers. mais avec plus de “moving parts” et avec un hop de reseau supplémentaire. * Mais l’architecture est plus flexible notamment pour Kubernetes * Le stockage étagé et la geo replication est plus facile dans Pulsar (par default). Stockage etageé c’est de stocker l’info dans un S3 quand ellee st vielle par example. * Pulsar est multitenant par design. * Pulsar accepte des gros messages et sit les fragmenter au besoin * plus grosse communaute sur Kafka mais il y a des composants non open source (Confluent). ### Cloud [Red Hat OpenShift Streams for Apache Kafka : un service cloud de Kafkas managé](https://twitter.com/emmanuelbernard/status/1387687197621563396) * C’est ce sur quoi emmanuel a bossé ses 9 derniers mois * [Essayer le Managed Kafka de red hat](https://red.ht/TryKafka) * Red Hat OpenShift Streams for Apache Kafka: un cloud service de Kafka managés https://twitter.com/emmanuelbernard/status/1387686420903563264 * Super intégration avec Quarkus et utilise Quarkus a l’intérieur ### Web [Bootstrap 5 est sorti](https://blog.getbootstrap.com/2021/05/05/bootstrap-5/) * New offcanvas component * New accordion * New and updated forms * RTL is here * Overhauled utilities * New snippet examples * Improved customizing * Browser support * Dropped Microsoft Edge Legacy * Dropped Internet Explorer 10 and 11 * Dropped Firefox < 60 * Dropped Safari < 10 * Dropped iOS Safari < 10 * Dropped Chrome < 60 * Dropped Android < 6 * JavaScript * No more jQuery! * Le [Guide de migration est ici](https://getbootstrap.com/docs/5.0/migration/) Crowdcast sur [Cypress](https://www.cypress.io/) par Emmanuel Demey [La fin de Google AMP ou son intérêt devrait descendre ](https://www.lafoo.com/the-end-of-amp/) * AMP avait un avantage majeur. Celui d’être en premier sur les résultats du moteur de recherche. * Et les médias passaient en AMP rien que pour ça parce que le traffic du moteur de recherche dominant est essentiel * Mais AMP posait beaucoup de problèmes techniques et éthiques. Le contenu était hébergé et caché sur des pros idées edge et en pratique Google. * Donc les mesures d’audience étaient plus compliqeees * Et les ads avaient aussi des bias pavers la régie google. * Les prochains scoring de google search seront neutre ce qui risque faire baisser les pages amp * Les pages amp avaient du réinventer beaucoup de concepts du web ### Outillage [JFrog garde Bintray JCenter en lecture seule y compris le miroir de Maven central ](https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/) * Ca sent le truc planifie pour faire migrer et descendre le traffic et arriver en bon samaritain après. Cela dit ils étaient bon samaritains avec la version gratuite * Au moins les builds anciens ne vont pas casser [Docker desktop : sauter une mise à jour devient une option payante](https://www.docker.com/blog/changing-how-updates-work-with-docker-desktop-3-3/) * a partir de Docker 3.3 on peut éviter l’installation d’une nouvelle version avec la souscription pro ou team. Si j’ai bien compris. * Tu peux faire un rappel pour plus tard mais tu ne peux effectivement pas refuser définitivement une version donnée sans payer sinon ils te harcèlent (je ne connais pas la fréquence) pour upgrader. * En gros si tu ne paies pas tu dois être sur latest. Ils ne vont pas faire du support sur d’anciennes version pour les clients gratuits * Ce qui est logique. [Spock 2.0](https://spockframework.org/spock/docs/2.0/release_notes.html) * Spock est rebasé sur JUnit Platform * Support de l’exécution en parallèle des test specs et des test features * Support de Groovy 3 * Améliorations des tests avec des données tabulaires ### Sécurité [Bug de dénie de service dans snakeyml](https://snyk.io/blog/java-yaml-parser-with-snakeyaml/) * C’est du à la capacité de faire des références qui contiennent une référence à un élément plus haut. Paf récursion infinie. * à un moment, notre support YAML dans Groovy utilisait SnakeYaml il me semble, mais je viens de vérifier, on est passé à Jackson ### Loi, société et organisation [Grafana, Loki et Tempo passent de ASL 2 à AGPL](https://grafana.com/blog/2021/04/20/grafana-loki-tempo-relicensing-to-agplv3/) * La AGPL c’est la GPL mais pour lequel un services est comme une distribution * inspiré par MongoLab CoackroachDB etc * Cela reste open source au moins même si il y a des interprétations différentes du linkage et donc des risques * Est-ce que un service qui utilise grafana doit entièrement être AGPL? [Quand un troll de brevet attaque, cloudflare contre attaque](https://techcrunch.com/2021/04/26/cloudflare-rallies-the-troops-to-fight-off-another-so-called-patent-troll/?guccounter=1&guce_referrer=aHR0cHM6Ly9kdWNrZHVja2dvLmNvbS8&guce_referrer_sig=AQAAAEKNBJxidgIYvuXxPu-69VCJuD9nzkRUHMT62_2SS9vEox3eoMhFekoDHrH4ZSrjpsithr74uN62VF-i-6mt4MRqRREcR7NOFjiGy1T5VARNkaXcxG6F3zXxBqCyBUSxaoECUB1yCMc7XChZ6BKwEjdbUPIQtzmraWENdciwdYja) * cloud flare est attaqué par un troll de brevet et contre attaque pour la seconde fois en payant la recherche d’antériorité sur l’ensemble du porte feuille de brevets de cette entité. * Pour lui faire perdre une bonne partie de la valeur. « You do not negotiate with terrorists or children » [BaseCamp perd 30% de ses employés après son ban de conversations sociétales ](https://www.google.com/amp/s/marker.medium.com/amp/p/d487bed43155) * La liste des noms d’employés « funny » est ressorti avec des relents racistes * Les employés ont visiblement eu un débat dessus * DHH et Fry on fait un mémo bannissant les conversations politiques et sociétale parce que elle n’amenaient pas de bien pour la société (resentment etc) * Mais les employés le voient comme une façon de ne pas voir les sujets importants en face et les impactes des produits tech sur la société * Ils on offert un golden parachute à qui voulait partir * Et boom 30% ont dit oui [Stratégie nationale du cloud français](https://www.lemonde.fr/economie/article/2021/05/17/cloud-la-france-se-veut-plus-souveraine_6080442_3234.html) * cloud solution d'hébergement par défaut des services numériques d'état * protégé de règlementation extracommunautaire * contre le cloud act et autres lois * label "Cloud de confiance" c'est comme le porc salut * mise à jour du SecNumCloud de l'ANSSI * solution hybride société Française ou Européenne en utilisant les briques logicielles de groups américains * serveurs en France * opérés par des entreprises européennes * détenues par des européens * "les américains sont les plus avancés" * Google et Microsoft ont signé l'accord de licence * donc pas Amazon [Cloud de Confiance en qui ? par Laurent Doguin](https://ldoguin.name/fr/2021/05/quoi-cloud/) ## Outils de l'épisode [MuseGroup rachète audacity](https://www.minimachines.net/actu/muse-group-rachete-le-logiciel-audacity-99063) * Enfin la marque * Promet des designers sur l’interface et des contributeurs * Et de rester open source * On va voir ## Conférences [Devoxx france bougent au 29, 30 septembre et 1er octobre](https://twitter.com/DevoxxFR/status/1389489979978563584) Crowdcast d'Agathe sur [hack.commit.push](https://paris2021.hack-commit-pu.sh/) samedi 29 mai, inscrivez-vous ! ## Nous contacter Soutenez Les Cast Codeurs sur Patreon [Faire un crowdcast ou une crowdquestion](https://lescastcodeurs.com/crowdcasting/) Contactez-nous via twitter sur le groupe Google ou sur le site web

The conversation covers:  Tracy's thoughts on how the relationship between open-source and cloud-native should be described. The advantages and disadvantages to an organization using open-source. Some of the major risks associated with using open-source, and why companies should approach with caution.   Why CI/CD is a rising security concern for open-source organizations.Tracy also provides her thoughts on how businesses are handling the CI/CD pipeline today, and where the trend is heading. Some of the unresolved challenges related to continuous delivery that currently exist. Tracy's advice for companies that are just starting to develop an open-source contribution strategy. How companies should approach topics like open-source strategizing and building open-source communities. The common mistakes that individuals and companies make when nurturing open-source communities. Tracy also comments on mistakes that people are making with continuous delivery. Links CloudBees: https://www.cloudbees.com/ Continuous Delivery Foundation: https://cd.foundation/ Twitter: https://twitter.com/tracymiranda  Emily: Hi everyone. I'm Emily Omier, your host, and my day job is helping companies position themselves in the cloud-native ecosystem so that their product's value is obvious to end-users. I started this podcast because organizations embark on the cloud naive journey for business reasons, but in general, the industry doesn't talk about them. Instead, we talk a lot about technical reasons. I'm hoping that with this podcast, we focus more on the business goals and business motivations that lead organizations to adopt cloud-native and Kubernetes. I hope you'll join me.Emily: Welcome to The Business of Cloud Native. Today, I'm chatting with Tracy Miranda. Tracy, thank you so much for joining me.Tracy: Hi, Emily. Thanks for having me. It's my pleasure.Emily: So, as usual, I just want to start off with having you introduce yourself, both what you do, where you work, but also, like, some details, what does this actually mean? How do you actually spend your day?Tracy: Yeah, so I'm the director of open-source CloudBees, and I'm also the board chair at the Continuous Delivery Foundation, which is an open-source foundation, which is home to projects like Jenkins, and Spinnaker, and Tecton, and Jenkins X. So, basically, I'm a big fan of all things open-source, which in day-to-day means I'm doing anything which is related to building communities. So, either involved with code, or building communities and through conferences, or sometimes just the boring governance stuff around open-source.Emily: What is the boring governance stuff around open-source?Tracy: So, I guess it is just trying to get folks moving in the same direction, and reminding people that it's sometimes more than just code. And whether it's updating a code of conduct, and one of the things we've seen and—okay, I wouldn't call this boring; it's actually taken over a bit in open-source communities, but it's sort of different from the code, but it's the whole terminology updates. We've seen a lot of open-source communities have become more aware about wanting to be better about using terms like ‘master' and ‘slave' and move away from that. That being said, it's not that easy, so there's a lot to do in getting people on the same page and ready to move forward even before you can start changing a line of code.Emily: Since the topic of the podcast is cloud-native, obviously, open-source and cloud-native are related. In fact, some people think that cloud-native must be open-source. Where do you fall on that spectrum? How do you think the relationship between open-source and cloud-native should be described?Tracy: Yeah, I think that they're pretty distinct things. So, cloud-native is all about using the Cloud effectively and having technology which takes advantage of modern architectures to give you things like rapid elasticity, or on-demand self-service. And that's distinct from open-source, which is around the licensing, and it's become more about communities, as well. But I think because Kubernetes has been the most successful cloud-native project that is open-source, I guess there's become this very, very strong association which, in my mind, is a very, very good thing because I think open-source communities are really the way to drive innovation very, very quickly across the industry.Emily: And this may seem sort of obvious, but what are some of the advantages and disadvantages to an organization in using open-source?Tracy: Yes. So, I think—well, lots—virtually every company uses open-source, and the first thing people can see as the benefits are just the engineering efficiencies. So, using technologies which, say aren't core to the business, but then building on top of those and taking advantage of the features rather than dedicating their own engineering resources to developing them. I used to work as a consultant, and I would go from company to company, and usually, they would be adopting open-source when they wanted to get away from an in-house project where the people or person who had written it had left the company. So, I think there's a lot to be said, as well, for sustainability of technology: that communities and open-source communities are really good at sustaining projects over the long term, and therefore kind of the best bet for technology that's going to live on beyond individuals or even companies, acquisitions, or whatever.Emily: Do you think there are any risks to using open-source? I'm even interested in hearing if there are risks that are not real, but that are perceived risks. And then even maybe some risks that people don't think about, but that are in fact, quite real.Tracy: Yes, yeah, no, absolutely there are risks. So, it's wise for companies to approach with caution. I think the risks sort of depend on which side—like, are you looking to just use open-source that someone else has written, or are you contributing something, which might be key to your company, but then you're saying, “Okay, I'm going to do this in an open way,” which brings us to one of those common perceived myths, that someone, like a cloud provider, is then going to take your open-source software and do a better job of making money around it, so thereby just ruining your entire business model.And I think the other area where we tend to see a lot of dialogue around, is always around open-source security. For a long time, people used to, sort of, make out that this was different from closed source security, somehow. Security through obscurity meant that closed-source was better than open-source, which is clearly not the case. You can have secure open-source software, not secure open-source software. It just really depends on the project and the practices.Emily: And then also, I thought we'd talk a little bit specifically about this CI/CD work that you do. How important is CI/CD, do you think, in the pursuit of being cloud-native?Tracy: Yes, no, I think CI/CD has just risen to the top as one of the key concerns. And I think, part of the reason—when you're doing things in a cloud-native way it means that your systems are very distributed; you don't necessarily know where the services are running, it's typically not on-premise, and suddenly it becomes very important to understand how do you do this integration, and how do you then deliver that software in a way that is both quick, and that is not going to—you can do it in a safe way, so it's not going to break every time you do releases. And I think we're seeing that it really is at the forefront. Like last year, we started the Continuous Delivery Foundation, which is an open-source foundation, and the mission there is to increase the world's capacity to ship software securely and at speed. And the uptake from folks has been really well. Everyone's grappling and trying to figure out, what does CI/CD look like in the Cloud? What does it mean to be cloud-native CI/CD?Emily: And from the perspective of an end-user, what do you think are some of the, still, unresolved challenges related to continuous delivery?Tracy: Yeah, it's very challenging. Everything is changing under enterprise's feet. And it's not just the tools we're using, is also the skills we expect people to have, the way we organize a team. And traditionally, it's been very, very hard to decommission software or deprecate it, but what we're seeing in the industry now is that everything is changing really rapidly. You take something like Kubernetes and it has a new release, like, every three months and then nine months later, that's deprecated. So, people are having to make changes in enterprise situations at a rate that they just previously didn't come anywhere close to, and that's pretty challenging when you're having to deal with the changing tools, and processes, and people all at the same time, all while keeping your business up and running.Emily: In terms of the whole CI/CD pipeline, do you think most end-users experience that as being mature? Is it sort of figured out, or is it something that they continue to struggle with?Tracy: I think everybody has a CI… certainly CI… many people have sort of cracked, and they've got their systems set up. And then the delivery side, it just, kind of, varies. And I think it depends; we see a lot of folks who are really trying to figure out pipelines and are really trying to figure out what that looks like in a cloud-native world, and they haven't figured out, what does it mean for things to be highly available? What does it mean to be able to scale at any level? So, everybody's got something, but I think we've only just scratched the surface of what's possible with today's technology.Emily: Where do you think it's going in the future?Tracy: Yeah, I think, like in the same way we're having this big shift, everybody's got monoliths, and the problem with the monolith is that you can't do the speed and security at the same time. So, if you think about the key metrics people use today, there's two on speed, “Which is how quickly can you deploy?” And, “What's your lead time for changes?” And then for the safety, it's, “How long would it take you to restore services, if something went wrong?” And, “What is your change failure rate? How often are things going wrong every time you push code?” So, in the bid to get really good at those metrics, I think people have realized that monoliths cause a lot of problems, and it's much easier to meet these capabilities if you've got microservices are smaller batches of code, each, which do a specific thing, and there's less chance of things falling over when you make changes because there's not all these huge dependencies. Now, however, when you do start having all these different microservices with, let's say, a web of dependencies, things start to get really complicated. So, now you don't have, perhaps, one CI/CD pipeline, you have a pipeline per microservice. And then we start to say, “Okay, what is the definition of the application even? Is it all these microservices? Which version is it?” And then things like configuration management start to enter the picture, especially if you've got dependencies on things, let's say, outside your company, or open-source. So, I think it's a lot for people to grapple with, like, how to truly do microservices, and how the definition of an application is going to evolve. And I think for CI/CD, we can't keep doing what we've done in the sense of traditionally, folks have written a pipeline by hand, and you'd write a pipeline for your monolith. But now you've got all these different microservices. You want to start thinking about how can you have a pipeline auto-generated for them.Emily: I wanted to actually shift and talk more about open-source communities as well since I know that's a large part of what you do. My first question is, what would you say to a company that's starting to think not just about consuming open-source, but developing a strategy to contribute to open-source? What do you advise companies who are just starting that journey?Tracy: Yeah, no, I think for companies, it's a really good thing. I think open-source can give you a lot of strategic advantages, especially if you're coming in strong, and you're looking to be a leader in a space. And if we talk about category creation, you can use open-source almost as a weapon to drive the industry in a specific direction. So, I think what is important for companies is to be very deliberate about this strategy because open-source strategies can be almost counterintuitive, especially to folks who haven't done it before. This idea that you're giving away assets for free, or making them open. So, it's really important to have all the stakeholders in the company on the same page, and really understanding that this is a long-term thing where you'll have these benefits and not something where you start off and you do sort of half-heartedly.Emily: Are there two or three, sort of, primary open-source strategies?Tracy: Yeah, no, I think—[00:13:42 unintelligible] I think you can break it down. So, people would talk about the Red Hat model, which is really hard to reproduce but everything was open-source, and then they have this whole—they layered on top of that with a lot of services, and things. And then there's the open-core model where you're separating an open-source portion of the product, and then you add on a lot of features and things that add value that aren't being produced in the open-source. So, I think there's those, and then the new one that we're starting to see more of is—just looking much more at SaaS platforms. So, you have some open-source code, but your real—where you're making money is by offering it as a service.Emily: And how does that differ for a company whose core business isn't software? So, for example, if you're something like a Home Depot, and almost undoubtedly you use open-source software. If Home Depot wants to start contributing as well, as part of their company strategy, what should they know? What should a company like that think about as strategies?Tracy: Yeah, no, I think that's a great point because we do see a lot of companies contributing, and actually a lot of innovation is coming from companies who use software, but they have a different focus. And I think one good example, as well, is Capital One, who have a lot of open-source they contribute and maintain. And it's different, it's separate from, kind of, the main banking function. So, I think, again, for companies like that, it's just mapping out the strategy, being very deliberate in is there some sort of monetization around this, or is it more—you know, we see a lot of companies who want to do it to be seen as leaders in the field, and to, sort of, share some innovation to be seen as an attractive place, as well, for people to work with, and just to really drive that industry to help the innovation and to help make it a good place to be. So, I think the same things apply there, although maybe the business models allow, perhaps, for a bit more freedom. And we often find in those companies, they will have open-source program offices, which is a dedicated set of people who will map out the strategy and pull the whole company along in the same direction.Emily: Obviously, a big part of open-source is building a community. How do you do this? How do you herd the cats in a way that advances your project? And I'm actually curious, I don't know if you have a perspective on this from both somebody—an individual starting a project, and a company that wants to create a community around a particular project?Tracy: Yeah, no, I think that's a really great question. And people are always attracted to, I think, you want to start out with the big idea: why is your project going to do things better than before, or what's nicer about it? So, I think you have to start with, I guess you'd call it, like, you're [00:16:58 unintelligible] for your open-source project; the reason people are going to be attracted to it, and they're going to come and say, “Actually, I want to be part of this.” Because I think people do want to feel part of something bigger than themselves. They also want to see other people contributing, and everybody pulling their weight, and not necessarily any kind of biases for specific companies. So, the more open you can make it, the more transparent you can be about how things happen, people love to—if they're committing, and folks in open-source do commit fully—they want to know that they're not going to be taken advantage of, that they can do that, and they can really change the way the project is going to—they can feel the change they're going to make. So, I think it's important just to go to those principles of openness and transparency, and to let people participate. I think sometimes having clear ways—like with Jenkins, we saw that originally it really thrived because people could write their plugins, and they could make it their own, and they could share them and show them to their friends. And it's the same idea with GitHub, things that make developers look good as well, while they're contributing to open-source always makes for very, very successful projects.Emily: What do you think are common mistakes that people—individuals or companies make around nurturing the community?Tracy: Yeah, I think the mistakes are always connected to control and wanting to control too much or in a too specific way. And you could almost—I don't know if this is a good analogy, but it's almost like, I guess, parenting, in a way. You might be tempted to be very regimented and say, “Okay, your child can do this, or they can't do that.” But then you sort of lose out in finding out where could this go? How big could this grow? So, I think it's finding the right level of control so that the project can take on a life of its own and be used in ways that perhaps you couldn't even imagine. I think that's when the real magic happens. But it does take a leap of faith and understanding that you will be able to reap some business benefit out of this if that is your aim as well.Emily: Do you think that that's easier for individuals or for companies to achieve?Tracy: I think it depends on what people are going into it for. And for individuals, I think often it's they want to share their idea with the world or they want to build a reputation, which is very synonymous with doing the project. Having said that, individuals can have the same issues around wanting to control it, but I think there's perhaps a different monetization emphasis which would make it easier.Emily: Actually, I had a similar question related to continuous delivery which is, do you find that there are common mistakes that you see people making?Tracy: Yes. And some of the mistakes, I guess—one of the most common mistakes is a pretty boring one. And I know why it happens, but [laughs] it's just around documentation, to be honest. And it's the, “Okay, we're going to write the code, and then we're not going to necessarily document it or share the way people can either get involved or use a project.” And it's just—documentation is hard. Good documentation is really hard. Things keep changing, and it's boring to go keep updating them. But it's so incredibly important, and some of the most successful open-source projects have always provided that kind of self-service set of docs where people don't have to be asking the same questions over and over again. They really can go off and feel empowered to do things and to do things and not feel like they're getting it wrong or wasting their time, which I think is really important when building community. So, yeah, just write good docs, everybody.Emily: And do you think there's anything else specifically related to how companies approach continuous delivery, that there's something that a lot of them are not doing right?Tracy: With continuous delivery, especially today where everybody's in a really, kind of, tricky situation where they're trying to make this move to using cloud-native technologies because the benefits are so huge, but at the same time, all these technologies are coming very thick and fast, and nobody's sure—people have tried technologies which are now no longer used, so this is a bit of fear of saying, “Okay, is this going to be a safe bet? And at the same time, while I'm trying to decide if that's the right technology to use, I'm having to restructure my teams, and change of habits is really hard, and we've got all these additional environments we're having to deliver software for.” So, it's a huge challenge, and everything has to be done in balance: you have to get the tools, and you have to get the technology, and you have to get the people right. You can't do any one of those and hope it's going to work, you have to do this juggling act within your organization. And that's massively, massively challenging, especially when you are trying to change long-held behaviors and habits people have, and just ask them to do things in a different way.Emily: Do you think technology is more challenging, or people skills organization is more challenging?Tracy: Yeah, I think the thing with technology that is more challenging today is, especially in the CI/CD space, we have a lot of different types of tools. And we don't have standard ways to talk about—like, we don't have standardization of terms, so different things have different meanings to different people. So, you might say ‘a pipeline' but it might mean—the scope might change depending on who you're talking to. And so it's really hard for people to understand, how do I connect these different tools together? There's very poor interoperability, as well, which is another thing the Continuous Delivery Foundation wants to try and solve. So, I think those are key areas. Security is another one, which makes it really hard when you break things up. And no one's taking responsibility for the interaction between different platforms of different open-source technology written by different people, that becomes really tricky. So, I think we do need solutions at a community level, and we need communities working together closer to tackle this proliferation, and lack of interoperability, and new security concerns that we have to deal with as an industry.Emily: Is there anything else that I didn't think to ask that you'd like to add?Tracy: Yeah, no. I think what we're doing in the Continuous Delivery Foundation, if I can say a little bit about that, it is a relatively new open-source foundation. And I think it's a good place to bring people together where we're trying to tackle these issues. So, things like interoperability, we have an interoperability working group. And one of the first things that happened in that group as people would come together and talk about the different tools, is that we spontaneously realized we needed to define the tools. And there was a page set up where everybody could write down the definition of how their tool—use different terms. You know, is it a step? Or what do you call it in your tool? So, we have this what we call, like, the Rosetta Stone, of CI/CD tools. So, it compares across—whether it's all kinds of Git providers or pipeline orchestration tools, was the different terminology. And I think from there, we're going to look to see how we can standardize as an industry, just to make it simpler for people because I think—I would really hate to be someone new coming into the industry today and trying to figure out where to start, which tool to try out because the amount of noise and confusion is at all-time high levels.Emily: That's absolutely fair. And in fact, speaking of tools, my next question is, what tool do you really rely on? What engineering tool would you not be able to work without?Tracy: Yeah, well, they kind of say for developers, and I think this rings true for me as well, you're kind of in three places. You're in, like, GitHub and Slack, and then your development environment which use VS code, and like many people. So, those are, kind of, the three development environments. I think, when I look at CI/CD, and we look at new technology in the space that's, kind of, gaining quick adoption, there's two projects in CDF which are starting to really resonate. And one is Tekton, which came out of Google, and their Knative serverless platform. But that's looking to have these standardized building blocks for CI/CD pipelines. And then the other one is Jenkins X, which, incidentally, uses the building blocks of Tekton to stitch together a CI/CD experience, if you wish, that pulls in Kubernetes, and Helm, and all those other projects to give a really nice developer experience just generating pipelines for you, so you don't have to write things by hand, and giving you preview environments, and really just trying to take advantage of all the power that cloud-native affords you in delivering software.Emily: And then lastly, how can listeners connect with you or follow you?Tracy: Yeah, no, I think the best place is Twitter. So, find me Twitter at @tracymiranda, and in all the continuous delivery working groups, and the communities we're building there. So, find that on cd.foundation, and, yeah, come join the community. We're having some great conversations in the space.Emily: Well, thank you so much, Tracy, for joining us.Tracy: Yeah, thanks for having me. And yeah, really great conversation and questions.Emily: Thanks for listening. I hope you've learned just a little bit more about The Business of Cloud Native. If you'd like to connect with me or learn more about my positioning services, look me up on LinkedIn: I'm Emily Omier—that's O-M-I-E-R—or visit my website which is emilyomier.com. Thank you, and until next time.Announcer: This has been a HumblePod production. Stay humble.

In this episode, we are discussing GitOps with Viktor Farcic from CloudBees. We explored some fundamental questions: What is GitOps?Where did it come from? and What prevents companies from applying its principles?Support the show (https://cd.foundation/podcast/podcast-submission-form/)

Panelist include: Kara de la Marck, Jenkins X Community Manager at CloudbeesFatih Degirmenci, SIG Interoperability Chair at CDFDeepak Giridharagopal, CTO at PuppetOrganizations often employ more than one tool in various stages of their CI/CD pipelines due to different capabilities provided by the tools and this is perhaps one of the biggest benefits users get by using open technologies for their CI/CD needs. However, one of the challenges users face is the lack of interoperability across the CI/CD tools and technologies, resulting in various issues while constructing and running pipelines such as passing metadata and artifacts between the tools or achieving traceability from commit to deployment. Often users end up building their “own glue code” to address what is a common problem, further complicating moving from one tool to another and adopting new technologies and methodologies.These “glue code solutions” are generally specific to users' needs and tools rather than being loosely coupled and agnostic to tooling and technology. Additionally these solutions are not visible to other users and the communities, making them vulnerable to the risk of outage in their CI/CD pipelines due to potential changes (i.e. non-backward changes to the APIs, changes in data models) that happen to the tools in respective projects.Therefore, focusing on tool interoperability is critical. The Continuous Delivery Foundation highlighted interoperability as one of the Foundation's 9 goals. The Interoperability special interest group (SIG) was founded as the forum for driving towards this goal. Support the show (https://cd.foundation/podcast/podcast-submission-form/)

About Emily OmierEmily Omier is a content strategy consultant who helps companies leverage content to build thought leadership, increase website traffic, grow their mailing list and book more demos. She has worked with CloudBees, Portworx, Plutora, Armory, and is a regular contributor for The New Stack. She graduated from the Columbia University Graduate School of Journalism and lives in Portland, Oregon.