CloudBees Connect San Jose

DevOps movement has been around for over 15 years and the benefits of a unified process across multiple teams is clear yet, enterprises still find it difficult - if not impossible - to make software delivery rapid, repeatable and scalable. Now, DevOps implementation isn’t magic, and transforming into a well oiled software delivery machine doesn't happen overnight.  You’ve taken the first steps but know you can do better. This session will start with an overview of common challenges in modern software delivery and highlight solutions to overcoming these challenges with focus on CI/CD as the cornerstone of DevOps practices.

Jenkins helps enterprise companies continuously automate at scale.  However, as teams, projects, and market pressures increase, so do administrative tasks, governance and security risks, and demands for customization associated with the tool. Scaling Jenkins usage across a growing enterprise, without affecting the security or stability of its software development lifecycle (SDLC) is challenging, particularly for highly regulated industries.

So, how do you go big and go fast with Jenkins?  Learn from CloudBees experts about :

• Stability, Support & Efficiency: Easier and quicker updates, security advisories, 24/7 support

• Governance & Security: Centralized role-based access controls, templatized job definitions, segregation of duty between Dev & Ops

Management at scale: CasC and centralized management of a scalable, distributed architecture

You know that feeling you get when you start a new codebase? It’s a feeling of endless possibility and productivity. You have an idea, you write some code, and you see it come to life. Amazing.

 But then reality comes crashing down. The code becomes difficult to maintain. You have to painstakingly vet every change, spend interminable hours looking for bugs, and bang your head against brick walls. 

Zero-friction development is about achieving the smooth flow, enjoyment, and productivity you see in a brand-new codebase, no matter how old your code may be. James Shore explains how to make it happen.

The CloudBees CI workshop is composed of two distinct sets of labs. The first is focused on product capabilities that make it easy to manage continuous integration at scale and the second is focused on features that provide a developer centric experience for software delivery. Manage Continuous Integration at Scale
These labs will provide hands-on examples that will show you how CloudBees CI enables shared services teams and Jenkins admins to provide highly scalable and easily manageable continuous integration for all of your software delivery teams. You will learn how CloudBees CI provides comprehensive centralized team management with features to manage Jenkins configuration as code, create and share templates for Jenkins pipelines, enforce pipeline policies and simplify collaboration across disparate development teams.

In the wake of increasing attacks on software supply chains, storing credentials in CI/CD tools is considered insecure. This session will discuss and demonstrate best practices for secrets management in CloudBees CI, including:

• How pipeline and freestyle projects can be assigned unique, authenticated identities

• How credentials can be dynamically instantiated for builds from a centrally managed credential vault

• How project access to credentials can be easily granted and revoked