Build greenfield projects, legacy applications, microservices, and more… without replacing your current stack.
Full-fledged CI that features automated unit testing, integration with static analysis tools, build reports, and more.
Deploy software to Windows or Linux servers, VMs, containers, Kubernetes clusters, cloud, mainframes, mobile, or PaaS.
Enforce the full CI/CD pipeline with gated issue tracking integration, manual user approvals, deployment windows, and automated checks.
BuildMaster is a fully-functional Continuous Integration tool for a variety of platforms allowing your organization to start using CI/CD today, even with legacy applications and using your current tech stack.
Build any type of .NET Framework application, including WinForms, services, WPF, ASP.NET MVC websites, Azure, .NET Core, and more with MSBuild support
Build core Java applications, Java EE, Spring applications, and more with maven or ant support
Build Node.js applications using tools such as Babel, Broccoli, Webpack, JSLint, TypeScript, and Grunt
PHP & More
Run quality tools (e.g. static analysis, transpilers, and other reporting tools) against code that does not require a typical “build” task, but still requires packaging
External Build Systems?
BuildMaster also supports referencing or importing artifacts from other CI tools such as:
Create, pull, and push build artifacts or packages from/to any Universal Repository, including ProGet, Nexus, or Artifactory
Let BuildMaster run automated testing for your applications and notify key team members if those tests fail.
Run unit tests against builds of any platform including Visual Studio Test, NUnit, JUnit, XUnit, and PHPUnit
Execute and capture code coverage reports, static analysis results, test coverage reports, and diffs alongside builds
Perform automated UI tests using Selenium, HPE Unified Functional Testing, SmartBear TestComplete, and more
Create and manage build artifacts for any deployment target, from simple ZIP files to complex container orchestrations in the cloud.
Build Docker containers, package your applications inside of a Docker container, or reference a Docker container stored in a Universal Repository
Create packages for cloud-based deployment to Azure, AWS, and more
As a full-fledged CI tool, BuildMaster can capture and host its own artifacts which can contain virtually every other type of deployment package
Use configuration files to create Helm Charts to version, share, and publish your Kubernetes applications, removing the guesswork of copy/paste from deployment
Package your applications into a Universal Package for deployment across environments
In addition to creating and managing build artifacts, BuildMaster is an automated deployment tool that can target virtually any platform used by any application in your organization.
Deploy to physical servers or virtual machines of any platform using the Inedo Agent, or over other protocols including SSH, WinRM, FTP, or simple file shares
Deploy containerized applications directly to servers, in-house Kubernetes clusters, or cloud-based container services including Azure Container Services, Azure Kubernetes Services (AKS), Google Kubernetes Engine (GKE), IBM Cloud Kubernetes Service, or Amazon Managed Kubernetes Service (EKS)
Guarantee uptimes with deployments targeting IBM zSeries, AS/400, and others using FTP or SFTP
Deploy applications, microservices, and files to cloud services including Microsoft Azure, Amazon AWS, Google Cloud, and IBM Cloud
Deploy mobile apps to the Google Play Store or App Store
Deploy and track database change scripts to the most popular database engines including SQL Server, My SQL, PostgreSQL, DB2, and Sybase
Deploy using familiar patterns and practices:
Use deployment variables to determine blue or green targets, and swap your load balancer, application pool, or host to eliminate downtime
Incrementally deploy to sets of servers using server roles, multiple pipeline stages, or explicit server targeting
Share deployment plans across an unlimited number of tenants to manage and track tenant deployments as quickly as the business can scale
Build, release, and deploy from repositories using the GitFlow pattern, configuring pipelines to enforce merge policies such that deployment branches never end up in production
Already have a custom process? Easily script your own!
BuildMaster is powered by the Inedo Execution Engine, allowing organizations to automate even the most complex deployments with a simple, declarative syntax
Execute any PowerShell, Bash, command-line, batch, process, or non-interactive program at any stage of deployment
BuildMaster integrates with issue trackers and performs other automated checks to keep human ingenuity in your release process while eliminating human error that costs your organization time and money.
BuildMaster integrates with several issue tracking tools to link issues with releases, change issue statuses after deployments, or ensure issues are in a certain status before deployments are permitted
Document and notify users or teams when their approval is required to deploy builds into testing environments or production, providing auditability and compliance for regulatory requirements or organizational change control policies
Select specific times that deployments can occur, and schedule them to occur within these timeframes without further human intervention
Establish automated gates to guard against the shipping of untested software into later stages of the delivery pipeline when they could have been caught earlier
Reduce overhead by orders of magnitude, enabling your organization to make decisions based on requirements and release on demand.
Immediately notify stakeholders at any stage during the release process who may be interested in the result of a build or deployment success or failure
Assign relevant target dates to track and coordinate releases on a calendar view, optionally alongside past or scheduled deployments, other releases’ target dates, and deployment window openings
Create multiple pipelines for the same project or application, enabling the ability to have separate release processes for different versions such as hotfixes, without locking in the complete release process at build time
Deploy previously released versions to rollback production bugs that impact the business