[Anthill-pro] Trunk and Branch workflow use

[Uldis Karlovs-Karlovskis]

Firstly we had the same configuration. That confuses users and
administration is harder. Sometimes there are cases when You need different
features on codelines (new features etc) what often is impossible with
"workflow per branch" configuration. 

Uldis Karlovs-Karlovskis, C. T. Co
uldis.karlovs-karlovskis at ctco.lv
 

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of emerson
cargnin
Sent: piektdiena, 2008. gada 28. martā 15:18
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Trunk and Branch workflow use

Isn't it enough to have a separated workflow? As theoretically the
non-originating builds would just be built on top of the originating
ones? And the differences could be done using workflow properties.

emerson

On 28/03/2008, Uldis Karlovs-Karlovskis <uldisk at ctco.lv> wrote:
> We need up to 3 base builds and some non-originating for branch, so we
copy
> Main project in Anthill and then adjust project/workflow properties for
> branch. Imo For now there isn`t any better solution.
>
> Uldis Karlovs-Karlovskis, C. T. Co
> uldis.karlovs-karlovskis at ctco.lv
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko,
Curtis
> Sent: piektdiena, 2008. gada 28. martā 14:29
> To: AnthillPro user and support list.
> Subject: RE: [Anthill-pro] Trunk and Branch workflow use
>
> We set security so our users can copy and existing workflow and edit the
> source config, bingo... New branch. They also edit the version as stored
> in the Stamping strategy.
>
>
> ===
> -Curt
> W: 860.702.9059
> M: 860.881.2050
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of emerson
> cargnin
> Sent: Friday, March 28, 2008 8:22 AM
> To: AnthillPro user and support list.
> Subject: [Anthill-pro] Trunk and Branch workflow use
>
> Hi
>
> How you guys set up a new branch?
> Do you just create a different workflow from the main build one?
> I created a property called branch in the workflow that is set by
> default to 'trunk'. I also used this property on the path for the
> repository of the sources. Finally i created a working directory script
> that takes that in account to avoid source location clashing.
> This way when I want to setup a different branch I will copy my trunk
> workflow and change de default value of this branch property.
>
> I can also just build a different branch choosing it in the build
> properties. The problem is that the only way to identify which branch
> that build originated is looking at the request properties.
>
> It w'ould be nice if you guys could tell me which are your strategy on
> setting different branches in AHP.
>
> regards
> emerson
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity to
> which it is addressed. If the reader of this e-mail is not the intended
> recipient or his or her authorized agent, the reader is hereby notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>