Operations | Monitoring | ITSM | DevOps | Cloud

Software development teams are much larger than the engineers that write code. Writing and deploying code are often only the tip of the iceberg. A well oiled software team will often consist of: All of these people need to know something about what the software development lifecycle is producing and shipping, but the level of information can vary dramatically based on a team member's position. Sleuth was built to automatically generate information to satisfy each team member's needs.

In today’s enterprises, DevOps isn’t one process, but many thinly connected tasks. A stack of DevOps tools that need to work together to operate as a single system, each one requiring its own integration and maintenance. The JFrog DevOps Platform unifies our industry-leading products because DevOps has a single goal: to speed releases from code to production. It takes several tools to build DevOps, but DevOps tools need to function as one.

To ensure that Cloudsmith is and remains a ‘universal’ package management solution, we continue to add formats and extend the scope of the platform. Hence the launch today of our support for CocoaPods.

Here at Sentry, we use Travis CI, a continuous integration tool for GitHub that lets us automate our tests and view the results right within each pull request. In this blog post, we’ll walk through a quick example of how to automatically create Sentry Releases with Travis CI when a commit is pushed to your project’s master branch. (Sentry Releases enable some of our best features, like identifying the commits that likely introduced new errors, and much more!)