@atripp One additionally thing to mention. I tested this also with the test repository i given to you. This repository i was able to clone, but not others.

What i have found out: There is a bug in your implementation, which leads to the error given in my last reply:

If the repository name contains a dot (.) for example a repository with name: image.kubernetes-test

You'll get this error. So i think url or content encoding is not done the right way. I tried to rename one repository from: image.kubernetes-test to image-kubernetes-test and voila... That worked. So, maybe you can fix this too, so your implementation is usable for all valid repository names

@atripp I was full of hope. Bute error messages are getting stranger than before.
Now we have: Unable to clone repository: HashDelta is not supported unless a repository is available.
:-(

For sure. I tested it directly. Unfortunately this produces a 400 BadRequest error. So for first it seems to have no ssl problems. Too bad. One additional thing to mention which confused me a little bit: You allow to configure to access the azure devops via a PAT. If you use a PAT, then a username is obsolete, as the azure devops documentation says you should use a Basic Authorization to access the server which should be a base 64 encoded string create from "USERNAME:PAT" where USERNAME should be left empty. But in your UI the Username is a required field, which then for me doesn't make sense. Also to mention: If you ignore this and pass the username along with the pat, a git clone for example with this basic authorization also fails. Maybe it could be the case you did that wrong. But this would be strange, as you told me you don't have these issues. Or maybe you're testing against the cloud AzureDevopsServices. We are talking here about a on premise Azure Devops Server installation. Maybe their authorization mechs differs... Just some thoughts...

@stevedennis said in Buildmaster fresh install / Unable to clone repository:

[QA-2678]

Yes, perfect. I have sended the email with the subject [QA-2678] Additional informations
a few seconds ago... Hope to hear from you

Hello. As you suggested i tried it with github. No issues there. But as you said it could be a problem with SSL i reconfigured the azure devops server to allow also http and disabled the redirect to https. Just to check if the issue then still exists. And the result: Even if you use pure http for the azure devops server you get the ssl error, which is very strange. Also tested this with another azure devops server at another site. Same problem there. Just to mention: The url i am using in buildmaster directly goes to the azure devops server, so there is no reverse proxy or something like this in between. Maybe you can reproduce the issue if i give you the azure devops url of my site. It's reachable for public. I created a test user and repository for you and created a personal access token, so you are able to reproduce the error at your site. Just give me a note where i can send you the credential informations so you can test it

@stevedennis said in Buildmaster fresh install / Unable to clone repository:

libssl

Thanks for answering quickly. First i had this issue testing buildmaster on a default docker installation running on ubuntu 24.04.2 LTS with docker 27.5.1. I had to put the topic aside for some time and now coming back to evaluate buildmaster. As i now have a kubernetes cluster available my first idea was to simply switch over to kubernetes and try it out again, but there the same issue arrived. Still the same error message. Buildmaster is now running on MicroK8s 1.32.3, default install, no additional security software installed on that host. The strange thing here is when adding a new connection to azure devops and entering the instance url, username and personal access token, i am able to browse the projects and repositories in the buildmaster setup dialog. I mean, i can see all the projects and repositories which are available at the azure devops server, so the connection should be already established. I've checked multiple times the personal access token and also created a new one, but still no luck. Also tried to set the minimum log level of buildmaster to 0 which seems to be debug, but no usable output is shown. Tell me if you need more informations

Tried exactly that version, but the same error shows up. Wondering that you've never fixed this in the product. Seems to be not widely used, right?

Used docker image: buildmaster:latest

When trying to create a new application and choose azure devops repository i am able to browse projects and repositories, afterwards an error occurs:

Unable to clone repository: could not set credentials: could not open libssl

Username and personal access token setted, also ssl verification turned off, but still no luck.

Any chances to resolve this issue?