erioshi
erioshi
As noted above I linked the issue I reported to this one as it looks to be related. Unfortunately in my case, using http along with a PAT also returned...
It looks like my issue may be related to a prior issue already tagged as a bug: https://github.com/ansible-semaphore/semaphore/issues/871 Someone there mentioned using a PAT as a work-around, but that also...
This issue also looks to be related: https://github.com/ansible-semaphore/semaphore/issues/910
As part of testing I built a fresh container using gitea instead of GiBucket as a git repository. With gitea as the repo I was able to complete the clone...
I'm thinking I may build a VM and see if the VM has the same issue as the container. No reason to expect different behavior, but it is probably worth...
I did just re-try all of this with a pull of the development container, and that failed as well. I also turned on the debug flag and that added a...
Thank you for that info. I also tried the "develop" tagged version of the container and had the same failure.
Interestingly DesireWithin had success connecting to an HTTPs GitLab repository. He provided that update in the issue reference above. He did not specify if the GitLab instance was the public...
Yes, vault-id can be assigned, but it seems to be once per run unless you were to find a method that could redefine the value of a specific Semaphore variable...