#30 Feature Request: different build configurations for a prj

[icnocop]

Hello.

I think it would be excellent if Draco would set
a "build.forced" NAnt property to "true" if the build was
actually forced (by a user).

Thank you.

[icnocop]

Logged In: YES
user_id=1108985

I was thinking about this for a long time and came up with a
better "solution".

Let me first clarify my problem, which I think I share with
others in the development community.

There may be more than one type of build I want to process
for each project. For example, my builds are currently set up
with Draco to commit changes back to source control. In
order to do this, I had to specify to ignore all users changes,
and require that the "Force Build" button be pressed in order
for an actual build to be performed.

In order to extend this requirement and functionality, there are
many solutions, but here is my idea:
Dynamically create "Tools" buttons for each project based on
settings in the Draco.builds.config file.

Here is an example configuration:

<build>
...
<continuousBuild>
<nant>
<buildfile>master.build</buildfile>
<targets />
<properties/>
</nant>
<ignorechanges>
<ignore user="AutoBuilder" />
</ignorechanges>
</continuousBuild>
<forcedBuilds>
<forcedBuild>
<name>Smoke Build</name>
<nant>
<buildfile>master.build</buildfile>
<targets />
<properties>
<property name="deploy" value="true" />
<property name="beta" value="true" />
</properties>
</nant>
</forcedBuild>
<forcedBuild>
<name>Build and Commit</name>
<nant>
<buildfile>master.build</buildfile>
<targets />
<properties>
<property name="deploy" value="true" />
<property name="commit" value="true" />
</properties>
</nant>
</forcedBuild>
</forcedBuilds>
</build>

Thank you