| Key: |
CIB-737
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
jason
|
| Reporter: |
James Gregory
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 07/Nov/06 01:39 AM
Updated: 21/Nov/06 02:04 PM
|
|
| Component/s: |
Web UI
|
| Affects Version/s: |
1.1.8
|
| Fix Version/s: |
1.2.6
|
|
|
Environment:
|
Linux, Firefox, etc.
|
|
|
We're using one of these "resource" things to set the version number on our release target when we're doing release builds. At the moment, we need to go through some crazy number of mouse clicks to get to the version resource, and its location is really not that intuitive.
I think it would be way more awesome to have the resources for a particular project visible and changeable on the project page itself. Then you can quickly do a visual inspection that the build version matches what you're expecting, and you can change it and hit "go", all from one place.
|
|
Description
|
We're using one of these "resource" things to set the version number on our release target when we're doing release builds. At the moment, we need to go through some crazy number of mouse clicks to get to the version resource, and its location is really not that intuitive.
I think it would be way more awesome to have the resources for a particular project visible and changeable on the project page itself. Then you can quickly do a visual inspection that the build version matches what you're expecting, and you can change it and hit "go", all from one place.
|
Show » |
|
Provide an easier way to manually specify properties to builds
The problem is really that this is not an intended use case for resources. Resources are designed to hold information about build dependencies (such as tools/runtimes/libraries etc) that are required for builds. They exist on a per-agent level as the available resources and their properties may differ from machine to machine. They are also used to decide which agents are capable of performing a build for scheduling purposes.
That said, currently there is no other way form the web UI to provide properties manually to a build. We would like to add something like this, and it will certainly be easier than the current workaround of using resources. Not sure when we will get to it. I am scheduling against 1.2 for now, in the hope we can squeeze it in.