TeamCity is broken, need a fix or replacement

[Alexander Zaytsev]

The Codebetter has decommissioned its old build agents and servers. This broke our builds.

The problem with Codebetter's TC that we do not have any control over it.

Does anyone know the better options? We either need to fix the build agent by communicating with Codebetter or migrate to another platform (either own or shared.

Best Regards,
Alexander

[Oskar Berggren]

Have you been in contact with them on the matter recently?

I got this from Anne Epstein in 2014 but couldn't do anything at the time:

> We are, however, in the process of moving to much newer agents, and would LOVE to get the process of moving NH started soon. Do you have a list of what might be required for your builds to fully work on a new agent? Given that > you are near you 4.0 release, it might not be the best time to actually make the switchover, but since your build is complex, we would like to get working on getting the new environment ready.

So the better option might be to collaborate with them and get new agents up?

/Oskar

--

---
You received this message because you are subscribed to the Google Groups "nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-develo...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Steve Bohlen]

I'd recommend AppVeyor (AppVeyor.com); its free for the level at which we'd probably want/need it and offers Windows-based build agents with all the necessary .net versions available.

The catch is that it doesn't offer all of the database targets we'd need to support in order to test all the dialects.  It does offer MSFT SQLServer, MySql, and a few others but its missing e.g., DB2, Oracle.  If we wanted to test these we'd need to stand up our own instances of these elsewhere and have the tests connect to those.

I've used AppVeyor successfully for several other OSS projects without issue.

-Steve B.

---

From: Alexander Zaytsev
Sent: ‎1/‎4/‎2016 9:39 PM
To: nhibernate-development
Subject: [nhibernate-development] TeamCity is broken, need a fix orreplacement

--

[Gunnar Liljas]

So, it seems that the SQL Server connection is the only problem, or is there something else? 

[Stephen Bohlen]

AppVeyor *does* offer SQL Server, so if that's the only dialect target we run integration tests against then its not a blocker.

Or did you mean that SQL Server was the only blocker for getting TeamCity up and running @ CodeBetter again?

Steve Bohlen
sbo...@gmail.com
http://blog.unhandled-exceptions.com
http://twitter.com/sbohlen

[Gunnar Liljas]

I'm not sure. That's where the build fails (setting up the test database)

[Alexander Zaytsev]

Yep, it seems that they do not have any DB set up on the agents, or we do not know the connection strings.

Best Regards,
Alexander

[Oskar Berggren]

Should I get back in touch with Anne Epstein to get official information? As I understand it, we are guessing a bit at the moment?

/Oskar

[Alexander Zaytsev]

Yes, please. Yes this are my guesses

[Oskar Berggren]

I've been in contact with the Anne and some others.

Basically we should provide a list of requirements and they will sort it out on the new agents. I suppose most/all of that could be gleaned from the teamcity.build file.

I'll work with them to see if we can get the regular SQL Server build running again, in the meantime if anyone wants to document the other requirements that would be helpful.

/Oskar

[Alexander Zaytsev]

Thanks Oskar,

As I understand we only need to have the supported RDBMSes installed, and to know the connection strings.

The specific instructions are in the lib/teamcity/<RDBMS> folders. These are only needed for Oracle MySQL, and Postgres, as we need to create the nhibernate user/DB upfront. For Oracle also need to install the .net client.

Best Regards,
Alexander

[Alexander Zaytsev]

It seems that CodeBetter has put "agent03" back online, which means that we can run our NH builds. Until it will break again. 

So, we still need more reliable solution.

Best Regards,

Alexander

[Oskar Berggren]

I've been neglecting reporting back. Sorry about that.

That agent03 is back is from my discussion with them, as an interrim solution. Their new agents are much more strictly managed (to ease maintenance), but we have been discussing some possibilities. They are evaluating if they can provide these databases and I think the matter is mostly about them finding a way to ensure it's low maintenance for them. I also have some other ideas.

/Oskar