💃 Let's chat about CI/CD best practices🕺

Good morning, Salesforce Nerds! Show of hands 🖐️, how many of you are working with teams that execute a CI/CD pipeline? 🤔 

How many of you are working with teams that WANT to execute a CI/CD pipeline? ⚙️ 

By now everyone’s hands 🖐️ should be up!

Before you schedule 📆 that meeting to talk through what implementing one will look 👀 like …

You should understand some important concepts & best practices! 💯 

That’s where 💃 ChaCha 🕺 comes in! 🤙 

These are three simple rules ✔️ any team running a successful pipeline adhere to …

Agenda for today includes

• Let's chat about CI/CD best practices

• Daily Principle

• All the Memes

Let's chat about CI/CD best practices

Today we will discuss -

💃 Merge early. Merge often. 🕺

💃 Shift Left🕺

💃 Keep the builds green🕺

Job Board | 💃 Click Here 🕺

Socials | 💃 Linkedin | Instagram | Twitter!🕺

⌛️ Merge early. Merge often.

This is one of the hallmarks of pro-grade pipeline! 💪 

You’re aiming 🎯 to merge small units of code/configurations into your repository at the earliest 🌅 possible time.

Why? 🤔 

Because this positions you to find out as quickly as possible if the stuff you’re building plays 🛝 nicely with:

✅ The stuff other people are building

✅ The stuff that’s already been built

It also helps 🤝 ensure the team is working against a fresh codebase when they spin up a new branch - which is one that reflects the latest work from everyone on the team. 💯 

This is muy importante!!

Failing to do this will inevitably cause merge conflicts down the line that will slow progress and block releases. 😡 

◀️ Shift Left

Shifting Left means moving 🧪 testing, 🤩 QA evaluations, ❎ validations as early in the development cycle as possible.

In other words, don’t get into the habit of testing code too late. ⏲️ Put the work in to get your lower environments the data they need to let your team effectively test EARLY! ⌚️ 

If you don’t - you will put strain on the team and won’t produce a quality product. ❌ 

Implementing the following practices & tools will help get you there:

✅ Automated tests (unit, integration, UI, etc.)

✅ Static Code Analysis

Place these kind of validations throughout your pipeline - especially early in the lower environments like Integration, QA, and UAT. 🧠 

You know … towards the LEFT ◀️ of your pipeline! 🤯 

Keep ‘em lean and mean 👿 so you don’t tie down devs with promotions that are a major PIA! 🫡 

The result is failing fast when issues arise. 🤤 

🟢 Keep the builds green

To a dev, a green 🟢 build signals that the code is working! 🥳 

Now if the ethos of CI/CD is to be able to release on demand 💥, then a green build what we need to see in order to sleep at night. 😴 

This means it’s priority #️⃣1 to keep the code in a constantly releasable state. 🔄 

Not only does this help you efficiently address issues as soon as they arise. 💪 

But, it also makes is possible to roll out hotfixes quickly⚡️when something goes wrong in prod. 🤕 

If a build fails, it should be your top priority to get it working again! 1️⃣

Daily Principle

and now....Your Daily Memes