Skip to content

Post-rollout task logs are not available until deployment is complete #417

Open

Description

@rocketeerbkw

If a post-rollout task takes a long time, a user might not know if it's still running or if something failed. One task took longer than an hour because it was doing filesystem mutations. The task itself was showing that it was processing, but those logs were never visible to users.

Activity

  1. weitzman commented on Sep 9, 2026

    @weitzman

    Yes, this is sorely lacking compared to Github Actions, Gitlab Pipelines, etc.

  2. rocketeerbkw commented on Sep 9, 2026

    @rocketeerbkw
    MemberAuthor

    The alternative solution, implied by the mentioned issue, is to use the lagoon cli to follow the deployment logs (in real-time), which should include post-rollout tasks as well: lagoon logs --project drupal-example --environment main --follow --build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions