-
Notifications
You must be signed in to change notification settings - Fork 81
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
Wont install ruby-runtime 0.12 #19
Comments
I suspect this might be the issue. |
Been trying a restart. I will try the c: and let you know |
Wow....finally success...this is such a ridiculous bug! |
So just to verify, the path with spaces was the cause? |
Yes. I really appreciate the prompt response. This tool is awesome! One question I have for you is, I noticed that during a post it only sends the master branch. Do you know why that is? I want to setup development with different branches then production. |
The Gitlab payload has the brach related to the commit. |
Ah I get it now! So when the commit goes through you see the commit for that specific branch. Is there any way to actually test that out in GitLab WebHook Test Section? |
Nah, best way is to just create a test project at Gitlab and Jenkins and play around. |
Figured as much. Thanks again! |
Sure :-) |
And i can confirm that this is still an issue in jenkins when trying to install ruby-runtime.
Installing Jenkins in the root of the c drive solved the issue and ruby-runtime could then be installed.
|
@tlogik thanks for the feedback! |
Thanks @elvanja |
Are you F*in kidding me? So this tool can't deal with spaces. WTF? |
this fix works for me : https://stackoverflow.com/questions/44403642/jenkins-plugin-installation-failing |
help me overcome this issue indetale |
had the same issue. |
I too was able to resolve this my simply moving Jenkins to C:\Jenkins. Don't forget to change any environment variables, etc... when you do so as well though. |
Ahh, I tried this and now I cannot connect to my Jenkins from remote (calling 192.168.xx.xx:8080 produces a timeout), locally / on that machine localhost:8080 works, but tells me that my reverse proxy configuration is wrong, which I definitely didn't set... I scanned the config and settings in the Jenkins folder, but I do not find what is going wrong. Any ideas? Help really appreciated. Forget the question - somehow the windows firewall re-emerged... D'uh! |
Had the same issue and moving Jenkins to c:\Jenkins solved it |
I know this isn't related to this but the pre reqs require it so I am not sure if I am missing something or doing it wrong...
This is what I get:
I am using jenkins v 1.538
The text was updated successfully, but these errors were encountered: