Does JetBrains uses TeamCity to insure that the Community version always compiles ?

The recent  refactoring of the local version code appears to be preventing the community version of IJ from compiling.
If this is indeed the case, I'll double check, why isn't JetBrains using one of TeamCity's best features to prevent this from happening ?

 


8 comments
Comment actions Permalink

Apologies,  this appears that doing a complete build fixed this.

Though, I would have hoped that the make detected which files needed to be recompiled.

And I am still curious if JetBrains uses TeamCity to insure that the Community version always compiles.

0
Comment actions Permalink

Hello Rob,

And I am still curious if JetBrains uses TeamCity to insure that the
Community version always compiles.


Of course we do. The local VCS changes did in fact cause a breakage (because
we have separate IDEA projects for the Community and Ultimate codebases,
and the one for Community wasn't properly updated), but as of now this has
been fixed.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

I was under the impression that if a developer uses TeamCity to checkin code and the compile/tests failed then there was the option for TeamCity not to checkin changes to the master repository.

Since the build did break it appears that this feature is not being used for the Community version.


If JetBrains is currently performing checkins through TeamCity, is it possible to use this feature for the Community repository so at least it compiles ?

Of course, if JetBrains isn't using this feature in house then I wouldn't expect them to make a change just for the Community version.



-Rob

0
Comment actions Permalink

Per the information at http://www.jetbrains.com/teamcity/documentation/pluginMatrix.html the TeamCity Pre-tested (delayed) Commit feature does not work with Git. (see footnote 1 on the page.)

0
Comment actions Permalink

Hello Rob,

We don't require developers to use pre-tested commit for all their changes.
They can do so when they feel it's necessary, and they have the option of
running the community build when they do so (TeamCity lets developers choose
the configurations to run, and has no possibility of mandating a specific
set of configurations).

I was under the impression that if a developer uses TeamCity to
checkin code and the compile/tests failed then the there was the
option for TeamCity not to checkin changes to teh master repository.

Since the build did break it appears that this feature is not being
used for the Community version.

If JetBrains is currently performing checkins through TeamCity, is it
possible to use this feature for the Community repository so at least
it compiles ?

Of course, if JetBrains isn't using this feature in house then I
wouldn't expect them to make a change just for the Community version.


--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Mark,

Per the information at
http://www.jetbrains.com/teamcity/documentation/pluginMatrix.html the
TeamCity Pre-tested (delayed) Commit feature does not work with Git.
(see footnote 1 on the page.)


That's true, but Remote Run does work, so the developers can run the build
remotely and commit changes if it passes. Sorry for a bit of confusion. :)

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Thanks for taking the time to explain.


-Rob

0
Comment actions Permalink

Would you mind sharing a little bit of your infrastructure setup (maybe in the blog)? It would be nice to know how you guys use TeamCity to to provide maximum productivity.

0

Please sign in to leave a comment.