You use search to find where specific items or other components are located. For example, you might want to search for enabled or disabled pipelines. Because if a pipeline is disabled, it cannot run.

What can I search

You can search in:
  • Projects
  • Endpoints
  • Pipelines
  • Executions
  • Pipeline Dashboards, Custom Dashboards
  • Gerrit Triggers and Servers
  • Git Webhooks
  • Docker Webhooks
You can perform column-based filter search in:
  • User Operations
  • Variables
  • Trigger Activity for Gerrit, Git, and Docker

You can perform grid-based filter search on the Activity page for each trigger.

How does search work

The criteria for search varies depending on the page you are on. Each page has different search criteria.
Where you search Criteria to use for search
Pipeline Dashboards Project, Name, Description, Tags, Link
Custom Dashboards Project, Name, Description, Link (UUID of an item on the dashboard)
Executions Name, Comments, Reason, Tags, Index, Status, Project, Show, Executed by, Executed by me, Link (UUID of the execution), and Input parameters, Output parameters, or Status message by using this format: <key>:<value>
Pipelines Name, Description, State, Tags, Created by, Created by me, Updated by, Updated by me, Project
Projects Name, Description
Endpoints Name, Description, Type, Updated by, Project
Gerrit triggers Name, Status, Project
Gerrit servers Name, Server URL, Project
Git Webhooks Name, Server Type, Repo, Branch, Project
Where:
  • Link is the UUID of a pipeline, execution, or widget on a dashboard.
  • Input parameter, Output parameter, and Status message notation and examples include:
    • Notation: input.<inputKey>:<inputValue>

      Example: input.GERRIT_CHANGE_OWNER_EMAIL:joe_user

    • Notation: output.<outputKey>:<outputValue>

      Example: output.BuildNo:29

    • Notation: statusMessage:<value>

      Example: statusMessage:Execution failed

  • Status or state depends on the search page.
    • For executions, possible values include: completed, failed, rollback_failed, or canceled.
    • For pipelines, possible state values include: enabled, disabled, or released.
    • For triggers, possible status values include: enabled or disabled.
  • Executed, Created, or Updated by me refers to me, the logged in user.
Search appears at the upper right of every valid page. When you start typing into the search blank, Code Stream knows the context of the page and suggests options for the search.
Methods you can use to search How to enter it
Type a portion of the search parameter.

For example, to add a status filter that lists all the enabled pipelines, type ena.


To display the enabled pipelines, in the Search area, enter "ena", and select Status:Enabled.
To reduce the number of items found, add a filter.

For example, to add a name filter type Tes. The filter works as an AND with the existing Status:disabled filter and only displays the disabled pipelines that have Tes in the name.

When you add another filter, the remaining options appear: Name, Description, Tags, Link, Project, and Updated by.


To reduce the search results, enter several letters in the Search area, such as Tes, and click one of the options that appear.
To reduce the number of items displayed, click the filter icon on properties of a pipeline or a pipeline execution.
  • For pipelines, Status, Tags, Project, and Updated by each have a filter icon.
  • For executions, Tags, Executed by, and Status Message each have a filter icon.

For example on the pipeline card, click the icon to add the filter for the SmartTemplate tag to the existing filters for: Status:Enabled, Project:test, Updated by:user and Tags:Canary.

Search Filters on Pipeline card
Use a comma separator to include all items in two execution states.

For example, type fa,can to create a status filter that works as an OR to list all failed or canceled executions.


Search OR
Type a number to include all items within an index range.

For example, type 35 and select < to list all executions with an index number less than 35.


Search Index with operator
Pipelines that are modeled as tasks become nested executions and are not listed with all executions by default.

To show nested executions, type nested and select the Show filter.


Search Nested Executions

How do I save a favorite search

You can save favorite searches to use on each page by clicking the disk icon next to the search area.

  • You save a search by typing the parameters for search and clicking the icon to give the search a name such as my enabled.
  • After saving a search, you click the icon to access the search. You can also select Manage to rename, delete, or move the search in the list of saved searches.

    Saved Search

Searches are tied to your user name and only appear on the pages for which the search applies. For example, if you saved a search named my enabled for Status:enabled on the pipelines page, the my enabled search is not available on the Gerrit triggers page, even though Status:enabled is a valid search for a trigger.

Can I save a favorite pipeline

If you have a favorite pipeline or dashboard, you can pin it so that it always appears at the top of your pipelines or dashboards page. On the pipeline card, click Actions > Pin.

Pin pipeline to top of display