build-automation

I have the following directory structure (only showing the relevant bits for illustration purposes): proj \ \ Gruntfile.js \ package.json \ test \ (all my tests are in this folder structure) \ app \ \ index.html \ scripts \ (all my scripts are in here) \ views \ (all views are in here) \ styles \ \ style.css \ oldie.css \ print.css \ images \ \ hires \ (all high resolution images are here) \ lowres \ (all low resolution images are here) The compass section of my Gruntfile.js file looks like this: compass: { options: { require: "susy", sassDir: '<%= my.app %>/styles', cssDir: '.tmp/styles',

I'm looking for a tool I can use via command line (windows 7) to merge two equally sized pngs. I'm not having much luck with search so far as most tools I've seen are pretty heavy applications which don't seem to target simple manipulations. I want to overwrite the bits in the opaque base image with the non-transparent pixels in the overlay image. I have photoshop CS4 as well, but haven't had much luck in finding the relevant command line arguments. ImageMagick has a command line tool called composite which will do what you want. Distributions available for Windows, Mac, Linux etc. I've just

Does anybody know how can I configure TFS Build to build a set of projects in a solution instead? The solution I have, has 16 projects but for one of my build definitions I want some of them to be compiled. The easiest way in my opinion is to create a new solution file. There is nothing stopping you from having several solutions that reference the same projects (or some subset). The other way is to create a new configuration. In Solution Explorer, rightclick the root node -> Configuration Manager. In addition to standard configs like "debug" or "release" you can create your own custom ones.

I would like to have TeamCity Artifacts be checked back into source control. I have used TFS Integrator before. So I am used to its approach where, through config, it can check in the output builds back into source control. Then when people do a get they will receive these artifacts. Or is there a completely different way of achieving this with TeamCity? The two ways I can think of are VCS Labeling specify a path in your working directory to label and the location relative to the trunk to check it in. jetbrains explains it here /project/trunk/dist=>/project/tags/%system.build.number% from the

for some time my company is now using Maven and TeamCity to build Java stuff. Currently we are investing quite heavily in continuous integration and ultimately continuous delivery. Among many smaller applications (apps) we are operating one big monolith app with approx. 1 million LOC. This app on quite a big build agent takes 5 minutes to compile (incl. 2 minutes svn up). Its 12k unit tests are running for another 5 minutes. Deploying the build results to Nexus takes at least 10 minutes. To provide fast feedback to developers we try to split the the amount of work to be done in different build