Bug 442143 - Gerrit Trigger Fails Authentication on Manual Trigger
Summary: Gerrit Trigger Fails Authentication on Manual Trigger
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Plugins (show other bugs)
Version: 3.2.0   Edit
Hardware: PC Linux
: P3 normal with 12 votes (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA Friend
QA Contact: Geoff Waymark CLA Friend
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-20 05:00 EDT by Dan Paulat CLA Friend
Modified: 2014-10-29 13:17 EDT (History)
5 users (show)

See Also:


Attachments
Gerrit Manual Trigger Stack Trace (6.28 KB, text/plain)
2014-08-20 05:00 EDT, Dan Paulat CLA Friend
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Paulat CLA Friend 2014-08-20 05:00:50 EDT
Created attachment 246157 [details]
Gerrit Manual Trigger Stack Trace

Overview:
After the upgrade of Hudson to version 3.2.0, I can no longer trigger a Gerrit event manually (automatically still works fine).

Hudson: 3.2.0
Gerrit Plugin: 0.7
Gerrit Trigger: 2.5.3-h-1

Steps to reproduce:
- From the main menu, press "Query and Trigger Gerrit Patches"
- Enter a valid query string, and press "Search"
- Select a patch set to trigger, and click "Trigger Selected"

Expected results:
Gerrit event is triggered, and job starts, just as if it were triggered automatically

Actual results:
HTTP ERROR 500
Problem accessing /hudson/gerrit_manual_trigger/build. Reason:
    hudson.model.Hudson.getAuthentication()Lorg/springframework/security/Authentication;

Full stack trace is attached.

Additional Information:
I saw in the release notes for Hudson 3.2.0 that Spring libraries were upgraded to Spring 3.  Perhaps this is related?