The Crossplex package of make macros simplifies the creation of embedded systems, and is powerful enough for large organizations to use for developing elaborate product lines. It allows you to organize many different products under a logical structure, making systems of any complexity easy to specify. When you have many different target platforms, each with multiple different software configurations, Crossplex keeps those configurations from stepping on each other, without requiring redundancy in your source tree. Crossplex allows you to use a single dependency tree encompassing both in-house software and third-party packages, and it is particularly suited to build automation. Crossplex makes it easy to shield your build from the host environment, setting all shell variables explicitly, and giving you complete control over the path that is used at any point in the build. This is nice when you want to support building on a variety of development platforms. Crossplex scales to your needs. You can dabble in the unpacking and patching features as you need them, or you can base your entire system from the ground up on the Crossplex framework. Crossplex supports creation and use of glibc and uClibc toolchains.
instmake allows you to instrument builds with GNU Make and then analyze what happened during those builds. It saves a very detailed build log and has reports to analyze those records. The reports provide you better insight into the build, allow you to find race conditions, and to analyze the parallelism of the build.
The maven-buildmetadata-plugin is a Maven 2 plugin that helps you easily add build metadata to generated archive artifacts. When a product is running on an application server, this tool can tell you which version of which artifact is currently running on that server, which artifact maps to which source code version in the SCM repository, what configuration set (including profiles and environment variables) has been used to generate the artifact, on which machine was the artifact built, and when was the artifact built. The provided metadata include SCM information, build time, operating system, Java runtime, Maven execution information, build user, build host name, and build version.
EBuild is a software project build, dependency management, and reporting technology. The aim is to be able to tackle any build problem in a structured, declarative, and elegant way. It is written in Java, but can be used to build all manner of projects and is extensible via a plugin interface. It is best compared to something like Maven (and in some respects Ivy). It aims to overcome certain design flaws and the resultant unnecessary complexity. The EBuild build model is general, but plugins need to be written in a JVM compatible language. Existing plugins all deal with the Java ecosystem, so EBuild is most suitable for Java and mixed technology software projects.
Lattice is a Java build system with strong multi-module support. Build files are written not in XML, but in the Python language. The benefits are much better readability and powerful imperative build scripting. For multi-module projects, Lattice uses topological sorting to decide the correct order to build each module. Because a custom task is just a regular Python function, they can perform any type of work, including invoking other Java build systems such as Ant, Maven, or Ivy.
TMake is a fast, lightweight, yet very powerful Build System. You can use TMake to build projects or create new ones. It supports C, C++, C#, Java, and Go compilers and over 100 different packages. It can perform C and C++ dependency checking. It is very fast. It uses for Lua for plain and simple build scripts. It has a GUI.
CI-Eye is a powerful continuous integration build radiator requiring no installation and almost no set-up. CI-Eye talks to many different CI servers through their REST APIs (so no plug-ins are required). Currently, support is offered for Hudson, Jenkins, and TeamCity. CI-Eye runs as a standalone Web application.