-
Notifications
You must be signed in to change notification settings - Fork 23
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
Gitweb links broken #33
Comments
Hi @patrickvinas, Looking into the issue. What happens if you manually copy and paste the url in the browser? does it resolve? I see the same format in our URLs. However, the link resolves and shows the changes in gitweb. Ex: If I remove the slash, chrome will add it back when i enter the selected url without it. Are you proxying through apache? Judging by the port, you're running directly from tomcat? Could it possible be a context path/docbase setting in your server.xml? |
If I copy and paste into the browser, it gives a 404 error. The commit In your example the query string starts immediately after the hostname and so requires a slash. Our path includes a page name before the query string, which, if I recall correctly, would not require a slash (or perhaps explicitly requires there to not be a slash). |
I'm seeing the same exact issue. I tried removing gitweb suffix from the URL and putting it as the Repository Path, but that didn't do anything that I can see. |
Hi scholarsmate, does the same URL work in the browser? What is the difference between the URL that works in the browser and the link provided from Bamboo? |
I don't think that it is necessary to have / before query string. |
In the Build Summary tab, the gitweb links to the commits are broken - it is generating links like "https://gerrit1:8443/gitweb/?p=devrepo/repo.git;a=commit; h=7e384362c24d121e0c9ba20e8b48cc6006e8c13b" (notice the extraneous slash between gitweb and ?p). I've verified that I didn't do something silly like add a trailing slash in the gitweb URL in the plan config. Is anyone else seeing this issue? This is with Bamboo 5.7.2 and gReview 1.4.4.1
The text was updated successfully, but these errors were encountered: