Release your Applications Reliably
Start your release by importing any number of build artifacts directly from Jenkins, TeamCity, TFS, Visual Studio, or a drop path.
If you're not already automating your builds, then BuildMaster can retrieve code from source control, build it, and run unit tests.
Automate your existing deployment process - whether that's for web applications, desktop tools, or cloud services.
Include "manual tasks" in your deployment plan to allow for steps that are impractical to automate.
On a single dashboard, see across all applications and environments to discover which stage various releases are, and which releases need attention.
Manage your release in one place, and see targeted environments, detailed deployment history, release notes, milestone dates, and more.
Create and share calendars that combine deployment windows, milestones, testing phases, and scheduled deployments across multiple applications.
Define user, group, and automated approval requirements before allowing deployment at different stages.
Integrate project and issue tracking tools like JIRA, TFS and YouTrack to ensure deployments happen only when issues are closed, and automatically update issues with release details.
Restrict who can deploy to which environment, and define other granular access control policies as needed.
Roll back if needed to a previously successful release at any time.
Created exclusively for infrastructure automation and orchestration, the Inedo Execution Engine makes it easy to deploy and execute across hundreds of servers, and provides detailed logging (with sensitive debugging details hidden from certain users) to let you quickly identify what went wrong
A lightweight, highly-optimized agent that allows a server to be securely orchestrated by a connected Inedo product. It's simple to deploy and upgrade, but is also backwards- and forwards-compatible to minimize change risks.
A lot of Inedo's product functionality is delivered through extensions, and you can add or modify functionality and capabilities to our product by creating an extension. Because this is a shared SDK, you can write a component once and introduce the same functionality across all of our products
