Details
-
Type:
Improvement
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: jenkins
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:TSSW Sprint - Jun 22 - Jul 6
-
Team:Telescope and Site
Description
The T&S Jenkins system https://tssw-ci.lsst.org/ gives a 404 error if one tries to go to a link and one's login has expired. This is a headache when trying to see the status of a job started on github, or even just visit a frequently-wanted page such as https://tssw-ci.lsst.org/job/LSST_Telescope-and-Site. I have to open a new browser to https://tssw-ci.lsst.org, log in there, wait for that to complete, and only then can I go to the other page and try the link again.
Please if at all possible enable login when visiting any page. Also please consider a longer time limit on login or some way to "remember this browser" (for those of us on secure computers, e.g. desktops).
Attachments
Activity
As a workaround, you can Enable Auto Refresh on an active Jenkins tab and that will maintain your session. I understand this isn't ideal, but it is hopefully temporary.
Additionally, it seems like you don't have a Jenkins window open all the time, so what do you feel is a reasonable session timeout?
I looked at that other ticket and if I read it right it is only related to the timeout, not the 404 error, which is to me is far more important. If I try to visit a link I'd like it to let me log in, instead of claiming the page does not exist. This would make links in github tickets work much better. Right now they simply appear to be broken unless you know the trick: visit https://tssw-ci.lsst.org/ and press the "login" button and wait for login, then suddenly the other link works.
But for timeouts: I'd be glad of a few hours or a day would be quite helpful, because once problems show up the odds are I may have to look at Jenkins multiple times, and my Jenkins runs typically take a long time.
If the 404 issue is hard to solve, an alternative to consider is to allow read-only access without authenticating. Then the link would open and that might be all most users need.
This turned out to be a Jenkins configuration issue, and not a web-host issue. According to this issue, found by IT, https://issues.jenkins-ci.org/browse/JENKINS-4740, there is a setting that controls whether unauthenticated users can "Discover" jobs. Once checked, logged out users that click a job-related link (console output, status, etc) automatically get logged in and navigated to the desired link location.
It works. It's great!
This is already a known issue and it is being worked: https://jira.lsstcorp.org/browse/IHS-3389