Double EAP: TeamCity 1.2 + Agra

Hi,

This time we're opening two EAP programs.

The first one is EAP for forthcoming TeamCity 1.2, which we're planning to
release in December.

TeamCity 1.2 will contain mostly critical bugfixes and a couple of features:

1. Visual SourceSafe 6.0 and 2005 support as a version control for your project
2. Visual Studio plugin which allows stacktrace opening from Web
! Please note, in this EAP you will need to have VSIP (Visual
Studio Industry Partner) SDK to use Vs-addin for TeamCity .
You may download it from Microsoft web site free of charge. Please visit the link
http://affiliate.vsipmembers.com/ for details about downloading VSIP SDK.
Surely, this will be fixed in the next EAP and release.

The second one is Agra, which is a codename for TeamCity 1.5 targeted on February.

It contains all fixes from 1.2 +

+ Show diff for your VCS changes on the Web
+ Enhanced notification policies with more customization
- ClearCase VCS support
- Option to checkout on build agent (for CVS and Subversion)
- Visual Studio 2005 Team System support
- Eclipse integration
- Dependent builds triggering
- Better and uniform UI to configure Inspections runner and IPR runner on the web
- Search for code duplicates on the server-side
- Agent details information page with possibility to edit agent properties
- Possibility to clone project
- Customizable build log filtering
- Improved Maven 2 support
- Ant 1.7 support

In this Agra EAP only first two features are available (+ many many lesser fixes,
see Changes page).

Now links.

Splitted TeamCity EAP page: http://www.jetbrains.net/confluence/display/TW
Changes page: http://www.jetbrains.net/confluence/display/TW/Changes+page

Download for stable 1.2 EAP:
http://www.jetbrains.net/confluence/display/TW/Download+Stable

Download for richer Agra EAP:
http://www.jetbrains.net/confluence/display/TW/Download+Latest

Let the force be with you,

KIR

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

6 comments
Comment actions Permalink

Will both of these automatically upgrade agents or do we need to
re-install? What about the Idea plug-in, does that need to be
re-installed? Generally speaking, how I do I know what to do for a
complete upgrade (i.e. when do I need to upgrade agent, Idea plug-in)?

Thanks,
R

0
Comment actions Permalink

Robert Gibson wrote:

Will both of these automatically upgrade agents or do we need to
re-install? What about the Idea plug-in, does that need to be
re-installed? Generally speaking, how I do I know what to do for a
complete upgrade (i.e. when do I need to upgrade agent, Idea plug-in)?


Build Agents should auto-upgrade.
Upgrade feature for IDEA plugin will work only in the next Agra EAP
(in 1.2 idea plugin autoupgrade is not available).


Regards,
KIR


Thanks,
R



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

0
Comment actions Permalink

Hi Kirill,

A couple of questions about the Agra release:

The second one is Agra, which is a codename for
TeamCity 1.5 targeted on February.
- Option to checkout on build agent (for CVS and
Subversion)


Will the ability to checkout to a build agent be added for Perforce as well eventually?

Will the ability to have build configs within a project have their own "VCS roots" (aka branch support) be introduced anytime soon? I asked support about this but was not given a release where this feature would be added.

Thanks,
-Dave

0
Comment actions Permalink

Hi Dave,

A couple of questions about the Agra release:

The second one is Agra, which is a codename for
TeamCity 1.5 targeted on February.
- Option to checkout on build agent (for CVS and
Subversion)


Will the ability to checkout to a build agent be
added for Perforce as well eventually?


There are some technical issues with this, so we didn't include this
in Agra release. BTW, what is your use case for such a feature?


Will the ability to have build configs within a
project have their own "VCS roots" (aka branch
support) be introduced anytime soon? I asked support


Definitely not soon. This would require significant refactoring of
almost all sever-side code. Please watch/vote for
http://www.jetbrains.net/jira/browse/TW-792
we'll probably add support in Benares (TeamCity 2.0).

Kind regards,
KIR

about this but was not given a release where this
feature would be added.

Thanks,
-Dave


Hi Dave,

0
Comment actions Permalink

Hello Kir,

Kirill Maximov (JetBrains) wrote:

Build Agents should auto-upgrade.
Upgrade feature for IDEA plugin will work only in the next Agra EAP


So if I upgrade to 1.2 EAP will I need to tell all my colleagues to
upgrade the plugin? I assume that I only need to do this if the server
API changes, is this the case for 1.1.1 -> 1.2? Since I have rolled out
to a limited number of users now I have less latitude to do frequent
client upgrades.

Thanks,
R

0
Comment actions Permalink

Hi Kirill,

Will the ability to checkout to a build agent be
added for Perforce as well eventually?


There are some technical issues with this, so we
didn't include this
in Agra release. BTW, what is your use case for
such a feature?


I am having a couple of problems using Perforce with TeamCity.
See the following bugs for details. I can provide more detail if needed:
TW-977 (This is a major problem)
TW-1099 (This is minor)

Will the ability to have build configs within a
project have their own "VCS roots" (aka branch
support) be introduced anytime soon? I asked

support

Definitely not soon. This would require significant
refactoring of
almost all sever-side code. Please watch/vote for
http://www.jetbrains.net/jira/browse/TW-792
we'll probably add support in Benares (TeamCity
2.0).


Okay. I added a comment to to TW-792 specifying
what we would like to see.

Thanks,
-Dave

0

Please sign in to leave a comment.