[JIRA] [core] (JENKINS-31307) Wrong redirects when behind reverse proxy

2015-10-30 Thread feder...@fsfe.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Fissore created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31307 
 
 
 
  Wrong redirects when behind reverse proxy  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 jenkins.conf, jenkins.redirects.txt 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 30/Oct/15 8:53 AM 
 
 
 

Environment:
 

 debian wheezy, nginx 1.8.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Federico Fissore 
 
 
 
 
 
 
 
 
 
 
I've setup jenkins behind a reverse proxy with nginx. ALMOST everything works. Here is a list of what doesn't, though that may be incomplete 
 

accessing "manage plugins" (see attached jenkins.redirects.txt). Although the url is correct (http://jenkins:9090/pluginManager) browser receives a 302 to http://jenkins/pluginManager. If then I manually change the url to http://jenkins:9090/pluginManager, I can access Manage Plugins
 

  

[JIRA] [copy-to-slave] (JENKINS-23043) Build hangs while copying artifacts to slave

2014-05-19 Thread feder...@fsfe.org (JIRA)














































Federico Fissore
 commented on  JENKINS-23043


Build hangs while copying artifacts to slave















Have you found any workaround?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-17049) Xvnc -localhost -nolisten tcp should be configurable

2013-03-07 Thread feder...@fsfe.org (JIRA)














































Federico Fissore
 commented on  JENKINS-17049


Xvnc -localhost -nolisten tcp should be configurable















soo easy! thank you very much: I confirm it works like a charm!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-17049) Xvnc -localhost -nolisten tcp should be configurable

2013-03-05 Thread feder...@fsfe.org (JIRA)














































Federico Fissore
 commented on  JENKINS-17049


Xvnc -localhost -nolisten tcp should be configurable















If for "screenshots" you intend "videos" then it answers my needs but introduces an overhead that may no be acceptable. In my case I needed to see the application running because the glitch that caused the build to fail showed just for a moment.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-17049) Xvnc -localhost -nolisten tcp should be configurable

2013-03-04 Thread feder...@fsfe.org (JIRA)














































Federico Fissore
 created  JENKINS-17049


Xvnc -localhost -nolisten tcp should be configurable















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


xvnc



Created:


04/Mar/13 1:47 PM



Description:


"-localhost -nolisten tcp" prevent seeing a problem occurring when it affects the test environment set up on jenkins: reproducing it locally and blindly can take hours
"-localhost -nolisten tcp" should be configurable, enabled by default 




Project:


Jenkins



Labels:


plugin
configuration




Priority:


Major



Reporter:


Federico Fissore

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.