Changes between Initial Version and Version 2 of Ticket #449
- Timestamp:
- Mar 20, 2017, 10:16:13 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #449
- Property Status changed from new to closed
- Property Resolution changed from to fixed
-
Ticket #449 – Description
initial v2 1 To fully integrate Jenkins (running on orxonox. info:8080) in our website, it would be good if we can make it available on port 80/443. I don't know what works best, but in general I'd like to have one of these options:1 To fully integrate Jenkins (running on orxonox.net:8080) in our website, it would be good if we can make it available on port 80/443. I don't know what works best, but in general I'd like to have one of these options: 2 2 3 * orxonox. info/build4 * orxonox. info/jenkins5 * build.orxonox. info6 * jenkins.orxonox. info3 * orxonox.net/build 4 * orxonox.net/jenkins 5 * build.orxonox.net 6 * jenkins.orxonox.net 7 7 8 Note: I don't want a browser forwarding to orxonox. info:8080. It should be fully accessible under the standard http(s) port because in some places (e.g. here at work) port 8080 is blocked.8 Note: I don't want a browser forwarding to orxonox.net:8080. It should be fully accessible under the standard http(s) port because in some places (e.g. here at work) port 8080 is blocked. 9 9 10 10 Do you think that's possible?