Commit trigger and CVS tags

Can I use commit triggering for a project that is based on a CVS tag? The triggering works grear for one of my other projects that is based off a CVS branch, but the project based off of a CVS tag never fires.

Thanks!

Todd

5 comments
Comment actions Permalink

Tagged directory contains fixed content from TeamCity point of view.
Even if you create new tag with the 'override' option, TeamCity cannot get
changes for the project for the same tag between 2 dates.

--
Olesya Smirnova
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


"Todd Breiholz" <no_reply@jetbrains.com> wrote in message
news:18008312.1176407152481.JavaMail.itn@is.intellij.net...

Can I use commit triggering for a project that is based on a CVS tag? The
triggering works grear for one of my other projects that is based off a
CVS branch, but the project based off of a CVS tag never fires.

>

Thanks!

>

Todd



0
Comment actions Permalink

That's unfortunate. I was excited to see that you added the ability to set up builds based on CVS tags in the latest versions of the product, but without automated triggering of builds based on CVS changes, I'm not seeing the benefit of using this tool in our environment.

Todd

0
Comment actions Permalink

When we added tags support the point was to get sources from some specific
cvs tag. In other words some fixed sources.Why don't you use branches if you
want changes to be triggered?



--
Olesya Smirnova
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


"Todd Breiholz" <no_reply@jetbrains.com> wrote in message
news:9655057.1176755648591.JavaMail.itn@is.intellij.net...

That's unfortunate. I was excited to see that you added the ability to set
up builds based on CVS tags in the latest versions of the product, but
without automated triggering of builds based on CVS changes, I'm not
seeing the benefit of using this tool in our environment.

>

Todd



0
Comment actions Permalink

We use tags similar to how many people use branches, I believe. We have a a tag that identifies the files necessary to build our integration environment, a different tag that identifies the files necessary to build our staging (or QA) environment and one more tag that identifies the files necessary to build our production environment. Revisions are moving in and out of these tags constantly.

We do not use branches because of the (perceived?) overhead of managing the branches and the frequent merges (we do integration builds 4 times a day, QA builds twice a day and production builds every 2 weeks).

Todd

0
Comment actions Permalink

Just for reference: related feature request.

0

Please sign in to leave a comment.