build-automation

On a recent project I have been working on in C#/ASP.NET I have some fairly complicated JavaScript files and some nifty Style Sheets. As these script resources grow in size it is advisable to minify the resources and keep your web pages as light as possible, of course. I know many developers who hand-feed their JavaScript resources into compressors after debugging and then deploy their applications. When it comes to source control and automated builds in the satisfying world of continuous integration (thank you CruiseControl.NET ); hand compression will simply not do. The only way to maintain

I'm completely at loss how the ant task ivy:publish is supposed to work. I would expect that I do my normal build, which creates a bunch of jar files, then I would push those jars to the (local) repository. How can I specify from where to retrieve the built jars, and how would those end up in the repository? Update: <target name="publish-local" description="--> Publish Local"> <ivy:retrieve /> <ivy:publish resolver="local" pubrevision="${release.version}" status="release" update="true" overwrite="true"> <artifacts pattern="${dist.dir}/[organisation]-[module].[ext]" /> </ivy:publish> </target>

I'm maintaining a quite large legacy application. The source tree is a real mess. I'm trying to set up a build server. On the source tree, I've third party component with sources (also in the project's include path). These components are also installed within the IDE. My question is : How to manage those components ? I thought to manage this way: Install the IDE on the build server Install all the third party component Remove the component sources from the project sources tree (and keep them on the project root on a dedicated folder each zipped) Each time we need to customize (or debug) a

So I'm trying to convert all of my ant build scripts to gradle, and I've been able to find ample resources and documentation on all of it except how to configure signing in the gradle.properties file. ant.properties does it like so: key.alias=alias key.store.password=password key.store=keystore.file key.alias.password=password But how do I do the same in gradle? Xavier Ducrohet In your gradle.properties file store the same values as in the ant.properties file, I think you'll have to do simpler names, like keyAlias for instance. Just remove the dots to be sure. then in your build.gradle file do

This is my first try with cmake and I would like to have, if possible, some feedbacks about what I did since some problems remain. In the CMakeLists.txt of the library folder, I created two makefile targets: configure-antlr3c and antlr3c . The first target runs the autotools configuration shell script, the second one runs the make executable to build the library: # CMakeLists.txt in libantlr3c-3.1.3 add_custom_target( configure-antlr3c ${SHELL_EXECUTABLE} configure WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR} ) add_custom_target( antlr3c ${MAKE} DEPENDS configure-antlr3c WORKING_DIRECTORY $

I'm looking to setup an automated nightly build server for our iphone apps, and looking for advice on what works and what doesn't. Basically, something that at least nightly runs all the unit tests and publishes a new adhoc build to our internal website. All the developers use laptops (which'll be off overnight), so I'm considering getting a dedicated Mac Mini to do this. I'm not sure if I should get standard Mac OS X or the server edition. At least for the first attempt, I'm considering just using a simple shell script run from a crontab to do the actual work. In the future a full continuous

Rake is a software build tool written in Ruby (like Ant or Make ), and so all its files are written in this language. Does something like this exist in Python? Ned Batchelder Paver has a similar set of goals, though I don't really know how it compares. Invoke — Fabric without the SSH dependencies. The Fabric roadmap discusses that Fabric 1.x will be split into three portions: Invoke — The non-SSH task execution. Fabric 2.x — The remote execution and deployment library that utilizes Invoke . Patchwork — The "common deployment/sysadmin operations, built on Fabric." Invoke is a Python (2.6+ and 3

In Xcode, I know that you can get variables such as PROJECT_DIR to use in some situations, such as a run script build phase. I am wondering if it's possible to get the build type (i.e., Release or Debug ). Any ideas? smorgan The best source is probably Apple's official documentation . The specific variable you are looking for is CONFIGURATION. Here's a list of the environment variables . I think you might want CURRENT_VARIANT . See also BUILD_VARIANTS . 来源： https://stackoverflow.com/questions/890569/xcode-variables

We are doing a web application with AngularJS and we like the idea of using Bower for Dependency Management and Grunt for building, running tests etc. ( Yeoman ) The server is done with Java using Maven, so of course we would like with a simple mvn install build everything (web application + server) So what approach you took and why? 1) Treat them as two different applications, which in fact they are. So using different building methods/tools is acceptable. 2) Forget about Grunt Bower, use Maven plugins to build, run tests, manage dependencies for the web application. If that is the case,