Problems with CVS

I'm running into quite a few problems with CVS, making a move from CC to TeamCity a questionable proposition.

The first is a problem with using branches that I mention in an earlier message.

In addition, I'm getting inconsistent code repositories on the different buildAgents and find myself having to "reset sources" pretty often to fix builds. Things such as missing files, bad versions, etc. Unfortunately, I don't have a good case to file a bug with. Just something I notice at some point down the line when investigating a broken build in TC that is building fine in CC. I'll keep trying to track down specifics to help in fixing them.

I don't want to use full checkout for each build, as that is a lot of code. But I don't want to keep resetting sources manually, either.

There have been some other CVS issues I've run into and I'll try and list them/Jira them as I recall them. But I'd have to say that the CVS support feels kind of sketchy. I wonder if this is in part due to the fact that CVS isn't part of Jetbrain's dogfood, I believe (I think you run with Perforce/Subversion mix).

--Tim

4 comments
Comment actions Permalink

In addition, I'm getting inconsistent code repositories on the different
buildAgents and find myself having to "reset sources" pretty often to fix
builds. Things such as missing files, bad versions, etc.


Can it be the result of some bulk change when TC, getting repository by
date, does get not all files in the change? Is 'changes' page for the build
shows valid information about real changes or not?


"Tim McNerney" <intellij@oneofus.org> wrote in message
news:26182704.1153418848255.JavaMail.itn@is.intellij.net...

I'm running into quite a few problems with CVS, making a move from CC to
TeamCity a questionable proposition.

>

The first is a problem with using branches that I mention in an earlier
message.

>

In addition, I'm getting inconsistent code repositories on the different
buildAgents and find myself having to "reset sources" pretty often to fix
builds. Things such as missing files, bad versions, etc. Unfortunately, I
don't have a good case to file a bug with. Just something I notice at some
point down the line when investigating a broken build in TC that is
building fine in CC. I'll keep trying to track down specifics to help in
fixing them.

>

I don't want to use full checkout for each build, as that is a lot of
code. But I don't want to keep resetting sources manually, either.

>

There have been some other CVS issues I've run into and I'll try and list
them/Jira them as I recall them. But I'd have to say that the CVS support
feels kind of sketchy. I wonder if this is in part due to the fact that
CVS isn't part of Jetbrain's dogfood, I believe (I think you run with
Perforce/Subversion mix).

>

--Tim



0
Comment actions Permalink

In addition, I'm getting inconsistent code

repositories on the different

buildAgents and find myself having to "reset

sources" pretty often to fix

builds. Things such as missing files, bad versions,

etc.

Can it be the result of some bulk change when TC,
getting repository by
date, does get not all files in the change? Is
'changes' page for the build
shows valid information about real changes or not?


Sorry, but I wasn't tracking things closely enough at the time to catch the problem when it happened (I know this makes it hard to debug, but I am looking for it to happen again). I noticed the problem well after it had happened and all sorts of things could and probably did happen in the interim, including shutting down of the server and the build agent. I don't think there were any strange happenings in terms of the checkins that could have caused confusion to TeamCity.

I'm pretty sure that CruiseControl does checkouts by date and I didn't see any similar problem with our builds there, but I won't swear to the fact that they use date. I can check if that would be useful to you.

I'm trying to keep an eye out for similar problems and can hopefully give you more complete information if it happens again.

--Tim

0
Comment actions Permalink

CruiseControl waits after the modifucation for new changes and (if changes
were made) it does not start build. It's a kind of support of "transaction"
for cvs where transactions are not supported. We're going to support the
same functionality but it is not supported at the moment. But some bugs
(related to patching not to cvs only) were fixed, maybe they were the result
of the problem, please let me know if it will be reproducable in the next
eap.

Please submit bug request related to cvs branch problem. Unfortunately, I
cannot reproduce the problem, but i'm planning to add possibility to enable
cvs output, maybe it will help.

Thanks!

"Tim McNerney" <intellij@oneofus.org> wrote in message
news:14054937.1153758193649.JavaMail.itn@is.intellij.net...
>> > In addition, I'm getting inconsistent code
>> repositories on the different
>> > buildAgents and find myself having to "reset
>> sources" pretty often to fix
>> > builds. Things such as missing files, bad versions,
>> etc.
>>
>> Can it be the result of some bulk change when TC,
>> getting repository by
>> date, does get not all files in the change? Is
>> 'changes' page for the build
>> shows valid information about real changes or not?
>

Sorry, but I wasn't tracking things closely enough at the time to catch
the problem when it happened (I know this makes it hard to debug, but I am
looking for it to happen again). I noticed the problem well after it had
happened and all sorts of things could and probably did happen in the
interim, including shutting down of the server and the build agent. I
don't think there were any strange happenings in terms of the checkins
that could have caused confusion to TeamCity.

>

I'm pretty sure that CruiseControl does checkouts by date and I didn't see
any similar problem with our builds there, but I won't swear to the fact
that they use date. I can check if that would be useful to you.

>

I'm trying to keep an eye out for similar problems and can hopefully give
you more complete information if it happens again.

>

--Tim



0
Comment actions Permalink

CruiseControl waits after the modifucation for new
changes and (if changes
were made) it does not start build. It's a kind of
support of "transaction"
for cvs where transactions are not supported. We're
going to support the
same functionality but it is not supported at the
moment. But some bugs
(related to patching not to cvs only) were fixed,
maybe they were the result
of the problem, please let me know if it will be
reproducable in the next
eap.

Please submit bug request related to cvs branch
problem. Unfortunately, I
cannot reproduce the problem, but i'm planning to add
possibility to enable
cvs output, maybe it will help.

Thanks!


I have done so (http://www.jetbrains.net/jira/browse/TW-592) and will keep it updated with new findings.

As per my original post, I have also filed an issue (http://www.jetbrains.net/jira/browse/TW-593) for branches on CVS failing.

--Tim

--Tim

0

Please sign in to leave a comment.