Git Switch Branch: Everything You Need to Know

921
CloudBees
CloudBees, the enterprise software delivery company, provides the industry’s leading DevOps technology platform. CloudBees enables developers to focus on what they do best: Build stuff that matters, while providing peace of mind to management with powerful risk mitigation, compliance and governance tools.

The following is a guest blog post written by Carlos Schults.

Repositories in Git work in a fundamentally different way from most other tools. One of the most glaring examples of said differences is branching. In most other VCS tools, branching is this elaborate ceremony. They make a huge deal out of it, and developers just give up, preferring workflows that don’t rely on many branches.

In Git, the opposite is often true: branching is so cheap that most people do it a lot. People often get confused when trying to manage their branches. This post attempts to clear up some of that confusion by offering a guide on how to successfully git switch branch in an easy and safe way. Before we get there, though, we start with some basics, explaining what branches actually are in Git, how they work and how you create them.

Before wrapping up, we share a bonus tip, covering how to check out remote branches. Let’s get started!

How Do Git Branches Work?

How do branches work in Git? The first thing you need to know is that a repository in Git is made up of objects and references. The main types of objects in a Git repository are commits. References point to other references or to objects. The main types of references are—you’ve guessed it—branches.

Objects in Git are immutable. You can’t change a commit in any way or move its position in history. There are commands that appear to change things, but they actually create new commits. References, on the other hand, change a lot. For instance, when you create a new commit, the current branch reference is updated to point to it.

When you create a new branch, all that happens is that a new reference is created pointing to a commit. That’s why it’s so cheap and fast to create branches in Git. Speaking of which…

How Do I Create a New Branch?

We already have a whole post explaining how you can create a branch in Git, covering the four main ways to do that.

Here, we’ll just cover the easiest way to create a branch in Git, which is simply using the branch command from the current branch. Let’s see an example:

mkdir git-switch-demo # creating a folder
cd git-switch-demo
git init # initializing a repository
touch file1.txt # creating the first file
git add . # adding the file to the stage
git commit -m "Create first file" # commiting the file
touch file2.txt
git add .
git commit -m "Create second file"
touch file3.txt
git add .
git commit -m "Create third file"

In the example above, we’ve created a new repository and added three commits to it, creating a new file per commit. Here’s a visual representation of the current state of our repository:

To create a new branch from the current point, we just have to run git branch <branch-name>. I’ll call the branch “example” since I’m not feeling particularly creative:

git branch example

We’ve created a branch but haven’t switched to it yet. This is how our repo looks like now:

What if we added a new commit while still in the master branch? Would that impact the example branch? The answer is no. Execute the following commands:

echo "Another file" > file4.txt
git add .
git commit -m "Create fourth file"

In the next section, we’ll show how you can git switch branch, and then you’ll be able to see for yourself how that new branch doesn’t contain the fourth commit. For now, take a look at the visual representation of the current state of our repo:

How Do You Switch Branches?

For most of Git’s history, the checkout command was used for that. While you can still use it, version 2.23 of Git added the switch command (as well as the restore command) in an attempt to have more specific commands for some of the many tasks the checkout command is used for.

How Do I Use Git Checkout?

The older, more well-know way of switching branches in Git is by using the checkout command. Following our example, if we wanted to change to the “example” branch, we’d just have to run:

git checkout example

After executing the command, you should see a message saying that you’ve successfully switched to the example branch:

Now you’re in the new branch, that means you can add how many commits you want, knowing that the master branch won’t be impacted. The checkout command, followed by a branch name, updates the working tree and the index, and it updates the HEAD reference, pointing it to the branch you’ve just checked out. What if you had uncommitted changes at the moment of switching? Those would be kept to allow you to commit them to the new branch.

Git allows you to use the checkout command in different ways. For instance, an incredibly common scenario is to create a branch and immediately switch to it. In fact, I’d argue that creating a branch and not changing to it on the spot is the exception rather than the rule. So, Git offers us a shortcut. Instead of creating a branch and then checking it out, you can do it in one single step using the checkout command with the -b parameter.

So, doing this:

git checkout -b new

is equivalent to this:

git branch new
git checkout new

Checkout doesn’t work only with branches, though. You can also checkout commits directly. Why would you want to do so?

Well, taking a look at how the project was some amount of time ago is often useful, particularly for testing purposes. But there’s more. Checking out a commit puts your repository in a state called “detached HEAD” which allows you to create experimental changes, adding commits that you can then choose to keep or throw away.

What Is Git Switch?

For the most part of Git’s lifetime, the checkout command was the only one you’d use for switching branches. The problem is that this command also does other things, which can lead to confusion, especially among new users.

The 2.23.0 version of Git solves this by adding two new commands: switch and restore. The restore command isn’t relevant for us today. The switch command, on the other hand, is a new way to switch to branches.

The manual page for the command lists all of its many options. On its most basic form, you use it the same way as git checkout, only swapping the command’s name:

git switch example

If you want to go back to the previous branch, you can use a shortcut instead of its full name:

git switch -

What if you want to create a new branch and immediately switch to it? With checkout, we could use this shortcut:

git checkout -b <branch-name>

The new command also offers a shortcut, but in this case, we use the letter “C”:

git checkout -c <branch-name>

Is using the new command worth it? Well, I’ll probably keep using git checkout, as long as they don’t change it, mainly because of muscle memory. But when teaching Git to beginners? Then I’ll definitely use the switch command. It has a name that’s more closely related to the task it does and, therefore, it’s more memorable.

How Do I Switch to a Remote Branch?

Before wrapping up, we share a final tip: how to switch to remote branches?

For this example, we’re going to use an open-source project called Noda Time, which is an alternative date and time API for .NET. Start by cloning the repository:

git clone https://github.com/nodatime/nodatime.git

If everything worked fine, you should have a “nodatime” folder now. Enter the folder and run the following command:

git branch -a

The branch command lists the branches in your repository. The “-a” option means you want to see all branches, not only local ones. The result should look like this:

As you can see, we have only one local branch, which is the master branch. You can see, in red, all of the remote branches. So, let’s say you want to check out the branch called “slow-test.” How would you go about that?

Well, technically speaking, Git doesn’t allow you to work on other people’s branches. And that’s what remote branches are. What you actually do is to create a local “copy” of someone else’s branch to work on. So, let’s see how to do it.

When you create a branch, you can pass a commit or branch name as a parameter. So, in order to create a local branch from the remote “slow-test” branch, I’d just have to do:

git branch slow-test origin/slow-test

In the example, I’m using “slow-test” as the name for my local branch, but I could’ve really used any other valid name.

Alternatively, I could’ve used the checkout command with the -b option or the switch command with the -c option. So, the two following lines are equivalent to the line above:

git checkout -b slow-test origin/slow-test
git switch -c slow-test origin/slow-test

Finally, there’s an even easier way. I could’ve just used git checkout slow-test, and the result would have been the same. That works because when you try to check out a branch and Git doesn’t find a branch with that name, it tries to match it with a remote branch from one of your remotes. If it can successfully match it, things just work.

Git Branches: Use in Moderation

In this post, we’ve shown you how to switch branches in Git. But we went further than that: we’ve explained what branches are and how they work. Hopefully, by now, you’re more comfortable creating and using branches in Git.

Before we go, a final caveat: just because you can do something, it doesn’t mean you should. Sometimes people get so carried away with the ease of branching in Git they end up using workflows that rely on a number of long-lived branches, which makes their development process way too complex and error-prone and delays integration.

Thanks for reading, and until next time.

Carlos Schults is a .NET software developer with experience in both desktop and web development, and he’s now trying his hand at mobile. He has a passion for writing clean and concise code, and he’s interested in practices that help you improve app health, such as code review, automated testing, and continuous build.

CloudBees
CloudBees, the enterprise software delivery company, provides the industry’s leading DevOps technology platform. CloudBees enables developers to focus on what they do best: Build stuff that matters, while providing peace of mind to management with powerful risk mitigation, compliance and governance tools.
Tools mentioned in article
Open jobs at CloudBees
Principal Site Reliability Engineer-C...
EMEA

OUR CUSTOMERS DEVELOP SOFTWARE AT THE SPEED OF IDEAS

CloudBees, the enterprise software delivery company, provides the industry’s leading DevOps technology platform. CloudBees enables developers to focus on what they do best: Build stuff that matters while providing peace of mind to management with powerful risk mitigation, compliance, and governance tools. Used by many of the Fortune 100, CloudBees is helping thousands of companies harness the power of continuous everything and gets them on the fastest path from a great idea, to great software, to amazing customer experiences, to being a business that changes lives.

Backed by Matrix Partners, Lightspeed Venture Partners, Verizon Ventures, Delta-v Capital, Golub Capital, and Unusual Ventures, CloudBees was founded in 2010 by former JBoss CTO Sacha Labourey and an elite team of continuous integration, continuous delivery, and DevOps professionals.

The CloudBees Community team is seeking a Principal Site Reliability Engineer. In this role, you will support the Community team and the Jenkins community by maintaining, updating, refining, and improving the Jenkins project infrastructure.  The Jenkins infrastructure team powers the Jenkins project.  We provide services to more than 40000 users every day and 300000 Jenkins instances worldwide. This project is special in the way that almost everything is public, sponsored, and orchestrated by the Jenkins community.

You will manage multiple Kubernetes clusters and the applications running on those clusters.  You will interact with an international community of open source contributors both inside and outside of CloudBees.  Your work will be widely visible and deeply appreciated by users around the world.

WHAT YOU'LL DO

  • Key contributor to Jenkins infrastructure
  • Lead, design, implement, and support Jenkins infrastructure initiatives
  • Meet budget objectives and improve service reliability
  • Produce necessary documentation, reports, and presentations
  • Communicate effectively with others inside and outside CloudBees

WHAT THE ROLE REQUIRES

  • Kubernetes production experience
  • Cloud experience with at least one major public provider (AWS, Azure, Google Cloud)
  • Linux system administration experience
  • Jenkins administration experience
  • Automation experience with languages like Bash, Groovy, Python, or Go
  • Excellent organization and planning skills
  • Good English language communications skills, both written and verbal
  • Good attention to detail; ability to monitor, manage, and track impending deadlines, and present data accurately to support decision making
  • Willing to mentor others

DESIRED SKILLS

  • Windows experience
  • Java ecosystems experience
  • Infrastructure as code experience with tools like Puppet, Terraform, Packer, etc.
  • Willing to advocate for Jenkins, possibly including travel to conferences and participation in contributor events
  • Blogging or other advocacy experience

WHAT YOU’LL GET

  • Highly competitive benefits and vacation package
  • Ability to work for one of the fastest growing companies with some of the most talented people in the industry
  • Team outings
  • Fun, Hardworking, and Casual Environment
  • Endless Growth Opportunities

We have a culture of movers and shakers and are leading the way for everyone else with a vision to transform the industry. We are authentic in who we are. We believe in our abilities and strengths to change the world for the better. Being inclusive and working together is at the heart of everything we do. We are naturally curious. We ask the right questions, challenge what can be done differently and come up with intelligent solutions to the problems we find. If that’s you, get ready to bee impactful and join the hive.

At CloudBees, we truly believe that the more diverse we are, the better we serve our customers. A global community like Jenkins demands a global focus from CloudBees. Organizations with greater diversity—gender, racial, ethnic, and global—are stronger partners to their customers. Whether by creating more innovative products, or better understanding our worldwide customers, or establishing a stronger cross-section of cultural leadership skills, diversity strengthens all aspects of the CloudBees organization.

In the technology industry, diversity creates a competitive advantage. CloudBees customers demand technologies from us that solve their software development, and therefore their business problems, so that they can better serve their own customers. CloudBees attributes much of its success to its worldwide workforce and commitment to global diversity, which opens our proprietary software to innovative ideas from anywhere. Along the way, we have witnessed firsthand how employees, partners, and customers with diverse perspectives and experiences contribute to creative problem solving and better solutions for our customers and their business.

Development Support Engineer
US or Canada

Our Customers Develop Software at the Speed of Ideas

CloudBees, the enterprise software delivery company, provides the industry’s leading DevOps technology platform. CloudBees enables developers to focus on what they do best: Build stuff that matters while providing peace of mind to management with powerful risk mitigation, compliance, and governance tools. Used by many of the Fortune 100, CloudBees is helping thousands of companies harness the power of continuous everything and gets them on the fastest path from a great idea, to great software, to amazing customer experiences, to being a business that changes lives.

Backed by Matrix Partners, Lightspeed Venture Partners, Verizon Ventures, Delta-v Capital, Golub Capital, and Unusual Ventures, CloudBees was founded in 2010 by former JBoss CTO Sacha Labourey and an elite team of continuous integration, continuous delivery, and DevOps professionals.

Team description

CloudBees customers rely on our Support team to help them be successful in the use of our products. Our team is uniquely positioned to help sustain the company’s growth by providing a customer support experience that surpasses expectations. These positive customer experiences help drive annual renewals and business expansion. A successful Development Support Engineer (DSE) will use their skills and experience to accurately diagnose customer issues and get them resolved in a timely way, to the customer’s satisfaction. In addition, motivated individuals who want to contribute in other ways will have opportunities to work on our collection of internal tools that automate the diagnosis of issues, making the entire team more efficient by reducing manual work.

A typical day in our Support team starts with a scrum meeting where we review open and unassigned cases and help each other with issues we’re stuck on. Working on active cases, we answer basic questions and also troubleshoot problems that range from the mundane to the fiendishly complicated (it helps if you enjoy a good challenge). We collaborate with each other throughout the day, via Slack or video calls. During down time, we build technical knowledge through training and tools development.

CloudBees has been a remote-work-first company since it was founded, and the majority of the DSE team works remotely. The existing team has a mix of backgrounds including system administrators, developers, support engineers, and devops engineers. We strive to provide everyone on the team with interesting challenges, opportunities for personal and professional growth, and a positive work/life balance.

What You'll Do 

  • Answer customer questions about product usage and best practices
  • Diagnose complex technical issues and provide solutions or workarounds
  • Communicate with customers through a ticketing system, with phone support sometimes required for complex or urgent issues
  • Collaborate frequently with members of the Support and Engineering teams
  • Contribute to documentation
  • Contribute to internal software tools to automate diagnosis of customer issues
  • Work a weekend on-call rotation every 4-8 weeks (daytime hours only)

What The Role Requires 

A successful candidate will have:

  • Basic Linux system administration knowledge
  • Good communication skills (English language fluency required)
  • The ability to work independently
  • The ability to build knowledge of new technologies easily
  • A sense of empathy with our customers

As previously mentioned, members of our team have a variety of past work experience, and each bring a different mix of skills to our team. The following are some examples of these skills, but by no means do we expect candidates to have all of them. If any of these fit with your experience, we would love to hear from you!

  • System administration knowledge, especially Linux, storage, and/or networking
  • Good working knowledge of popular DevOps tools and services such as: Jenkins, Docker, Artifactory/Nexus, Kubernetes, git & GitHub
  • Knowledge of common enterprise environments & technologies such as LDAP & databases
  • Knowledge of common web application architectures, SSL, REST API concepts, etc.
  • Understanding of Continuous Integration and Continuous Deployment concepts and practices
  • Experience with cloud computing environments
  • Programming experience, anything from shell scripting to Java development
  • Open source community contributions, especially Jenkins
  • Previous experience in customer-facing roles
  • Computer Science / IT degree or equivalent work experience
  • Certifications: Cloud computing providers, Kubernetes, etc.

What You'll Get 

  • Gain experience working with and troubleshooting a variety of tools used widely in the tech industry
  • Enhance your career by completing industry-recognized technical certifications
  • Manage projects and initiatives within the team, contributing to team goals
  • Potential future opportunities to grow into management, engineering, or other field roles
  • Play a key role in maintaining and growing company revenue over time

We have a culture of movers and shakers and are leading the way for everyone else with a vision to transform the industry. We are authentic in who we are. We believe in our abilities and strengths to change the world for the better. Being inclusive and working together is at the heart of everything we do. We are naturally curious. We ask the right questions, challenge what can be done differently and come up with intelligent solutions to the problems we find. If that’s you, get ready to bee impactful and join the hive.

At CloudBees, we truly believe that the more diverse we are, the better we serve our customers. A global community like Jenkins demands a global focus from CloudBees. Organizations with greater diversity—gender, racial, ethnic, and global—are stronger partners to their customers. Whether by creating more innovative products, or better understanding our worldwide customers, or establishing a stronger cross-section of cultural leadership skills, diversity strengthens all aspects of the CloudBees organization.

In the technology industry, diversity creates a competitive advantage. CloudBees customers demand technologies from us that solve their software development, and therefore their business problems, so that they can better serve their own customers. CloudBees attributes much of its success to its worldwide work force and commitment to global diversity, which opens our proprietary software to innovative ideas from anywhere. Along the way, we have witnessed firsthand how employees, partners, and customers with diverse perspectives and experiences contribute to creative problem solving and better solutions for our customers and their businesses.

Development Support Engineer
, Spain

Our Customers Develop Software at the Speed of Ideas

CloudBees is powering the continuous economy by offering the world’s first end-to-end continuous software delivery management system (SDM). For millions of developers and product teams driving innovation for businesses large or small, SDM builds on continuous integration (CI) and continuous delivery (CD) to enable all functions and teams within and around the software delivery organization to best work together to amplify value creation.
 
CloudBees is the continuous integration (CI), continuous delivery (CD) and application release automation (ARA) powerhouse built from the commercial success of its products and its open source leadership as the largest contributor to Jenkins and a founding member of the Continuous Delivery Foundation (CDF). With a globally distributed workforce of more than 500 employees, the company reflects the global nature of the DevOps movement. We believe in walking the talk! From startups with full-stack developers practicing NoOps to large Fortune 100 companies, CloudBees enables all software-driven organizations to intelligently deploy the right capabilities at the right time.
  
Over 3,500 of the world’s best known brands and over 50% of the Fortune 500, invest in CloudBees because of its ability to work across any cloud, in any development environment and to balance corporate governance and control with developer flexibility and freedom.
 
CloudBees is home to the world’s leading DevOps experts helping thousands of companies harness the power of “continuous everything” and putting them on the fastest path from great idea, to great software, to great business value.

 

CloudBees customers rely on our Support team to help them be successful in the use of our products. Our team is uniquely positioned to help sustain the company’s growth by providing a customer support experience that surpasses expectations. These positive customer experiences help drive annual renewals and business expansion. A successful Development Support Engineer (DSE) will use their skills and experience to accurately diagnose customer issues and get them resolved in a timely way, to the customer’s satisfaction. In addition, motivated individuals who want to contribute in other ways will have opportunities to work on our collection of internal tools that automate the diagnosis of issues, making the entire team more efficient by reducing manual work.

A typical day in our Support team starts with a scrum meeting where we review open and unassigned cases and help each other with issues we’re stuck on. Working on active cases, we answer basic questions and also troubleshoot problems that range from the mundane to the fiendishly complicated (it helps if you enjoy a good challenge). We collaborate with each other throughout the day, via Slack or video calls. During down time, we build technical knowledge through training and tools development.

CloudBees has been a remote-work-first company since it was founded, and the majority of the DSE team works remotely. The existing team has a mix of backgrounds including system administrators, developers, support engineers, and devops engineers. We strive to provide everyone on the team with interesting challenges, opportunities for personal and professional growth, and a positive work/life balance.

WHAT YOU'LL DO

  • Answer customer questions about product usage and best practices
  • Diagnose complex technical issues and provide solutions or workarounds
  • Communicate with customers through a ticketing system, with phone support sometimes required for complex or urgent issues
  • Collaborate frequently with members of the Support and Engineering teams
  • Contribute to documentation
  • Contribute to internal software tools to automate diagnosis of customer issues
  • Work a weekend on-call rotation every 4-8 weeks (daytime hours only)
  • In this role, you will be responsible for working our North America shift hours (2:00pm - 11:00pm CET)

WHO YOU ARE

A successful candidate will have:

  • Basic Linux system administration knowledge
  • Good communication skills (English language fluency required)
  • The ability to work independently
  • The ability to build knowledge of new technologies easily
  • A sense of empathy with our customers

As previously mentioned, members of our team have a variety of past work experience, and each bring a different mix of skills to our team. The following are some examples of these skills, but by no means do we expect candidates to have all of them. If any of these fit with your experience, we would love to hear from you!

  • System administration knowledge, especially Linux, storage, and/or networking
  • Good working knowledge of popular DevOps tools and services such as: Jenkins, Docker, Artifactory/Nexus, Kubernetes, git & GitHub
  • Knowledge of common enterprise environments & technologies such as LDAP & databases
  • Knowledge of common web application architectures, SSL, REST API concepts, etc.
  • Understanding of Continuous Integration and Continuous Deployment concepts and practices
  • Experience with cloud computing environments
  • Programming experience, anything from shell scripting to Java development
  • Open source community contributions, especially Jenkins
  • Previous experience in customer-facing roles
  • Computer Science / IT degree or equivalent work experience
  • Certifications: Cloud computing providers, Kubernetes, etc.

HOW YOU WILL GROW

  • Gain experience working with and troubleshooting a variety of tools used widely in the tech industry
  • Enhance your career by completing industry-recognized technical certifications
  • Manage projects and initiatives within the team, contributing to team goals
  • Potential future opportunities to grow into management, engineering, or other field roles
  • Play a key role in maintaining and growing company revenue over time

WHAT YOU'LL GET

  • Highly competitive benefits and vacation package
  • Ability to work for one of the fastest growing companies with some of the most talented people in the industry
  • Team outings
  • Fun, Hardworking, and Casual Environment
  • Endless Growth Opportunities

At CloudBees, we truly believe that the more diverse we are, the better we serve our customers.  A global community like Jenkins demands a global focus from CloudBees. Organizations with greater diversity—gender, racial, ethnic, and global—are stronger partners to their customers.  Whether by creating more innovative products, or better understanding our worldwide customers, or establishing a stronger cross-section of cultural leadership skills, diversity strengthens all aspects of the CloudBees organization.

In the technology industry, diversity creates a competitive advantage.  CloudBees customers demand technologies from us that solve their software development, and therefore their business problems, so that they can better serve their own customers.  CloudBees attributes much of its success to its worldwide work force and commitment to global diversity, which opens our proprietary software to innovative ideas from anywhere. Along the way, we have witnessed firsthand how employees, partners, and customers with diverse perspectives and experiences contribute to creative problem solving and better solutions for our customers and their businesses.

Senior DevOps Engineer
EMEA

OUR CUSTOMERS DEVELOP SOFTWARE AT THE SPEED OF IDEAS

CloudBees, the enterprise software delivery company, provides the industry’s leading DevOps technology platform. CloudBees enables developers to focus on what they do best: Build stuff that matters while providing peace of mind to management with powerful risk mitigation, compliance, and governance tools. Used by many of the Fortune 100, CloudBees is helping thousands of companies harness the power of continuous everything and gets them on the fastest path from a great idea, to great software, to amazing customer experiences, to being a business that changes lives.

Backed by Matrix Partners, Lightspeed Venture Partners, Verizon Ventures, Delta-v Capital, Golub Capital, and Unusual Ventures, CloudBees was founded in 2010 by former JBoss CTO Sacha Labourey and an elite team of continuous integration, continuous delivery, and DevOps professionals.

It’s an exciting time to be part of the CloudBees team. That’s because thousands of development and deployment teams around the world are using CloudBees products that enhance and optimize the way their teams build and deliver software using continuous delivery.

To support the delivery of CloudBees products (both internal and external), CloudBees has an Operations team that designs, deploys, secures and manages a variety of software systems and the related GCP / AWS infrastructure that underpins these software engineering objectives.

The Operations team guiding principle is simple - “Make Engineering Faster”.

Underpinning this are the challenges of security, process change, technical change that all must be met to varying degrees.

Further, we are passionate about reducing the manual work that plagues IT teams - Engineering / Ops / Support / Security - and are empowered to re-engineer processes (more easily said than done) and technology to achieve those objectives.

Location

Our preferred candidate will be located in a European time zone to provide the best working hour coverage for our Engineering and Operational workloads. Please visit our website for a list of our approved hiring locations https://www.cloudbees.com/careers

What you’ll be doing

Team-building - inside the team and across teams - you’ll be proposing new ideas and helping implement them

Thinking - coming up with new ways of solving problems - and working with the team to prove them out and then implement them

Documenting - describing problems, how your proposed solution solves those problems, and how your implemented solutions are operated.

Optimizing - working with Engineering teams to optimize their build systems - even our monster jobs (lots of parallelism - lots of bottlenecks - lots of technical challenges)

Defining - writing / modifying Terraform to handle our infrastructure, and helping teams define their infrastructure using our modules.

Coding - you’ll be writing code in Golang - we occasionally write glue in Python / Groovy (but not very often)

Securing 

  • working with our security team to drive operational change in engineering teams - “Supply Chain Integrity” - you’ve heard about it - it’s the new hot topic
  • working with our security team to drive organizational security changes (logging, auditing, monitoring, alerting)

Observing - adding the right monitoring so that we are alerted before our customers notice, and not alerted when the system is able to heal itself

Alerting - getting alerts and working with team members to solve the initial problem, documenting the problem and then working out how to stop them happening again

DevOps / DevSecOps - We’re not “DevOps” engineers, but we do help our teams become more proficient in doing Dev and Ops (and embracing Total Ownership). We build the guard rails to help them do it safely and align tech-stacks across the company.

What you’ll bring to the team

  • New ideas from where you’ve worked in the past - what worked well, what didn’t work, what CloudBees could do better?
  • “the knack” - an uncanny ability to uncover the root cause of problems based on limited information because “it feels like something you’ve seen before”
  • The courage to say - “I’m not sure” - and getting feedback from your colleagues on how to complete a task in our tech-stack
  • No fear of saying - “Have you considered doing it this way” - and giving constructive feedback to colleagues on alternative ways of doing things

What you’ll work on

  • Corporate tools - GSuite, GitHub, Jira, Confluence, Slack
  • Operations tools - PagerDuty, DataDog
  • Language tools - Golang
  • Engineering tools - Jenkins, Vault, CodeShip, Auth0
  • Platform tools - Kubernetes, terraform, helm, docker
  • IaaS - GCP, AWS, a little Azure

There are a lot more tools - you should ask during your interview!

How you’ll be part of the team

You are:

  • self-motivated and enjoy solving problems
  • excited by the opportunity to automate yourself out of recurring work
  • able to keep tickets up to date, so we don’t need too many status meetings (we’re async first due to our distributed nature)
  • You will liaise directly with the software engineers across all teams, ensuring that decisions are agreed internally and externally to Operations and that they meet our technical and non-technical objectives.

You have experience in:

  • programming in various languages and domains
  • the "modern Ops stack" (e.g. monitoring, alerting, cloud-based provisioning, Docker, Kubernetes)
  • Linux systems administration
  • cloud-based operations (GCP, AWS, or Azure)
  • cluster orchestration and management tools (e.g. k8s / ECS / Terraform / etc)
  • continuous integration / continuous delivery tools (Jenkins / CodeShip etc)
  • modern software engineering practices: code reviews, unit / acceptance testing, source control, etc.

How you’ll work

  • You work in a geographically distributed team (APAC, US, EMEA) of peers
  • You choose your own work in tandem with the team, team-leader, and manager
  • You report directly to the Operations Manager (who reports to the VP of Engineering)
  • Your working hours are flexible - while there will be some core hours required for meeting with Engineering and Operations teams - much latitude is given in getting work done. This includes determining your own start and finish times to accommodate family life.
  • Travel is limited (especially at the moment) - but once things return to normal (whatever that looks like) we’ll have an annual offsite somewhere on the planet

On-Call

We prefer to avoid out-of-working-hours on-call where possible (and are geographically distributed to achieve this), however it is expected that you will be willing to respond to alerts out of hours on a best-effort basis. You don’t take your laptop anywhere unless you want to.

Work hours on-call is just known as “work” - if it blows up - you fix it or find someone who can fix it.

Engineering teams operate under a “Total Ownership” model - they own their entire stack and are empowered to fix it.  They occasionally need help out of hours, and we provide best-effort support.

As an example - 

  • No one has been woken up for an outage in over 8 years
  • There hasn’t been a weekend outage in the last 6 months
  • We have had to triage security vulnerability reports (on weekends), but those have not required work beyond the initial fault analysis.
  • There are occasional false-positives - that are easily silenced - and then resolved at a system level during normal working hours.

We have a culture of movers and shakers and are leading the way for everyone else with a vision to transform the industry. We are authentic in who we are. We believe in our abilities and strengths to change the world for the better. Being inclusive and working together is at the heart of everything we do. We are naturally curious. We ask the right questions, challenge what can be done differently and come up with intelligent solutions to the problems we find. If that’s you, get ready to bee impactful and join the hive.

At CloudBees, we truly believe that the more diverse we are, the better we serve our customers. A global community like Jenkins demands a global focus from CloudBees. Organizations with greater diversity—gender, racial, ethnic, and global—are stronger partners to their customers. Whether by creating more innovative products, or better understanding our worldwide customers, or establishing a stronger cross-section of cultural leadership skills, diversity strengthens all aspects of the CloudBees organization.

In the technology industry, diversity creates a competitive advantage. CloudBees customers demand technologies from us that solve their software development, and therefore their business problems, so that they can better serve their own customers. CloudBees attributes much of its success to its worldwide workforce and commitment to global diversity, which opens our proprietary software to innovative ideas from anywhere. Along the way, we have witnessed firsthand how employees, partners, and customers with diverse perspectives and experiences contribute to creative problem solving and better solutions for our customers and their business.

Verified by
Technical Evangelist
You may also like