Skip to content
This repository was archived by the owner on May 8, 2023. It is now read-only.
This repository was archived by the owner on May 8, 2023. It is now read-only.

When using Gated Check Ins with Azure DevOps, Build Information(work items and commits) do not get submitted to Octopus. #18

Open
@millerjn21

Description

@millerjn21

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

When using Gated Check Ins with Azure DevOps, Build Information(work items and commits) do not get submitted to Octopus.

What I expected to happen

Work items and commits to get submitted to Octopus

Steps to reproduce

  1. Create a pipeline on ADO that is a gated Check in with push build info and create release at the end.
  2. Ensure there are work items and commits for the build
  3. Start build and let it finish
  4. See there is no build information within the release in Octopus

Screen capture

N/A

Log excerpt

N/A

Affected versions

Octopus Server: 2020.5.5 (latest at time of writing)

Workarounds

Use the legacy option in create release step instead of the push build info step.

Links

Source ticket(internal): https://octopus.zendesk.com/agent/tickets/63717

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions