Hi Michael,
I think the simple answer is that LAVA only supports git repositories without passwords. I think it might be possible to store the credentials in git global config on the dispatcher, but I haven't tried this. Under the hood the usual git client is used. If there is a way to configure credential manager for git not to ask any interactive questions, this might work.
Best Regards, Milosz
On Wed, Jan 24, 2024 at 10:34 PM michael.peddie@gallagher.com wrote:
Hi,
As stated in the subject, I was wondering if it is at all possible to use a repo on Azure DevOps instead of a GitHub one. I have been using a GitHub repo thus far, and it works just fine, but I need to move my files over to DevOps.
According to the docs here: https://docs.lavasoftware.org/lava/actions-test.html only git is supported at the moment, with URL and tar planned for. Would URL work for this if support came in at any point? Or would azure need its own support?
Or should git work and there is something wrong with the repo URL I am using? Because the particular error I get is that the password could not be read (I'm using a PAT in the link, like I did for GitHub)
Best Regards. Michael _______________________________________________ lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s