Skip to content

Simplify CI/CD layer for easier adoption by the LabVIEW community #4

@svelderrainruiz

Description

@svelderrainruiz

Is your feature request related to a problem? Please describe.
On a design review i had with Nikolaus Naredi-Rainer, it was brought to my attention that the multi platform approach for CI/CD is too complex for the LabVIEW community to replicate.

Describe the solution you'd like
Deprecate the approach that makes a github action to trigger and poll an azure devops pipeline, and instead use only a github action.

Describe alternatives you've considered
Current alternative is a github action triggering an azure devops pipeline that polls the pipeline status.

Additional context
The current multi-layered approach for CI/CD (layer 1 is Azure, layer 2 is Github action) was made because NI uses Azure to build, and i wanted to make sure to maintain the order of operations on a single location, therefore it seemed like a good idea to not duplicate the process on 2 places (azure and github action). This process was too complex since i am just experimenting with CI/CD and it is quite simple to fall into a rabbit hole like the current approach on the repo.

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions