As a team empowered by .NET open source, we’ve always been sensitive to the people, projects, and conferences that make the .NET communit...
conference oss teamThe RIMdev team composition is a unique blend of disciplines forged in the crucible of time. We have backend developers, frontend develop...
Vue.js JavaScript frontend clientsidePreviously, I wrote about Publishing to npm Using AppVeyor. This is a similar post, but specifically geared toward publishing an npm pack...
AppVeyor npm MyGetStuntman is an open source library we developed at RIMdev to make testing user scenarios easier during development time. There are times ...
Windows Azure Azure Stuntman OSSTypically, running a Jekyll site locally for the first time requires a basic knowledge of using the command line. It usually involves a f...
jekyllA picture is worth a thousand words, so I assume a diagram is worth a billion words. Expressing our ideas is important and our blog is an...
JekyllBefore claiming we are in a Renaissance or that it is time for one, we should take the time to understand the meaning of the word and its...
.NET Community OSSAppVeyor does not currently provide built-in support for publishing to npm (at least, currently). Instead, we can provide the npm token a...
AppVeyor npmAt RimDev we’re trying to rethink the way we build our frontend. We have so many properties with common functionality, and it was startin...
Web components JavaScriptAt RIMdev, we are attempting to layer Hypermedia concepts into our APIs. One of these concepts is to have a collection of links to relate...
Web API ASP.NETTranscript Hello my name is Khalid Abuhakmeh and in this video I’ll be presenting an ASP.NET OWIN middleware library designed to eas...
video stuntman OSSHere’s some copy-pastable commands for creating SQL Server Express LocalDb instances: "C:\Program Files\Microsoft SQL Server\110\Tool...
LocalDbWelcome back for another edition of Under the Decision Tree. Our weekly selection of machine learning articles, podcasts, conferences, a...
Machine LearningOne of my early challenges at RIMdev was to create a RIMdev logo. Something that worked with the existing RitterIM knight, but also let u...
RIMdev Team DesignRather than enjoying some R&R during our recent holiday vacation, I worked on a small side project and was rewarded with an aching ri...
DevelopmentWelcome back for another edition of Under the Decision Tree. Our weekly selection of machine learning articles, podcasts, conferences, a...
Machine LearningWe are all in when it comes to static site generation. With [Windows Azure][azure] [GitHub][github] integration, it has never been easier...
question architecture jekyllElasticsearch is a best of breed search platform, but before you can search, you’ll need to import your documents. Being a .NET shop, we ...
search elasticsearchHappy New Year and Welcome back for another edition of Under the Decision Tree. Our weekly selection of machine learning articles, podca...
Machine LearningWe’ve made some good contributions to the world of open source this year. Our major projects are listed at our open source page. Stuntma...
OSS .NET npmOn our team TeamCity server we build repositories by default using build.cmd in the repository root. This has a few advantages.
One advantage is being able to run what TeamCity runs locally. It isn’t perfect – your machine can still be different from the TeamCity build agent. But, it allows running the same commands consistently. This can greatly improve the experience of debugging works on my machine issues.
Another advantage is keeping any complex build setup in the repository. Files in repositories are versioned and follow the familiar pattern of submitting changes via pull requests.
Here’s a simple build.cmd to get started (this one is useful for Node.js, but can be adapted for your needs!):
@echo Off
pushd %~dp0
setlocal
:Build
call npm install
call npm test
if %ERRORLEVEL% neq 0 goto BuildFail
goto BuildSuccess
:BuildFail
echo.
echo *** BUILD FAILED ***
goto End
:BuildSuccess
echo.
echo *** BUILD SUCCEEDED ***
goto End
:End
echo.
popd
exit /B %ERRORLEVEL%
In this case, the build will run call npm install and call npm test in order. You can modify these steps as necessary.
When creating a new build configuration for a project, a template can have build.cmd usage baked in. This consistency makes it faster and easier to setup a build configuration for new projects.
Team members can assume build.cmd will be ran for each TeamCity build. Having a consistent build script makes setting up new projects in TeamCity faster and easier, since executing build.cmd is included as part of a template. And, if a pull request fails to build unexpectedly a quick git clean -xdf and ./build.cmd can run what the build agent ran!
build.cmd enhances our team development experience by providing consistency.
Note: If build.cmd works locally and fails on a TeamCity build agent, this post won’t help you! :-)
