9 comments
Comment actions Permalink

Under "Administration" -> "Edit server configuration", I cannot change the Authentication Settings anymore.
An "Edit Settings" link is only provided for the two notification sections.

I wanted to activate Guest User Login, but it's not possible anymore via the web interface...

0
Comment actions Permalink

What do you consider as a blocker for Agra
release?


The inability to run code inspections.
See http://www.intellij.net/forums/thread.jspa?threadID=266326&tstart=0

The inability to use code coverage with JUnit4 (which was released more than a year ago).

Message was edited by:
Tobias Kurzke

0
Comment actions Permalink

Next bugfix release of Agra is available.


Is there a list of bug fixes for this EAP build? I haven't been able to find it.

What do you consider as a blocker for Agra release?


For us, it would be the ability to use Perforce client specs in build configs as specified in these JIRA bugs:
TW-792 (which has been pushed out to Benares)
TW-2104 (which has not been assigned)

It would be very helpful to have this one fixed as well because of the workarounds that I am forced to do to get around the problems caused by not having direct checkouts:
TW-2103

Thanks,
-Dave

0
Comment actions Permalink

Here's another bug in #3989:

For the Ipr & the Inspection runner, the option "Detect global libraries and module-based JDK in *.iml files" can't be disabled.
Well, it can be disabled, but when you enter the configuration page again after saving the disabling, the feature is enabled again.

0
Comment actions Permalink

Next bugfix release of Agra is available.


Is there a list of bug fixes for this EAP build? I
haven't been able to find it.


http://tinyurl.com/sk9y6

Regards,
KIR

0
Comment actions Permalink

We've removed this section from the interface, but plan to re-add it back.
For now, you can specify that setting in .BuildServer/config/main-config.xml file.

Hope this helps,
KIR

0
Comment actions Permalink

What do you consider as a blocker for Agra

release?

For us, it would be the ability to use Perforce
client specs in build configs as specified in these
JIRA bugs:
TW-792 (which has been pushed out to Benares)
TW-2104 (which has not been assigned)

It would be very helpful to have this one fixed as
well because of the workarounds that I am forced to
do to get around the problems caused by not having
direct checkouts:
TW-2103


Dave, all these issues require a lot of work to implement (several of men-months) because require a lot of refactoring and rewriting of existing code. That's why these issues were moved to the next version of TeamCity (Benares).

Thanks for understanding,
KIR

0
Comment actions Permalink

Will be fixed in the next EAP.
Thanks for the report!

0

Please sign in to leave a comment.