Thanks Ruben! This makes complete sense.
On Sep 15, 2:22 pm, "Ruben Willems" <[EMAIL PROTECTED]> wrote: > Hi > > you can do the following : > in every report that you want to include in that 'Master Project', > include a task in the publisher section. > This task will create/append a file in a certain location : > eg c:\temp\failed_procjects.txt > The contents of this file is the failed project name, or if you want, you > can also include the error(s) of the failed project. > > Now the Master project only needs to check the existence of this file. (Just > a task in the tasks section) > If the file exists --> build failed. > > To let the engineers see which project(s) failed, write the contents of this > file to the error stream. > for example : suppose this task is a Nant task, read the file contents into > a string, and use the fail task of Nant > with this string. > > Hope this makes it clear for you > > with kind regards > Ruben Willems > > > > On Mon, Sep 15, 2008 at 3:19 PM, rdbossjr <[EMAIL PROTECTED]> wrote: > > > I am looking for a way to create one project that will be run after > > all other projects that will be red or green based on the results of > > the other projects. For instance, If projA, projB and projC are green > > I would like the summary project to be green. If any projecty is red > > I would like the summary project to be red. > > > I need this because we have many projects (40+) on one server that are > > built once a night. I would like to be able to have one project in > > CCtray that the engineers can look at first thing in the morning that > > can give them the state of the previous night's build. > > > Any ideas? I have looked through the documentation and can not find > > anything that pops out to me to make this happen. > > > Thanks, > > david- Hide quoted text - > > - Show quoted text -
