| Summary: | wrong path configured for Hudson Buckminster plug-in | ||
|---|---|---|---|
| Product: | Community | Reporter: | Nicolas Bros <nicolas.bros> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Nicolas Bros
Well according to Hudson Headless Buckminster 3.6 already points to /opt/public/common/buckminster-3.6 , so I'm not sure where it's getting the '-stable' suffix from. And I confirmed that the plugins directory is there. -M. In fact, it works on the master but fails on the slave. Could you check the Buckminster path defined for the Hudson slave? I've updated the slave config. Based on what I see it looks like the Buckminster integration settings pointed at the stable version. -M. It works now, marking fixed. |