Comments
2 comments
-
Hello JesusB,
Is the Path environmental variable a user one or a system one please?
The execution context (your user and the build agent account) may be different, which could account for the difference. -
Have you restarted the Azure pipeline service since you set up Flyway?
I just ran into this myself in Azure DevOps. Agent service was up, I added the Flyway key, and ADO just refused to read it even though it was clearly and correctly set in the system PATH environment variable. I just had to open Services and restart the corresponding Azure Pipeline Agent service.
Add comment
Please sign in to leave a comment.
I am able to run flyway on the terminal in the build agent computer but not through Azure.
I set the PATH variable to C:\Flyway\flyway-9.17.0\.
I've attached the flyway.conf file and logs from the run.