No matching results found
- 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
 - 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++)
 - Composer (PHP)
 - Other Feed Types
 
 - Asset Directories & File Storage
 - Docker and Containers
 - Replication & Feed Mirroring
 - Software Composition Analysis (SCA)
 - Security and Access Controls
 - Cloud Storage
 - Administration
 - Installation & Upgrading
 - API Methods and CLI Commands
 
 - 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)
 - Linux (Docker)
 - High Availability & Load Balancing
 - User Directories & Domains (LDAP)
 - Logging & Analytics
 - SAML Authentication
 - When to Upgrade your Inedo Product
 - Managing Agents and Servers
 - Backing Up & Restoring
 - Installation Configuration Files
 - PostgreSQL & Inedo Products
 - SQL Server & Inedo Products
 
 - 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
 - Romp (Discontinued)
- Using Romp
 - Installing, Configuring, and Maintaining
 - Romp CLI Reference
 - Package Layout
 - Downloads & Source Code
 - Extensibility
 
 
 - Inedo SDK
 
List Projects
List Projects is available as both a pgutil command and an HTTP Request, and will return an array of ProjectInfo Object objects describing all projects.
🚀 Quick Example: Listing Projects with pgutil
This example lists all existing projects:
pgutil builds projects list
Command Specification (CLI)
The builds projects list command is used to list all existing projects.
Listing projects requires no additional options.
Example output:
myProject
anotherProject (Application)
yetAnotherProject (Application)
testApplication
HTTP Request Specification
To list all projects, simply GET to the URL with an appropriate API Key.
GET /api/sca/projects
HTTP Response Specification
A successful (200) response body will contain an array of ProjectInfo Object objects. For example, to listing all projects, the request would return this:
GET /api/sca/projects
[
  { 
    "id":1,
    "name":"myProject"
  },
  { 
    "id":2,
    "name":"anotherProject"
  },
  { 
    "id":3,
    "name":"yetAnotherProject"
  },
  {...}
]
| Response | Details | 
|---|---|
| 200 (Success) | body will contain an array of ProjectInfo objects | 
| 400 (Invalid Input) | indicates invalid or missing properties | 
| 403 (Unauthorized API Key) | indicates a missing, unknown, or unauthorized API Key; the body will be empty | 
| 500 (Server Error) | indicates an unexpected error; the body will contain the message and stack trace, and this will also be logged |