Hi Shaun,

Currently, there are no interactions between security and dynamic
values - actually, there are no interactions between dynamic values
and system properties at all!

So, I have made a few modifications to allow this scenario:
1) Labellers can now use dynamic values (previously only tasks could).
2) Integration properties (http://confluence.public.thoughtworks.org/
display/CCNET/Integration+Properties) are now added as parameter
values. To access these use the integration property name prefixed by
a dollar sign (e.g. $CCNetBuildDate).
3) Added a new integration property called CCNetUser - this will only
be set when there is a valid logged in user.

Let me know what you think,


Craig

On Jul 1, 1:50 am, CinnamonDonkey <[email protected]>
wrote:
> Hi All,
>
> What information does CCNET hold about the person/machine that
> 'forced' a build?
>
> Using the new dynamic parameters in the 1.5 branch (not yet released).
> I've configured a project that allows the requester to specify the
> configuration,platform and changelist to be built.
>
> Off course, the requester needs to be emailed the results of their
> build request.
>
> Also, ideally the build should be labelled "Changelist 1234, built for
> Joe (DEBUG|Win32)".
>
> How do you think this could be achieved.
>
> Cheers,
> Shaun
>
> p.s. Dynamic Parameters ROCK!

Reply via email to