Zimbra

This repository contains the build script and supporting files required to create a FOSS build of the Zimbra Collaboration Suite. build.pl - Invoke this script to produce a build. See the Building section below for an example. instructions/ FOSS remote list.pl - Maps between remote label and URL FOSS repo list.pl - Specifies which branches (or tags) are checked out to build each component repository. FOSS staging list.pl - defines the staging order and details. Set up docker on your box You can then pull and run using development images (built from Zimbra/zm-base-os.git) In case you need to customize the images for your purposes, you could maintain your own Dockerfile such as this: $ cat Dockerfile FROM zimbra/zm-base-os:devcore-ubuntu-16.04 RUN sudo apt-get install emacs my-special-tool etc.. RUN ... The following steps assume that your are starting with a clean VM and are logged in as a non-root user with sudo privileges. sudo yum groupinstall 'Development Tools' sudo yum install java-1.8.0-openjdk ant ant-junit ruby git maven cpan wget perl-IPC-Cmd sudo yum groupinstall 'Development Tools' sudo yum remove java-1.7.0-openjdk java-1.6.0-openjdk ant sudo yum install java-1.8.0-openjdk java-1.8.0-openjdk-devel ruby git cpan wget install specific perl modules sudo cpan IPC::Cmd cd /tmp install maven wget sudo tar -xf apache-maven-3.3.9-bin.tar.gz sudo mv apache-maven-3.3.9 /opt echo 'export PATH="/opt/apache-maven-3.3.9/bin:$PATH"' sudo tee -a /etc/profile.d/maven.sh install current version of ant wget sudo unzip apache-ant-1.9.9-bin.zip sudo mv apache-ant-1.9.9 /opt echo 'export PATH="/opt/apache-ant-1.9.9/bin:$PATH"' sudo tee -a /etc/profile.d/ant.sh The build.pl command is used to build the product. Run it with the -h option for help: The completed build will be archived into a .tgz file that is stored in the appropriate platform and release-specific subdirectory of the BUILDS directory. The above command, run on an Ubuntu 16.04 machine, created the following: The following is a walk-through of the basic steps required to do ZCS development. The first step is to simply install a current FOSS build on the machine that you wish to use. The instructions that follow assume that this has been done. 3. Configure /opt/zimbra/.ssh/config to use your ssh key for the git remotes that you need to access. 4. Perform the following edits on /opt/zimbra/.bash profile Comment-out export LANG=C and export LC ALL=C . Add export LANG=en US.UTF-8 Add export ANT OPTS=-Ddev.home=/home/zimbra 5. Change permissions on files and folders that you will be updating; e.g., 8. Now you can clone any repositories that you require and get to work. As the zimbra user, cd /home/zimbra/zcs . Then clone the zm-mailbox repository from github The top-level build.xml is used by the zm-build scripts to create an installer package. You will not use that for normal development. There are build-order dependencies between the above-listed deployment targets. These can be determined by inspection of the ivy.xml files within each subdirectory. Here you can see that the deployment target, zm-store (the store subdirectory), depends upon common , soap , client , and native . Here is the current ordering dependencies among all of the zm-mailbox deployment targets. The higher-numbered deployment targets depend upon the lower-numbered ones. Note that milter-conf and store-conf have no cross-dependencies. Comments: The requirement to include -Dzimbra.buildinfo.version=8.7.6 GA to ant is due to a change that was made when the FOSS code was moved to GitHub. You can also just add that option to your ANT OPTS enviroment variable that you defined in $HOME/.bash profile as follows: If you do that, then you can omit that -D... argument to the ant command and future examples will reflect that. The publish-local target adds the artifact to /home/zimbra/.zcs-deps , which is included in the Ivy resolution path. The deploy target installs the artifact to its run-time locatio