Products Desktop + Web Everything you need to build robust native Mac and Windows apps, dynamic web apps, and beyond. Choose the SDK that fits your needs, whether it be gaming with Unity, hybrid apps with Xamarin, server-side apps with PHP, or web apps with JavaScript. SDKs Available For OS X + tvOS Unity Windows JavaScript PHP .Net Explore Desktop + Web Mobile Build powerful, full-featured mobile apps faster than ever before. iOS + watchOS Android Unity Windows Xamarin React Explore Mobile Embedded + IoT Connect your Internet of Things devices to the power of Parse. QualcommTexas Instruments AtmelC++ Broadcom IntelArduino Explore Embedded + IoT
NWTS Java Code The installation instructions for all of our plugins is the same, and pretty straightforward: Download the desired plugin ZIP package from the downloads page. Place the plugin ZIP package in the $TEAMCITY_HOME_DIRECTORY$/webapps/ROOT/plugins/ directory. Restart the TeamCity server. Go to Administration | Server Administration | Plugins List and verify that the plugin appears under External Plugins, and is the correct version. Additionally, see the information below about each of our TeamCity plugins: LinuxSystemProperties | Shared Build Number Linux System Properties Linux System Properties was born out of TeamCity feature request TW-23523. On a Windows machine, those three might read "amd64," "Windows 7" and "6.1," respectively. While this information is technically accurate, "Linux" and "2.6.32-279.5.2.el6.x86_64" are not super helpful in identifying the environment the Agent is running in. Shared Build Number
Semantic Versioning 2.0.0 Summary Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes,MINOR version when you add functionality in a backwards-compatible manner, andPATCH version when you make backwards-compatible bug fixes. Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format. Introduction In the world of software management there exists a dread place called "dependency hell." In systems with many dependencies, releasing new package versions can quickly become a nightmare. As a solution to this problem, I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. I call this system "Semantic Versioning." Semantic Versioning Specification (SemVer) The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. About License
Version Numbering These guidelines have been revised in 2006 for the Europa Simultaneous Release, and revised again in 2009 for the Galileo Simultaneous Release. Guidelines on versioning plug-ins This document contains a set of guidelines expressing how to evolve plug-in version numbers in a way that captures the nature of the changes that have been made. Reminder: In Eclipse, version numbers are composed of four (4) segments: 3 integers and a string respectively named major.minor.service.qualifier. Each segment captures a different intent: the major segment indicates breakage in the API the minor segment indicates "externally visible" changes the service segment indicates bug fixes and the change of development stream (the semantics attached to development stream is new to this proposal, see below) the qualifier segment indicates a particular build When to change the major segment The major segment number must be increased when a plug-in makes breaking changes to its API. When to change the minor segment
Plastic SCM - distributed version control system (DVCS) project management - Trac vs. Redmine vs. JIRA vs. FogBugz for one-man shop Integrating Sauce Labs Selenium Tests with a TeamCity Integrated Server | The Code Less Traveled In the course of my internship, I was provided a rare opportunity to research possible “new directions” for Appriss. One such area of research pertained to automated testing. Of course, Appriss has a sophisticated regression testing and unit testing system, but, in order shorten the QA cycle in development, my manager thought it might be worth looking into running Selenium, automated web browser tests in multiple environments so that different browsers on different platforms would no longer have to be tested manually. Setting Up the Tests Alright, no problem, Selenium is pretty straightforward; just read the docs and write the tests. To start, I wanted to make sure I could at least get some tests running on Sauce Labs itself, so I mimicked their Java-tutorial as shown on Github. TeamCity must check out the latest version of source code from the version control system.The latest version must be deployed to QA…somehow.The Selenium tests would execute. Build Step 1: mvn clean package
Minecraft + Node.js + Socket.io = Awesome Have you ever found programming extremely enjoyable? I hope so, otherwise you probably shouldn’t be programming. Well, either way, I found a whole new way of making programming fun: integrating new programming technologies to make your games even easier to use! As I stated in the video, this project is still a work in progress. Conclusion That is all for this fine Monday morning. About the Author Joe Zim Joe Zimmerman has been doing web development ever since he found an HTML book on his dad's shelf when he was 12. Related The Lazy Man's URL Parsing in JavaScript Have you ever needed to parse a URL using regular expressions? In "JavaScript" NPM and Using Node as a Command Line Tool Node.js was made to bring JavaScript to the web server so that people could use the same language on their front and back end, but that's not its only possibility Event-Based Architecture: Getting Decoupled