TeamCity 3.1 EAP, build 6692, is available

Yegor Yarko (JetBrains) wrote:

New TeamCity EAP release (build #6692) is ready for download!

This build brings Oracle support as external database and bug fixes.

As TeamCity 3.1 release is really close, please do not hesitate to let us know any critical issues you experience with your current or this latest build.

I'd like to nominate my Build Agent over https problem. I don't see a
workaround for this and I'm stuck.

http://jetbrains.net/jira/browse/TW-4520

Ah, I see the Fix Version and Priority have been assigned -- does "Next
Version Pool" mean 3.1 or not?

I don't mind coping with a workaround if there's a decent one, but I
don't think I can wait until a 3.2 release.

Hello,

Since https communication is critical we will address this issue ASAP.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Chris Morris" <chris.morris@einstruction.com> wrote in message
news:fpfklj$e95$1@is.intellij.net...

Yegor Yarko (JetBrains) wrote:

>> New TeamCity EAP release (build #6692) is ready for download!
>>
>> This build brings Oracle support as external database and bug fixes.
>>
>> As TeamCity 3.1 release is really close, please do not hesitate to let us
>> know any critical issues you experience with your current or this latest
>> build.
>

I'd like to nominate my Build Agent over https problem. I don't see a
workaround for this and I'm stuck.

>

http://jetbrains.net/jira/browse/TW-4520

>

Ah, I see the Fix Version and Priority have been assigned -- does "Next
Version Pool" mean 3.1 or not?

>

I don't mind coping with a workaround if there's a decent one, but I don't
think I can wait until a 3.2 release.

Chris,

I believe https problem has already been fixed in the first TeamCity 3.1 EAP.
So pleeease try 3.1 :)

Kind regards,
KIR

Kirill Maximov (JetBrains) wrote:

So pleeease try 3.1 :)

Trying it out - a note first. When I put https://yada.yada.com in the
build agent properties at the end of install, I'm prompted with:

"Wrong value for 'serverUrl' parameter. Http protocol should be used.
Continue anyway?

Should this dialog be there?

Kirill Maximov (JetBrains) wrote:

Chris,

I believe https problem has already been fixed in the first TeamCity 3.1 EAP.
So pleeease try 3.1 :)

Ok, the build agent was able to get going - but not without some other
problems - opened a JIRA ticket: http://jetbrains.net/jira/browse/TW-4556

• After entering the https url in the Build Agent properties, I

was warned with a dialog saying, "Wrong value for 'serverUrl' parameter.
Http protocol should be used. Continue anyway?"

• The build agent shut itself down after downloading several update

.zip files and didn't restart. I was tailing the teamcity-agent.log
file, saw it had shut down, waited a few minutes and manually started
the Build Agent service myself. It came back up and eventually
registered with the server.

• The process of the build agent downloading several .zip files and

whatnot takes well over 2 minutes - and there's no feedback anywhere,
not even a dialog (I don't think) that says, "Hey it could take several
minutes for your Build Agent to get up-to-date before seeing it on the
build server."

• Any .NET related agent failed to register, because it couldn't

find any .NET frameworks. I have 2.0 installed (VS2005 is running right
now with a C# project I'm working on, in fact

(JIRA issue has my teamcity-agent.log file attached)

Chris Morris wrote:

Kirill Maximov (JetBrains) wrote:

>> So pleeease try 3.1 :)

Trying it out - a note first. When I put https://yada.yada.com in the
build agent properties at the end of install, I'm prompted with:

"Wrong value for 'serverUrl' parameter. Http protocol should be used.
Continue anyway?

Added this to this ticket: http://jetbrains.net/jira/browse/TW-4556