History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-1352
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: jason
Reporter: James French
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pulse

Impossible to clear build specification restriction for build completed trigger

Created: 27/Dec/07 01:24 PM   Updated: 31/Dec/07 04:08 AM
Component/s: Web UI
Affects Version/s: 1.2.43
Fix Version/s: 1.2.44


 Description  « Hide
I have a trigger that is set to fire when another project build finishes (in any state). It does not get triggered if the 'restrict to build specification' is blank. My understanding is that it should fire on completion of any build specification in this case.

 All   Comments   Change History      Sort Order:
jason - 28/Dec/07 12:19 AM
Hi James,

Thanks for the report. It appears that the problem is actually in editing the build completed trigger. Once a specification is selected, it is impossible to clear it. You can work around this by deleting that trigger and adding a new one with the specification not set.

jason - 28/Dec/07 03:57 AM
Fixed in change 4059.

James French - 28/Dec/07 10:22 AM
Ah yes, that is a bug. Are you sure its the same bug though? When I looked at the 'restrict to build specification' field it was blank - so shouldn't that trigger on all specs? When I changed the field to a specific specification it started triggering correctly. Seems like two bugs to me.

jason - 31/Dec/07 04:08 AM
Hi James,

There may be a fault assumption on my part here. I tried to reproduce the problem of having no specification set but the trigger not firing. However, the trigger fired for me just fine with a trivial set up. In trying some more variations, I noticed that the specification could not be cleared. Since the effect was basically the same, I (it appears mistakenly) assumed this to be the bug.

So that leaves one bug fixed but the original a mystery which I cannot yet reproduce. Can you describe each field of the trigger configuration for the broken trigger and also which projects are involved in the triggering? My setup was very simple so something could be different. Thanks in advance for any help.