I'm considering TeamCity for CI and not sure whether I can use Professional License (which is free) for commercial application?
From their license page https://www.jetbrains.com/teamcity/buy/ , seem like the Professional License only restricted in number of build configuration and build agents, doesn't mention anything about commercial usage.
In their FAQ https://sales.jetbrains.com/hc/en-gb, they are talking about commercial license and personal license, not mentioning professional license and enterprise license, which makes me even more confused. Is the FAQ page outdated?
My application is .NET application, hosted in Github (private). We intend to setup TeamCity in AWS as build server
According to the licensing (section 4b: https://www.jetbrains.com/teamcity/buy/license.html), there is no restriction for corporations.
Note: In my division we currently use the free version, and we didn't find any difficulties. We are still planning to upgrade soon because of the limited build configurations.
TeamCity can be used for commercial purposes, but is restricted to 20 build configurations and 3 build agents. If you want to use more build configurations or agents, then you need to upgrade to a paid licence.
However, if you just need additional build agents, these can be bought separately.
From TeamCity 2017.2 onwards, the professional version (free) includes 100 build configurations, which is a significant increase on the previous versions that were limited to 20. It still has a limit of 3 build agents.
Further info here https://confluence.jetbrains.com/display/TCD10/Licensing+Policy
Related
I couldn't stomach purchasing the $150 for GCP's support service for this one question. I'm just looking to understand the schedule for Cloud Build Node.js versions. It's still stuck on Node.js v10.10 and my projects are starting to require higher versions to build. According to Cloud Build's changelog, I don't believe the Node.js version has updated in years. Any ideas?
As per the official Github repository:
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js.
So, this means it should work with Node.js 12 and the updates should be more constant. In addition to that, in here, it says that if you are using a Cloud Build config file, you can use Node.js 12, so the Node.js' latest version should be compatible with Cloud Build.
To summarize, by the repository, it should follow Node.js schedule. However, in case you think this is not occurring, I would recommend you to raise a bug on the Google's Issue Tracker - it's free, by the way - so they can assess this.
I have started using the preview of Microsoft Team Foundation Service (TFS in the cloud, henceforth TFService) for a small project, and I'm currently setting up builds using the online build service included with TFService.
What I want to do is to add an installer of some kind. I've previously worked with InstallShield Limited Edition, WIX and Inno Setup and would like to keep using one of those if possible.
I've previously integrated Inno Setup as part of a build process (TFS 2010). This involved installing Inno Setup on the build computer, and adding a custom build task for running an inno setup script. The last part should be possible with TFService as well, because it's possible to create custom build process templates.
However, I realize that installing anything such as Inno Setup or InstallShield will not work with TFService, since it's not possible to install any 3rd party software on the build computer (it's just a cloud service running on some unknown virtual computer which I cannot access).
So my question is; is there a way to automatically create an installer as part of a build process running on TFService? For example, is the build service capable of building installshield projects out of the box (there's a license included with Visual Studio after all)? Or are there other ways to do this?
I have some experience with this trying to get WiX and InstallShield to work with Microsoft TFS Preview cloud service using their managed build agents. On these agents, you don't have administrator rights and you can't install software.
This currently rules out InstallShield which must be installed.
It is however possible to check the WiX binaries into source control and pull them down as part of your build.
WiX uses .wixproj files (MSBuild) to define their project compile activities. This references a targets file and other properties ( referencing registry values ) that won't exist when you deploy this way. A small bit of hacking will get all of these properties to resolve to workable values.
The one problem you may still have though (and I'm thinking TFS managed build environment ) is that you may have to configure your projects to skip MSI ICE validation suites. On the build machines, I played on the windows installer service was outright disabled and this prevented the tests from running.
I'm looking for possibility to allow any users of certain project of Jira start (trigger) certain Hudson builds. Is it possible without creating own Jira plugin?
I would have expected this feature to be available with the Marvelution JIRA Hudson Integration, which offers functionality pretty similar to he one offered by the JIRA Bamboo Plugin (e.g. build status reporting) - surprisingly though, triggering builds as you desire seems not to be available in either one yet, despite an obvious feature indeed (the JIRA Bamboo Plugin has related/partial support at least, see Running a Bamboo Build when Releasing a Version).
Consequently you might want to file a feature request for the Marvelution JIRA Hudson Integration first rather than developing your own from scratch immediately, maybe it is going to be considered.
Please note that this plugin doesn't support JIRA 5.0 yet, but the respective version 5.0.0 is scheduled for May 24, 2012.
At the moment, we are running our automated (not CI as such) builds via FinalBuilder via a very simple homegrown Apache interface that just launches the FB scripts on our server. (I like FinalBuilder, and will keep it, but it's CI server, FinalBuilder Server just doesn't cut it IMHO -- especially it doesn't support any "agent" concept at the moment to distribute builds across machines.)
We are doing native C++ development on Windows with a bit .NET mixed in where it's needed and makes sense.
Our current FinalBuilder scripts do everything quite well, from creating nightly builds to full releases (build / automated translation / build / unit test / create setup / put created artifacts on a network share / ...), but our webinterface, queuing abilities, user traceability and reporting is pretty limited.
I have looked around and it seems that TeamCity and Bamboo tick similar boxes, but most descriptions I can find cover only Java and/or .NET simple builds.
So my specific question is, given
several (20-30) complicated FinalBuilder Scripts that work to my satisfaction and that I will have to integrate into ("call" from) the new automation/"CI" server
Native Windows C++ and .NET projects
The actual build (= compiler invocation(s)) is done via a few Visual Studio solution files at the moment
Currently one build server machine, wishing to scale to 2-3 atm.
Using JIRA as issue tracker
using AccuRev as SCM
which tool is better suited, and why: TeamCity (currently 6.5) or Bamboo (currently 3.1).
(Note that I also hope to get some highly subjective answers on the TeamCity and Bamboo forums.)
For TeamCity side, it integrates with Jira, has AccuRev plugin, and has a good support for VisualStudio/C++ projects. It can also run arbitrary scripts.
You can trigger a build and obtain some build results via HTTP-based API. In the UI, you can see which changes have been built and in which build configurations. Easily integrate any custom HTML reports into TeamCity UI (no coding), publish artifacts.
Probably, you should try both solutions and see which one is more suitable for you (with Teamcity, you can use full-functional server for free, the only limit is number of build agents and number of build configurations).
Disclaimer: I'm a TeamCity developer
I found Bamboo more credible than TeamCity. Here are my reasons:
Those Jira plugins for VS or Eclipse are Bamboo plug-ins too. :) no extra add-ins needed.
Better support for Jira integration.
Nice user interface, like the one you used for Jira.
Ability to better integration with other Atlassian tools, such as FishEye.
Cheaper. A 10$ license will suffice your company.
More add-ons on Bamboo than TeamCity, lots of plug-ins.
For completeness' sake: I ended up using Jenkins + Finalbuilder. :-)
I worked in a similar environment using FinalBuilder for build automation, AccuRev for source control and a native windows projects.
I ended up selecting Electric Commander as the best CI solution for the job. It is possible to reuse parts of the FinalBuilder scripts and call them from Electric Commander but simply calling the FB script as one build step would result in you missing out on some of the key advantages of using Electric Commander - realtime log file processing, the ability to parallelize right down to individual step levels in Electric Commander and data collection and reporting.
Electric Commander has an API that exposes all product functionality which can be used in combination with AccuRev triggers to achieve a very flexible solution.
Disclaimer - I liked Electric Commander so much I joined the company and am currently employed by Electric Cloud.
You can try Electric Commander by going to www.electric-cloud.com and clicking on "Try It!"
I'm trying to test Coldfusion for learning purposes, but I really don't know what is the aditional features that the non-free Enterprise Edition add to the free Developer Edition.
Thanks!
Legally, Enterprise is for public consumption, and Dev is not.
Practically, this means that the Dev edition (which is the same as the Eval edition after the 30? days) is limited to localhost + 1 IP address. That is, it can serve files to localhost and 1 external IP. This IP can only be reset by restarting the service.
Otherwise, your dev install will mimic an ent install completely.
The developer edition of Adobe ColdFusion Server is limited by IP addresses - only the localhost and 1 other IP address can access the server. Any more, and it will throw license exceptions.
Also, printable items such as documents created with cfdocument and cfpresentation are watermarked with a gigantic diagonal banner over each page.
Otherwise, the dev and enterprise editions both have all the features enabled, including advanced debugging and server monitoring, PDF & FlashPaper generation, advanced gateways, 64 bit CPU support and full database drivers including Oracle - the works.
The Trial edition of ColdFusion is the same as enterprise for 30 days, but then drops to be the developer edition after 30 days - once the license has expired. Do make sure you remember to get your serial number in if you put this on production :)
For reference, see Adobe ColdFusion Editions.
The key is the line: "Used for delivering multiple websites and applications on one or more servers"
The Enterprise Edition allows for deployment for commercial purposes.
The Development Edition allows you to develop locally, but not deploy. The deployment requires Enterprise or Standard editions, or purchasing a hosting solution which handles the licensing for you.
Here you go.
Edit: Scroll to bottom for Dev v. Ent. discussion.