Hi
The file labeler allows you to use the BuildOK label, without any number. so
I would try it out.
Now I do not know if your sourcecontrol allows double labels,
but I doubt it (it would be silly if it did).
I know VSS replaces the build label if you use a dumplicate label
If clearcase does the same, than you just need to use this file labeler,
if not a setup as below would be a good approach
° use the file labeller, pointing to file with a contents of BuildOK
° set up a task in the task section that will remove the existing BuildOK
rom clearcase
a batch file or so that will be ran with the exec task in ccnet.
set this task as the LAST task n the task section
The reason : : the operation flow of ccnet is as follows :
1) Wait for the triggers to awaken.
2) Ask the source control system for a list of the modifications
since the last build.
3) If any modifications were found or if the triggers said "force the
build":
3.1) Generate a label for the build.
3.2) Run the prebuild tasks in the order specified, failing
the build in case of error.
3.3) Get the source code from the source control system.
3.4) Run the build tasks in the order specified, failing the
build in case of error.
3.5) If the repository should be labeled:
3.5.1) Let the source control system apply the label.
3.6) Run the publisher tasks.
4) Go to 1.
This should have the desired result
with kind regards
Ruben Wilems
On Fri, Oct 3, 2008 at 10:17 PM, Saran <[EMAIL PROTECTED]> wrote:
>
> Hi Ruben,
>
> I would like to keep moving the BUILDOK label whenever there is a
> successful build to all the files that were checked in after previous
> successful build. Our plan is to let developers use this label for
> view update, this will make sure that whenever they update the view it
> will be in buildable state.
>
> Thanks very much for your time
> Saran
>
> ps: I looked in to the filelabeler and I think this will not address
> my requirements, please correct me if I'm wrong.
>
>
>
> On Oct 3, 3:01 pm, "Ruben Willems" <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > just thought of something :
> > maybe you can take a look at the file labeler :
> http://confluence.public.thoughtworks.org/display/CCNET/File+Labeller
> > This sounds like the solution to your problem.
> >
> > with kind regards
> > Ruben Willems
> >
> > On Fri, Oct 3, 2008 at 4:18 PM, Saran <[EMAIL PROTECTED]> wrote:
> >
> > > Thanks Reben, but I guess I cannot apply customized label
> > > (LAST_SUCCESS_LABEL) using Cruisecontrol.net.
> > > Saran
> >
> > > On Oct 3, 6:28 am, "Ruben Willems" <[EMAIL PROTECTED]> wrote:
> > > > Hi
> >
> > > > In default the defaultLabeler is use
> > > > (if you do not specify a labeler section in your ccnet.config, you
> get
> > > this
> > > > one)
> > >
> http://confluence.public.thoughtworks.org/display/CCNET/Default+Labeller
> >
> > > > When you have set useLabel to true, a label will be applied.
> > > > The layout of this label is will be the buildnumber.
> > > > You can add a prefix to it (BuildOk-), so the label will be BuilOK-25
> >
> > > > with kind regards
> > > > Ruben Willems
> >
> > > > On Fri, Sep 26, 2008 at 4:19 PM, Saran <[EMAIL PROTECTED]> wrote:
> >
> > > > > Hi,
> >
> > > > > I would like to apply build label (BUILD_OK) if build succeeds but
> I'm
> > > > > not sure how to specify build label name to cruisecontrol.net. In
> the
> > > > > source control block, there is an option to apply label (useLabel),
> > > > > but I can't figure out how to specify the build label name.
> >
> > > > > <sourcecontrol type="clearCase">
> > > > > <viewPath>C:\PATH\TO\SOURCE</viewPath>
> > > > > <branch>main</branch>
> > > > > <autoGetSource>false</autoGetSource>
> > > > > <useLabel>true</useLabel>
> > > > > <useBaseline>false</useBaseline>
> > > > > <projectVobName>PROJECT_VOB_NAME</projectVobName>
> > > > > <viewName>PROJECT_VIEW_NAME</viewName>
> > > > > <executable>cleartool.exe</executable>
> > > > > <timeout>50000</timeout>
> > > > > </sourcecontrol>
> >
> > > > > Any suggestions would be really appreciated.
> >
> > > > > Thanks very much,
> > > > > Saran
>
