-
Task
-
Resolution: Duplicate
-
Critical
-
-
1.0
The ATH runs with security turned off right now for historical reasons.
This is not a recommended configuration and prevents it from testing things like:
- Personalization
- Creation
- Permissions
The ATH should be able to run tests as a logged in user (or different users with different permissions).
cc imeredith
- blocks
-
JENKINS-41434 Restrict access to Creation Flow for users with insufficient permissions
-
- Resolved
-
-
JENKINS-36641 End to end test acceptance tests for personalization
-
- Resolved
-
[JENKINS-42354] ATH must support users and run logged in where needed
Rank | New: Ranked higher |
Epic Link | New: JENKINS-35749 [ 171790 ] |
Link |
New:
This issue blocks |
Sprint | New: 1.1 [ 251 ] |
Priority | Original: Critical [ 2 ] | New: Blocker [ 1 ] |
Rank | New: Ranked higher |
Assignee | New: Ivan Meredith [ imeredith ] |
Priority | Original: Blocker [ 1 ] | New: Critical [ 2 ] |
I had previously suggested that perhaps we could use a custom subclass of LocalController to set up a Jenkins home with the appropriate configuration. However imeredith made what might be a better suggestion which is that this could be set up via a plugin that's bundled with the Jenkins deployed by ATH. I'm not knowledgeable enough to enumerate the pros and cons though.