- BuildMaster
- Getting Started with BuildMaster
- Builds and Continuous Integration
- What is a "Build" in BuildMaster?
- Git and Source Control
- Git Pipelines and Workflows
- Build Scripts & Templates
- Packages & Dependencies
- Build Artifacts
- Automated Testing & Verification
- Deployment & Continuous Delivery
- What is a “Pipeline” in BuildMaster?
- CI Server (Jenkins, TeamCity, etc.) Integration
- Deployment Scripts & Templates
- Automatic Checks & Approval Gates
- Manual Deployment Steps and Tasks
- Databases
- Configuration Files
- Rollbacks
- Advanced CD Patterns
- Applications & Releases
- Connecting to your Servers with BuildMaster
- Scripting in BuildMaster
- Configuring for Your Team
- Docker/Containers
- Development Platforms
- Deployment Targets
- Tools & Service Integrations
- Reference
- BuildMaster API Endpoints & Methods
- Extending BuildMaster
- Built-in Functions & Variables
- Applications
- Builds
- Configuration Files
- Containers
- Credentials
- Databases
- Deployables
- Environments
- Executions
- Files
- General
- JSON
- Linux
- Lists
- Maps
- Math
- Nuget
- Packages
- Pipelines
- PowerShell
- Python
- Releases
- Servers
- Strings
- XML
- Built-in Operations
- Batch
- BuildMaster
- Configuration Files
- Databases
- DotNet
- Files
- Firewall
- General
- Apply-Template
- Attach Package
- Build
- Checkout-Code
- Close-Issue
- Concatenate-Files
- Copy-Files
- Create-Directory
- Create-File
- Create-Issue
- Create-Issue
- Create-IssueComment
- Create-Package
- Create-ZipFile
- Delete-Files
- Download-Asset
- Download-Http
- Ensure-Directory
- Ensure-File
- Ensure-HostsEntry
- Ensure-Metadata
- Ensure-Milestone
- Ensure-Package
- Ensure-Release
- Ensure-Tag
- Exec
- Execute Python Script
- Execute VSTest Tests
- Get-Http
- Install-Package
- OSCall
- OSExec
- Post-Http
- Push-PackageFile
- PYCall
- PYEnsure
- Query-Package
- Remediate-Drift
- Rename-File
- Repackage
- Replace-Text
- Send-Email
- Set-FileAttributes
- Set-Variable
- SHEnsure
- Sleep
- Transfer-Files
- Transition-Issues
- Upload-Assets
- Upload-Http
- Upload-ReleaseAssets
- Git
- IIS
- Nuget
- PowerShell
- ProGet
- Python
- Registry
- Servers
- Services
- Shell
- Windows
- Administration
- Installation & Upgrading
- ProGet
- Getting Started with ProGet
- Packages: Managing & Tracking
- Feeds Types & Third-Party Packages
- What is a "Feed" in ProGet?
- What is a "Connector" in ProGet?
- NuGet (.NET)
- Universal Feeds & Packages
- PowerShell
- Chocolatey (Windows/Machine)
- RubyGems (ruby)
- Visual Studio Extension (.vsix)
- Maven (Java)
- npm (Node.js)
- Bower (JavaScript)
- Debian (Apt)
- Helm (Kubernetes)
- PyPI (Python)
- Conda (Python)
- RPM (Yum)
- Alpine (APK)
- CRAN (R)
- pub (Dart/Flutter)
- Cargo (Rust)
- Terraform Modules
- Conan (C++)
- Other Feed Types
- Asset Directories & File Storage
- Docker and Containers
- Replication & Feed Mirroring
- Software Composition Analysis (SCA)
- Security and Access Controls
- Cloud Storage (Amazon S3, Azure Blob)
- Administration
- Installation & Upgrading
- API Endpoints & Methods
- Otter
- Getting Started with Otter
- Orchestration & Server Automation
- Connecting to your Servers with Otter
- Collecting & Verifying Configuration
- Drift Remediation / Configuration as Code
- Scripting in Otter
- Configuring for Your Team
- Installation & Upgrading
- Administration & Maintenance
- Reference
- Otter API Reference
- OtterScript Reference
- Built-in Functions & Variables
- Executions
- Files
- General
- JSON
- Linux
- Lists
- Maps
- Math
- PowerShell
- Python
- Servers
- Strings
- XML
- Built-in Operations
- Batch
- Docker
- DotNet
- Files
- Firewall
- General
- Apply-Template
- Collect Debian Packages
- Collect RPM Packages
- Collect-InstalledPackages
- Concatenate-Files
- Copy-Files
- Create-Directory
- Create-File
- Create-Package
- Create-ZipFile
- Delete-Files
- Download-Asset
- Download-Http
- Ensure-Directory
- Ensure-File
- Ensure-HostsEntry
- Ensure-Metadata
- Ensure-Package
- Exec
- Execute Python Script
- Get-Http
- Install-Package
- OSCall
- OSExec
- Post-Http
- Push-PackageFile
- PYCall
- PYEnsure
- Query-Package
- Remediate-Drift
- Rename-File
- Repackage
- Replace-Text
- Send-Email
- Set-FileAttributes
- Set-Variable
- SHEnsure
- Sleep
- Transfer-Files
- Upload-Assets
- Upload-Http
- IIS
- Otter
- PowerShell
- ProGet
- Python
- Registry
- Servers
- Services
- Shell
- Windows
- Installation & Maintenance
- Windows (Inedo Hub)
- What is the Inedo Hub?
- Configuring & Maintaining Inedo Products
- Offline Installation (no Internet access)
- HOWTO: Install on Windows
- HOWTO: Upgrade or Downgrade with the Inedo Hub
- HOWTO: Install Pre-release Product Versions
- HOWTO: Configure Your Inedo Product to Run As a Windows Domain Account
- Silent/Automated Installation Guide
- Legacy (Traditional) Installer
- Linux (Docker)
- Manual Installation
- High Availability & Load Balancing
- LDAP/AD Integration
- IIS & Web Hosting on Windows
- Logging & Analytics
- SAML Authentication
- Upgrading your Inedo Product
- Managing Agents and Servers
- Backing Up & Restoring
- Installation Configuration Files
- SQL Server & Inedo Products
- Windows (Inedo Hub)
- Inedo Agent
- What is the Inedo Agent?
- Installation & Upgrading
- Downloads & Release Notes
- Maintenance & Configuration
- Internal Architecture
- MyInedo
- OtterScript (Execution Engine)
- Reference
- OtterScript
- Inedo Execution Engine
- Operations & Functions
- Text Templating
- Resource Pools
- Runtime Variables
- Advanced Scenarios & Features
- Statements and Blocks
- Romp (Discontinued)
- Using Romp
- Installing, Configuring, and Maintaining
- Romp CLI Reference
- Package Layout
- Downloads & Source Code
- Extensibility
- Inedo SDK
BuildMaster Health API
The Get BuildMaster Health is an endpoint that will return a BuildMasterHealth object describing the health of a BuildMaster instance.
Using this endpoint does not require an API key and can be accessed by simply adding /health
to your BuildMaster URL (e.g. https://proget.corp.local/health
)
This example will get the health of a BuildMaster instance with the URL proget.corp.local
:
curl -H "Content-Type: application/json" -X GET https://proget.corp.local/health
Request Specification
To return the health status of a BuildMaster instance, simply GET
to the URL.
GET /health
Response Specification
A successful (200
) response body will return an BuildMasterHealth object. For example, to querying the health of a BuildMaster instance, the request would return this:
GET /health
{
"applicationName": "BuildMaster",
"databaseStatus": "OK",
"databaseStatusDetails": null,
"extensionsInstalled": {
"BuildMaster Core Extensions": "23.0.9",
"BuildMaster": "23.0.9",
"Inedo.SDK": "2.4.0",
"Azure": "2.0.1",
"AzureDevOps": "2.4.0",
"Bitbucket": "2.4.0",
"Docker": "2.4.3",
"DotNet": "2.2.7",
"Git": "2.4.0",
"Gitea": "2.4.0",
"GitHub": "2.4.2",
"GitLab": "2.4.0",
"InedoCore": "2.4.0",
"Java": "2.2.0",
"Jenkins": "2.4.0",
"Jira": "2.4.2",
"Node": "2.2.0",
"Python": "2.2.0",
"Scripting": "2.4.0",
"TeamCity": "2.4.0",
"Windows": "2.0.3"
},
"instanceName": null,
"licenseStatus": "OK",
"licenseStatusDetail": null,
"versionNumber": "2023.9 (Build 1)",
"releaseNumber": "23.0.9",
"serviceStatus": "OK",
"serviceStatusDetail": null
}
Response | Details |
---|---|
200 (Success) | body will contain a BuildMasterHealth object |
500 (Server Error) | indicates an unexpected error; the body will contain the message and stack trace, and this will also be logged |
BuildMasterHealth Object Attributes
BuildMasterHealth
is a set of key/value pairs that describe the health status of a ProGet instance. It's used as output data for the Get BuildMaster Health endpoint as a JSON-formatted object.
Property | Format | Notes |
---|---|---|
applicationName |
string | For this API it will be BuildMaster as default |
databaseStatus |
string | health state of the database. (OK or Error ) |
databaseStatusDetails |
string? | a specific error message if databaseStatus is Error (default null ) |
extensionsInstalled |
object | describes the extentions installed in the instance and their versions (e.g. "Azure": "2.0.1" ) |
instanceName |
string? | the name of the instance (default null ) |
licenseStatus |
string | health state of the product license. (OK or Error ) |
licenseStatusDetail |
string? | a specific error message if licenseStatus is Error (default null ) |
versionNumber |
string | current version number of the instance |
releaseNumber |
string | current release number of the instance |
serviceStatus |
string | health state of the service. (OK or Error ) |
serviceStatusDetail |
string? | a specific error message if serviceStatus is Error (default null ) |