Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retention policy isn't returning runsToRetainPerProtectedBranch #597

Open
bsmithb2 opened this issue May 28, 2024 · 3 comments
Open

Retention policy isn't returning runsToRetainPerProtectedBranch #597

bsmithb2 opened this issue May 28, 2024 · 3 comments

Comments

@bsmithb2
Copy link

Environment

Node version: v21.7.3
Npm version: 10.5.0
OS and version: MacOS Sonoma 14.4.1
azure-devops-node-api version: 12.5.0

Issue Description

When attempting to use IBuildApi.getRetentionSettings(), the value for runsToRetainPerProtectedBranch is null

Expected behaviour

It should be a RetentionSetting object

Actual behaviour

The RetentionSetting object is null

Steps to reproduce

  1. Create a IBuildApi object connected to an Azure Devops server
  2. call getRetentionSettings() on that project
  3. Note the runsToRetainPerProtectedBranch object is null but the other options are not.

Logs

JSON object representation for example
{"purgeArtifacts":{"min":1,"max":60,"value":30},"purgePullRequestRuns":{"min":1,"max":30,"value":10},"purgeRuns":{"min":30,"max":731,"value":30},"retainRunsPerProtectedBranch":null}

@KonstantinTyukalov
Copy link
Contributor

hi @bsmithb2 thanks for the reporting! We are working on higher priority issues, but we'll get back to this one soon.

Copy link

This issue has had no activity in 90 days. Please comment if it is not actually stale

@github-actions github-actions bot added the stale label Aug 28, 2024
@bsmith-bupa
Copy link

it's not stale

@github-actions github-actions bot removed the stale label Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants