Skip to content

Conversation

svelderrainruiz
Copy link
Collaborator

No description provided.

…ding on the pipeline thatn the one used locally.
# Conflicts:
#	azure-pipelines.yml
…ns were setting the agent into an error state needing for manual intervention.
…rovide meaningful feedback"

This reverts commit 033ebbb.
instead of doing it while on th eprocess of building the VI package, i do it to both labview bitnesses in the beginning.
This way i avoid closing labview executions and risking the next process to lose the handle, we now open a labview bitness once, and close it once.
@svelderrainruiz svelderrainruiz marked this pull request as ready for review December 5, 2024 02:06
Ensures that the agent is set to the same state it was before executing the pipeline, since the process itself zips vi.lib\LabVIEW Icon API\* and sets localhost.librarypath to your working folder.
@svelderrainruiz svelderrainruiz marked this pull request as draft December 5, 2024 03:28
@svelderrainruiz svelderrainruiz marked this pull request as ready for review December 5, 2024 03:33
@svelderrainruiz svelderrainruiz merged commit 7529953 into develop Dec 5, 2024
1 check was pending
@svelderrainruiz svelderrainruiz deleted the feature/85-powershell-azure-integration branch March 18, 2025 14:49
svelderrainruiz added a commit that referenced this pull request Aug 6, 2025
## Summary
- clarify that direct pushes retain the previous version and only
increment the build number in CI workflow docs

## Testing
- `python -m pytest`

------
https://chatgpt.com/codex/tasks/task_e_6893d6bfa01c8329b68d34fb37d31a24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Integrate calling powershell build script from azure devops pipeline feature/powershell-build-automation

1 participant