AHAH!!! Oddly I was not thinking "labeller" and this one just slipped past me.
Thank you very much !! Kevin On Thu, Mar 22, 2012 at 1:45 PM, Rolando Valdivia < [email protected]> wrote: > Kevin, > > Look for Remote Project Labeller in the documentation > > Rolando > El 22/03/2012 11:51, "Kevin Fernandes" <[email protected]> escribió: > > Hi all. I have a configuration where my builds are done on one machine and >> the installation packaing is done on separate machine. I have CCNet >> installed on both machines and currently use project triggers to coordinate >> copying the production binaries to a staging area (from machine 1) and then >> running an InstallShield command line to build the install package and >> publish it to a distribution site (from machine 2). The process itself >> works nearly flawlessly but I now have a requirement that the install >> packages get published to a folder whose name is the version label of the >> last build (from machine 1). The question is, is it possible to get the >> version label information of a remote CCNet project, using existing CCNet >> components? Both machines know about each others projects because of the >> coordination required. I could use the ForceBuild task to pass parameters >> but the project that forces the other project to build is not the project >> that has the build version label (is it easier to get it from the same >> machine rather that the remote machine?). >> >> Anyway I am all for writing the info to a file somewhere and reading it >> from the forced project (executing a script or some such to do this) if >> this is the only way to do it but I was interested in knowing if there is a >> way to do this directly in CCNet that I might be missing. >> >> Thanks in advance >> >> Kevin Fernandes >> > -- Kevin F.
