This article describes how continuous integration, delivery, and deployment can help development teams build and release software quickly and reliably.

Joao Grassi — a .NET developer, front-end hobbyist, and friend of Sentry — likes .NET very much and recently tried to bring a friend to the “dark side” of .NET development. To win a point, he decided to create a small sample project using Azure DevOps. As he started, he struggled to find helpful information in the documentation (like how to control the artifact name).

Continuous testing has evolved to become an important phase in modern application development and delivery. When we at Sumo Logic sketched out a plan to start delivering our microservices continuously, we knew we needed to define a delivery pipeline, which would run our automated tests and provide feedback in early phases of development.

So much of our world has moved away from the slow and methodical, towards the agile and iterative. In transport, for example, everything is “on demand”, constantly changing and adaptable. The same is true for developers. With movements and philosophies such as CI/CD, everything is about moving quickly, yet smartly. Test automation is an integral part of this development philosophy.

Shipping clean, safe, and correct code is a high priority for engineering at Sentry. Bugs are best discovered before they hit production because afterward they have real user impact and can drain even a high-performing team’s resources quickly. The later in the development cycle a bug is found, the longer it will take to fix.

In many projects, the product development workflow has three main concerns: building, testing, and deployment. Each change to the code means something could accidentally go wrong, so in order to prevent this from happening developers adopt many strategies to diminish incidents and bugs. Jenkins, and other continuous integration tools (CI) are used together with a source version software (such as GIT) to test and quickly evaluate the updated code.

In this blog post we’ll cover how to implement Docker Scanning for Jenkins with the Sysdig Secure Jenkins plugin. The plugin can be used in both freestyle and pipeline jobs to scan images and fail the build if the image fails a policy evaluation.

Get a decent source code management system like Github, Gitlab or Bitbucket etc. Every one uses the same code and keeps upto date with base line. this reduces the merge conflict issues. Don’t put every thing in SCM but everything you need to do a build should be in there including: test scripts, properties files, database schema, install scripts, and third party libraries

It's time for a newsletter from your friendly neighbourhood Package Management as a Service provider - Summer 2018 Edition. Can you believe it's summer-time already? It's hard for us to tell from the cave that we're coding in day and night, but the office thermostat indicates that it is probably sunny way up there, above the ground.