Pipeline for release and updated tests

[miguelgfierro]

Description

Details #1408

Related Issues

Checklist:

• I have followed the contribution guidelines and code style for this project.
• I have added tests covering my contributions.
• I have updated the documentation accordingly.
• This PR is being made to staging branch and not to main branch.

[miguelgfierro]

yeah, that is defined in the build pipeline, it looks like clean is not set to true (at least for this pipeline). You will need to edit the pipeline -> triggers -> yaml -> get sources -> clean -> set to true
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git?view=azure-devops&tabs=yaml

do you know if this is something that we can add in the yaml file directly?

[gramhagen]

yeah, that is defined in the build pipeline, it looks like clean is not set to true (at least for this pipeline). You will need to edit the pipeline -> triggers -> yaml -> get sources -> clean -> set to true
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git?view=azure-devops&tabs=yaml

do you know if this is something that we can add in the yaml file directly?

yes, in the documentation listed you can either add a checkout step, or use the workspace setting for any job

[anargyri]

Excellent work @miguelgfierro, you are now officially the master of build pipelines!

[gramhagen]

most of my comments are questions so I can better understand how things work, maybe we should set up some time to talk this through, i don't think any of them should block this.

it would be nice though to add a readme that explains how the release process works, it looks like we need to tag a release starting with 0. or 1. and then some artifacts are pushed to github, then we manually upload them to pypi?