| Key: |
CIB-1162
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
jason
|
| Reporter: |
Richard Fine
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 24/Jul/07 04:00 PM
Updated: 25/Jul/07 08:20 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
1.2.33
|
|
|
When specifying the revision number for a "prompt" build spec on a versioned project, if the revision number you specify is such that the pulse file doesn't exist at the desired path in the repo, then there's no error or anything - it just returns to the project summary screen without starting a build. I had to look into the server logs to find out what was going on.
(I'm not really expecting a fix for this in 1.2.x, but it may be worth bearing in mind for 2.0, and may be useful to anyone else who runs into the same problem).
|
|
Description
|
When specifying the revision number for a "prompt" build spec on a versioned project, if the revision number you specify is such that the pulse file doesn't exist at the desired path in the repo, then there's no error or anything - it just returns to the project summary screen without starting a build. I had to look into the server logs to find out what was going on.
(I'm not really expecting a fix for this in 1.2.x, but it may be worth bearing in mind for 2.0, and may be useful to anyone else who runs into the same problem). |
Show » |
|
Poor error reporting when triggering a build from an invalid revision number
Thanks for the report. It is pretty poor, so I will take a look for 1.2.x to see what this will take to fix.