We are running into an issue implementing Liquibase on our ADO Windows Release agents. We are able to run Liquibase on the agent host machine - but due to relative paths it is failing on the agents themselves. Liquibase is installed on the OS drive (C:) and individual agent workspace folders are on a different drive (E:). The agents are going to roll out updates to multiple databases in several different environments.
The thought is to pull a zip artifact that contains changelog and scripts for the specific database/environment and expand in the agent workspace for use by Liquibase. The relative path requirement is making it difficult. Any ideas?