edgexfoundry / edgexfoundry/cd-management

Make edgeXReleaseOpenApi idempotent. Build errors occur upon releasing the same release.yaml file.

Open
#322 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
6
Forks
16
PR merge metrics
No merged PRs in 30d

Description

# 🚀 Feature Request

### Relevant Package [**REQUIRED**]

This feature request is for...

### Description [**REQUIRED**]
A clear and concise description of the problem or missing capability...
This release build job fails:
https://jenkins.edgexfoundry.org/blue/organizations/jenkins/edgexfoundry%2Fcd-management/detail/release/134/pipeline/550

```
apiInfo:
nextReleaseVersion: '2.4.0'
reviewers: edgexfoundry/device-sdk-go-committers
```

### Describe the solution you'd like
If you have a solution in mind, please describe it.
This release yaml for device-sdk-go was released in Nov 2022 but was a new version was released in Mar 2023. The apiInfo in the release yaml didn't change. I think the release automation should allow this as a valid use case and not fail the build.

### Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.