The list, filters, and rules

The header

The same Rules and Refresh buttons as Pull Requests, working the same way: Refresh re-fetches, and the previous list stays visible if a refresh fails.

How do I filter?

The filter bar offers:

• Search deployment (free text)
• All statuses dropdown: Success, Failed, Running, Queued, Cancelled, Skipped
• Source (free text, for example codepipeline)
• Environment (free text, for example production)
• From / To date pickers
• Clear: only appears once at least one filter is set

Two extra status badges can show up on rows or the detail page even though they are not options in the status filter: Action required and Partial (both styled as warnings).

The table

Each row shows: the pipeline or workflow name and run number; the first 12 characters of the commit hash; the source (with a provider badge and repository, account, and region context); a status badge; the target environment and branch; how long the run took; and when it was last updated. Click a row to open its detail page.

A count line reads {n} deployment(s) (with "· refreshing…" while a background fetch runs), and Previous / Next with a Page X of Y label page through longer lists.

States you will see instead of the table:

• No project selected: "Select a project to load its deployments."
• Loading: "Loading deployments…"
• Nothing matches your filters: "No deployments match the current filters."

Rules

Click Rules (requires repo:manage) to open Deployment rules, where you choose whether ACE analyzes failed runs automatically. The filter scopes that behavior. The toggle is set separately for Other event sources (provider-neutral deployment data sent in from outside a connected repository) and for each connected repository:

• Analyze failures automatically: runs the agent only after a run ends in failure. The analysis result stays inside ACE.
• A pattern field beneath the toggle, enabled only while the toggle above is on, scopes which runs the analysis covers:
  • For a connected repository: Branches / refs for analysis is comma-separated, supports * wildcards, and empty means every branch or ref.
  • For other event sources: Pipelines / build projects for analysis matches the run's name as reported by things like CodePipeline or CodeBuild, with the same wildcard rules.

If no repository is connected yet, that section reads "Connect a repository to add provider-specific deployment rules." instead of the form.

A note in each section reminds you that rule changes only apply to runs observed after the change; a run already in progress keeps the rules that were active when it started. Click Save rules to apply, or Cancel / Close (Close, if you lack repo:manage) to leave without saving.