CI/CD Consulting

Our diverse client roster enables us to gain a broader perspective of CI/CD than companies focusing exclusively on mid-sized clients; as a result, many challenging and intriguing open-source projects required us to customize existing systems by building new CI/CD systems based on them, given their large volume. When working on push/commits that require numerous events such as queues, triggers or other features we often create event driven systems which include waiting queues as part of these builds.

Unfortunately, tools are continually changing so we are unable to suggest one or several as solutions are always evolving. Jenkins and GitlabCI remain market leaders; however, other CI/CD tools might better suit your needs than these market leaders; more companies are adopting GitOps techniques, with newcomers such as JenkinsX or ArgoCD available now too. You should think carefully about customization needs; some TravisCI may suffice while for others Jenkins would provide more customization features; ultimately it depends on you and your company - some TravisCI will suffice while for others Jenkins would need be required in order to integrate custom logic - before choosing what tool(s).

Our favorite question when interviewing candidates for positions, we ask this one often because it enables us to assess their understanding of this practice. Essentially, Continuous Delivery occurs where there is no human intervention - think automated pipeline as opposed to one where someone manually pushes a red button at any point during deployment stage.

Continuous Deployment is another option; while automation tools will likely play an integral part, security testing process still must take place prior to making changes live for users. We do not advocate this practice but for certain systems/platforms this may be their only means for getting updates out to end-users quickly and reliably.

Surely it should be used by developers, DevOps engineers and DevOps managers. A strong Continuous Delivery/Deployment system relies heavily on its Quality Assurance team for development. Developers should maintain quality in code that they build via Continuous Integration; how you do so depends on what principles your organization employs. When we talk about Continuous Delivery/Deployment, however, QA should play an integral part ensuring new versions have more positive than negative side-effects before deploying it - whether manually or automatically; what's essential here is not expecting code developers themselves can guarantee its quality; instead professional specialists must do this manual task instead!

Automating all aspects of your system may seem impossible, and while that would certainly be ideal, if resources are tight, prioritize automating only those components with critical importance for saving QA time by automating them. Automating basic and important logic of applications/platforms may prove more cost effective for you in terms of unit testing and time savings than doing everything yourself manually.