Versions Compared

Old Version 2

changes.mady.by.user Ben Hoffman

Saved on

compared with

New Version Current

changes.mady.by.user Joel Wenzel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Environment History report provides visibility into the history of all deployments activities across the topology of environments and instances. This report is helpful in determining what may have happened with a given project that might be having issues. To run the report, optionally select a Project Name, Environment, Instance, Package Name, File Path and if the report should represent Partial Deployments only and click the Search button.
Image Removedfilter the report, use Basic or Advanced mode. You can view activities at individual file or project/package level, use Show File Level Details checkbox.

Report will initialize to Basic mode with activity details from past 3 months without file level details.

Info
titleResult table details

Path is

  • Fully qualified application name

Ref #

  • S - for pipeline stage execution and stage execution id
  • P - for project request and workflow request id
  • A - for application request and folder request id

Release and Snapshot

  • Only present if deployment was done using Release

Change Ticket

  • Only present if Change Management System integration is used for deployments and change ticket is used for deployments.

Issue Number

  • Only present if Issue Tracking System integration is used and build captured issue numbers.

File level details

  • File level details for partial deployment project is only shown if Show File Level Details is checked, otherwise package level activities are displayed.

Basic Search

Search FieldSearch OperatorNotes
EnvironmentEqualsConfigured Active Environments
InstanceEqualsConfigured Active Instances
StatusEqualsAborted, Failure, Queued, Running, Scheduled, Success
Workflow TypeEqualsBuild, Deploy, Utility, Test, Other, Test Definition
Requested OnAfter, Before or Between

Task requested time

Depending on whether first, second or both values are provided respectively

ReleaseContains Ignore Case

Release name, suggestions are provided as you type

You can use partial or full Release name.

Image Added

Advanced Search

Search FieldSearch OperatorNotes
EnvironmentEqualsConfigured Active Environments
InstanceEqualsConfigured Active Instances
StatusEqualsAborted, Failure, Queued, Running, Scheduled, Success
Workflow TypeEqualsBuild, Deploy, Utility, Test, Other, Test Definition
Requested OnAfter, Before or Between

Task requested time

Depending on whether first, second or both values are provided respectively

ReleaseContains Ignore Case

Release name, suggestions are provided as you type

You can use partial or full Release name.

Ref #EqualsSearch for Project, Application or Pipeline Stage Execution id
Project NameContains Ignore CaseProject Name
Start TimeAfter, Before or Between

Execution start time

Depending on whether first, second or both values are provided respectively

End TimeAfter, Before or Between

Execution end time

Depending on whether first, second or both values are provided respectively

Package NameEqualsPackage name, only applicable for partial deployment projects
Requested ByEqualsexact user name of person that requested execution
SCM RevisionEqualsRevision associated with project version or specific file (if showing file level details)
Change TicketEqualsChange ticket associated with deploy or utility execution
Issue NumberEqualsIssue numbers associated with project version
Build Request FlexfieldsEquals

Depends on configured active and visible Build Request Flexfields

Only applies to project and application executions

Deploy Request FlexfieldsEquals

Depends on configured active and visible Deploy Request Flexfields

Only applies to project and application executions

Image Added

Tip

The reference number (Ref #) in the first column can be used to correlate data across reports. It refers to the project, application, or stage execution identification number.