-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem starting analysis #96
Comments
It looks like deeptracy cannot stop containers in your computer:
A quick search brought me to this answer: https://stackoverflow.com/questions/49104733/docker-on-ubuntu-16-04-error-when-killing-container Maybe AppArmor is stopping us from stopping the container. Please try the solutions given in the StackOverflow answer and let me know if that help. |
Also, are you sure the hostname stash can be resolved inside your container? |
After disable apparmor, kill the existing docker instances and then reload the deeptracy, the exception disappears. But I stay with the other problem, I can't checkout the repo inside the docker. If I try to connect to stash from the docker I'm able to reach that (deeptracy_deeptracy-worker_1):
|
Could you please access the buildbot access panel under: http://localhost:8010/, Access the build with the same name as your repository URL and take an screenshot of the steps, please. Also, could you please send an analysis of the URL: https://github.com/nilp0inter/gitsectest with the commit a5a01ca69ac99c793ec5af1bbc190f518d8fc412 ? |
You were right.
So.. do you overwrite the DNS of the machine? If I point to the IP of the stash server I works as spected (Now I have a problem with my project but I¡ll try to fix It to test again). I would like to report a problem with buildbot. I'm accessing with the Ip of my VM, but when I navigate through buildboot gui I get redirected to "localhost". I attached the image that shows where it happens: |
I am not overwriting the DNS settings, but maybe Buildbot/Docker are. To stop buildbot redirecting you to localhost there are a few environment variables you can change under the environment section of the deeptracy-buildbot definition in the docker-compose file. I think the correct variable is BUILDBOT_WEB_URL. You can check the list of allowed variables and default values here: deeptracy/deeptracy/buildbot/master.cfg Lines 26 to 58 in e5e7e0e
|
Thanks for this information, I corrected some problems the pom location and then I got the following error:
That's how my project looks like:
|
That is very interesting, could you share the pom or at least the list of dependencies contained in it? |
Of course that's my pom.xml
|
Hi @Berni69 , I've just uploaded a patch that should solve your problem. Please download the latest version and rebuild your containers with 'make' to test it out. Cheers, |
Hi @nilp0inter, now It seems that it passed from this point, but during the analysis I'm seeing this exception (in buildbot I can't see errors) in the container log:
I have another question, is there any way to set an ssh key to access private repositories? |
You can safely ignore the InvalidSignatureError; nevertheless I opened a ticket to try to fix it. Regarding your other question, buildbot support ssh keys directly and through secret managers but at the moment deeptracy has no method of pass it to buildbot. http://docs.buildbot.net/current/manual/cfg-buildsteps.html?highlight=sshprivatekey#git You can modify the Git steps on the master.cfg file to specify your custom SSH keys. If you have any suggestions on what is the best way of implementing it please open another ticket to discuss it. Thank you for your reports! |
Hi everyone,
I've just followed the installation docs of the new version of deeptracy (on a fresh install of ubuntu server 18.04), I prepared a demo repo with this configuration (.deeptracy.yml):
But when I ran this call:
I saw in the logs this error:
If I do a git clone outside the docker I'm able to do a clone without problems (no credentials are required):
Could you help me with this issue?
Thanks for your time
The text was updated successfully, but these errors were encountered: