Sponsored Content
Top Forums UNIX for Advanced & Expert Users Continous Integration for Unix / Linux Post 302155508 by +Yan on Friday 4th of January 2008 08:16:31 AM
Old 01-04-2008
Continous Integration for Unix / Linux

Hi all,
We have serious problem with continuous integration system for application building on few different platforms.
(aix 5.2, 5.3 solaris 8,9 , SUSE Linux 9.3, 10 , Slackware Linux 10,11,12, RedHAt Enterprise Linux и Windows 2003)
We need application ( program ) to do the following tasks:
- Automatically start build process and it's tests at desired time.
- Option for manual build invocation
- One build process at a time (The build process shall not be started for the second time before it is over).
- Write log file with all console messages.
- email notifications.
- conditional start of different builds i.e. if build one finishes with success, then start build tree.
- Web interface to control all configurations from single machine.
We use Makefile, ant to build our applications, and bash / perl scripts to prepare the build process.
We use CVS to control source code.

At the moment we are using this:
CruiseControl Home but it is not very useful for our needs.
We cannot afford to write our own building application. Using crontab is not good option.

Thank you in advance.

Last edited by +Yan; 01-10-2008 at 08:49 AM..
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

HSBC Payment Integration on Unix

Hi I'm hoping someone can help a complete *nix amatuer here. I've been asked to implement HSBC payment integration for a client. HSBC supply (amongst others) Linux and Windows libraries, and I've been asked to see if we can implement this on our dedicated Unix host. Basically the system... (5 Replies)
Discussion started by: elkdanger
5 Replies

2. UNIX for Dummies Questions & Answers

To remove Continous blank spaces from a file in UNIX

All... I want to remove blank spaces in file . I just leraned that we can use " cat <Input filename> | tr -s ‘ ‘ > <Target file name> " i also know with SED we can replace a blank space by other character by sed s/ /*/g filename. Please let me know how can i do that by... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies

3. UNIX for Dummies Questions & Answers

Help required Unix and Web page Integration.

HI guys , I want to create a simple website which can communicate with unix server. For example i want to run some command on a unix server through a website. What will be the best approach to do the same. Kindly help . (2 Replies)
Discussion started by: pinga123
2 Replies

4. Programming

Linux and Php integration help .

I m devoloping a website which communicate with Linux server . Whenever a page is loaded it runs one script on Linux server. My problem is a simple commands like date , ls runs very smoothly. But whenever i execute big script.It wont display the output. My knowledge of PHP is very less i m... (2 Replies)
Discussion started by: pinga123
2 Replies
build(1)						      General Commands Manual							  build(1)

NAME
build - build SuSE Linux RPMs in a chroot environment SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm] build --help build --verify DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc- tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec file for example), even if the package does not use BuildRoot. build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec- tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be sufficient for the build. If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current directory. OPTIONS
--clean remove the build system and reinitialize it from scratch. --no-init skip the build system initialization and start with build immediately. --list-state list rpms that would be used to create a fresh build root. Does not create the build root or perform a build. --rpms path1:path2:path3... Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari- able. --arch arch1:arch2:arch3... What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify this option. --root buildroot Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable. --useusedforbuild Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the same packages used for the srcrpm build. --norootforbuild --help Print a short help text. --verify verify the files in an existing build system. .spec FILE OPTIONS The build command interprets some special control comments in the specfile: # norootforbuild # needsrootforbuild build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2, the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec- tively. # needsbinariesforbuild provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root. ENVIRONMENT
BUILD_ROOT The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default. BUILD_RPMS Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value which will do the trick if you have the SuSE Linux DVD mounted. BUILD_RPM_BUILD_STAGE The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip- tions. "-ba" is the default. You can use this to add more options to RPM. SEE ALSO
rpm(1), Maximum RPM: http://www.rpm.org/max-rpm/ cross distribution packaging: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to SUSE packaging standards and guidelines: http://en.opensuse.org/Packaging (c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)
All times are GMT -4. The time now is 04:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy