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

Key: CIB-1350
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: James French
Votes: 0
Watchers: 0
Operations

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

Radio box support in trigger prompt

Created: 14/Dec/07 11:40 AM   Updated: 12/Dec/08 04:11 AM
Component/s: Web UI
Affects Version/s: 1.2.35
Fix Version/s: x.x


 Description  « Hide
Hi Jason, Daniel,

I would really, really like this as it would iron out an annoying irritation in out setup. Let me explain...

One of our products consists of two deliverables, an installer and a software zip. Mostly we release these at the same time, but sometimes we release them separately, and they are versioned separately. What I'd like is to setup a single pulse project that would allow me to choose whether I want to build the installer, the zip or both. A radio box that pops up to prompt would be ideal for this.

What we've got at the moment is two separate pulse projects. This mean that when we kick off builds we have to remember to kick off the same revision for both of them and provide the same QA build number for both. I don't like this as its fragile.

I know I could make people type a string in for this, but I don't like that either.

Can I please have a radio box? Would love this in the 1.2 series as I can't see us moving to 2 for quite a long time.

(Check box support would be awesome too...)

Cheers,
James



 All   Comments   Change History      Sort Order:
James French - 14/Dec/07 11:46 AM
It would also allow me to auto tag the repository in a nicer manner as I would be able to tag the combined product wherease at the moment the auto tagging tags the deliverables separately.

jason - 14/Dec/07 10:40 PM
Hi James,

I understand your issue but unfortunately in the near term we are focused on getting 2.0 out the door as there are a lot of people and things waiting on it. For this reason we are not adding features to 1.2. This particular change would also require a schema update which, while not impossible, makes the implementaton more difficult as we are currently implementing the upgrade path for 2.0. The upshot of this is it is unlikely we will see this feature in the short term, and it is more likely to appear in 2.0 than 1.2 when we do get to it.

James French - 17/Dec/07 03:55 PM
Fair enough. One has to try :)

Rest assured I'll be pushing for features when we're on the 2.x series (got quite a lot waiting in the wings....) I'm guessing it will be a few more months yet though.

James