Skip to main content

Workflow Logs

The workflow logs module automates CI/CD pipeline creation for application services upon environment deployment. It provides a detailed overview of each workflow step, including branch and commit information about the pipeline, the user who made the push, and the current status of the workflow. This module is crucial for monitoring and managing the continuous integration and deployment of your projects.

Accessing Pipelines​

Navigate to the Workflow Logs module from Atmosly's left side menu. Here, you can view all pipelines related to your workflows. Use the filtering options to quickly find specific pipelines by project name, environment, workflow, or status.

Understanding Pipeline Information​

Each pipeline entry provides:

  • Branch: The branch that triggered the pipeline.
  • Commit Details: Commit ID and message for context.
  • User: Who pushed the commit.
  • Status: Current state of the pipeline (e.g., running, failed, successful, pending approval, etc.).

Build Details​

The Build Details section includes a visual representation of the pipeline workflow. This visualization highlights each stage, including source, build, deploy, and tools integrated in the pipeline. Users can monitor the progress of each step and take necessary actions like restarting or retriggering specific stages.

  1. Viewing Workflow Stages: Click on any stage within the Build Details view to get more information or start/restart a particular step if required.
  2. Retriggering a Stage: To address issues or rerun a specific stage, click on the corresponding "Restart" button next to the stage.

Build Logs​

In the Build Logs section, users can access detailed logs for each workflow step. This section displays:

  • Log Type: Whether it pertains to app CI or another process.
  • Timestamp: The exact time the logs were generated.
  • Log Details: A preview of the log entries, with color-coded lines indicating different statuses (e.g., errors in red).

Users can download the full log file for in-depth analysis by clicking on the "Download Report" link.

Reports​

The Reports section provides detailed summaries of each pipeline's execution, including:

  • Execution ID: A unique identifier for each pipeline run.
  • Triggered At: When the pipeline was triggered.
  • Trigger Type: Whether the trigger was manual, scheduled, or event-based.
  • Tool: The tool used during the stage (e.g., Trivy Scan).
  • Stage: The specific stage (e.g., Pre-Build).
  • Report Link: A downloadable link for the detailed report of the pipeline's execution.

Approving a Manual Step​

For pipelines that require manual approval at certain stages, you will see the step which requires Manual approval, from the Manual tag at the concerned stage. Click on 'Start' at the bottom of the card to continue the workflow.

For example, if the Source stage requires a manual approval, you will see 'Start Build' udner the source stage. Click on the same to continue the workflow.

Troubleshooting​

In case of a failed pipeline please contact support at contact@atmosly.com with detailed information about the problem.