Operations | Monitoring | ITSM | DevOps | Cloud

Incident responders often find themselves under pressure to resolve issues quickly and efficiently. Once the alert comes in and the incident resolution starts, the actions taken in the next few minutes can make all the difference. Essential actions involve collaborating with team members and invoking specialized scripts for common issues like disk space shortages or server restarts.

When it comes to welcoming new developers into a team, a well-thought-out onboarding process is key. It all starts with setting clear goals and expectations right out of the gate, helping everyone understand their role and how it fits into the bigger picture of the company’s objectives. This, paired with a structured training program, can blend the often confusing process of learning the ropes with actual hands-on experience.

CEO Glenn Weinstein highlights Cloudsmith's support of the open source community.

In parts one and two of this series, we covered how to limit deployments to Upsun when a tag is pushed or created. Focusing first on using GitHub and the GitHub Actions platform, and then progressing onto Gitlab and pipelines to accomplish this goal. But in the spirit of being a polyglot PaaS, let’s look at how we can accomplish the same goal—limiting deployment to Upsun only when adding a git tag—using Bitbucket and their CI/CD system.