SAP use CBS for there continuous integration builds. To use another tool you have to get a command line build working.
The Development components are built with ANT but the build.xml file is generated each time. Therefore there is no pure ant build. However this info from the Netweaver Help looks promising but I could not get it to work, and gave up after a couple of hours of messing about. I fixed the script and classpath problems... but when I got to the stage where I had to import the whole "Development Configuration" and decided that it was getting too complex and hard to be useful.
If you can get it to work please post a HowTo. A few command line examples of builds would be great.
Doug
SAP NetWeaver CE Developer Studio Documentation > Developer's Guide > Using the Development and Production Infrastructure > Working with the Development Infrastructure > Concepts > Development Scenarios with Development Infrastructure > Using Third Party Development Infrastructure
"
Using Command Line Tool
You can use the command line tool to run an automated build on a collection of DCs that belong to a certain development configuration or if you do not have your own build infrastructure with a build engine. The commands it provides can be easily integrated into shell scripts, or run interactively. Furthermore, when run on a collection of DCs, the command automatically determines the correct build sequence. Therefore it can be treated as a simple, but complete build engine for the production of whole software products. The development configuration determines which development components and which versions of that development component are built together in the same context.
All SAP build plug-ins store logs and build results for each component that has been built in the /gen directory inside the components root directory. You can make these logs and build results available for further use. For more information about how to structure your folders in this directory, see Structure of the GEN Folder.
Requirements
The build command requires that all used build plug-ins, used libraries and the source files of the DCs you want to build are already available in the local file system. The corresponding locations must be set to the command using the command’s parameters. You have to first set up this environment. You have to retrieve the source code from the version control system, copy the used libraries from the build environment, define a suitable file system layout and so on. For the automated build, you have to integrate these tasks as additional steps in the build script before executing the build command.
Using ANT Build Task
SAP provides a generic ANT task that can be used to embed the build of components into any ANT make script. Since ANT is a standard for Java build technology, and is supported by many frameworks, it is possible to integrated the build of SAP components into a wide variety of build environments.
Requirements
The ANT build task requires that all used build plug-ins, used libraries and the source files of the components you want to build are already available in the local file system. The corresponding locations must be set to the command using the command’s parameters. You have to first set up this environment. You have to retrieve the source code from the version control system, copy the used libraries from the build environment, define a suitable file system layout and so on. For the automated build you have to integrate these tasks as additional steps in the build script.
Composition Environment Command Line Tool
Use
This command line tool is intended only for SAP NetWeaver 7.1 Composition Environment (CE). You should not use it with other SAP NetWeaver 7.0 environment(s).
The SAP NetWeaver Composition Environment command line tool (CECLT) is an add-on to the NetWeaver Developer Studio. Using the CECLT, you can build and package development components (DCs) and SCAs files. You can use the command line tool to run an automated build on a collection of DCs that belong to a certain development configuration or if you do not have your own build infrastructure with a build engine. The commands it provide can be easily integrated into shell scripts, or run interactively. Furthermore, when run on a collection of DCs, the command automatically determines the correct build sequence. Therefore it can be treated as a simple, but complete build engine for the production of whole software products. The development configuration determines which components and which versions of that component are built together in the same context.
All SAP build plug-ins store logs and build results for each component that has been built in the /gen directory inside the components root directory. You can make these logs and build results available for further use. For more information about how to structure your folders in this directory, see Structure of the GEN Folder.
Requirements
The build command requires that all used build plug-ins, used libraries and the source files of the DCs you want to build are already available in the local file system. The corresponding locations must be set to the command using the command’s parameters. You have to first set up this environment. You have to retrieve the source code from the version control system, copy the used libraries from the build environment, define a suitable file system layout and so on. For the automated build, you have to integrate these tasks as additional steps in the build script before executing the build command.
Starting the tool
The CECLT is installed in the folder <Developer Studio install dir>eclipse\tools\nwcetool. The required environment variables have to be set as described in readme.txt before the tool is launched. The tool runs in an interactive mode where you can enter commands sequentially. The command help provides an overview of the existing commands.
"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.