(Migrated) Building Zato packages with zato-build

(This message has been automatically imported from the retired mailing list)

Hello,

I’d like to introduce in a separate email a repository my colleagues use
for preparing pre-compiled Zato packages and build scripts.

  • deb, rhel6 and rhel7 contain scripts used for building either DEB or
    RPM packages,

  • meta contains the meta-installer, a set of Vagrant templates used for
    building the packages either selectively or all together - Vagrant is
    used to ensure that each package is built in its own system without
    influencing any other,

  • jenkins contains Jenkins jobs that automate build processes.

Unless someone is interested in build packages for all systems, using
deb, rhel6 or rhel7 alone will suffice.

Supposing one wishes to build a DEB package for Ubuntu 14.04 64-bit:

  • Install Ubuntu 14.04 64-bit

  • Clone the repository https://github.com/zatosource/zato-build/

  • cd ./zato-build/deb/

  • ./build-zato.sh master 2.0 label1

    • master - Zato branch on GitHub off which to build the package
    • 2.0 - version the package represents
    • label1 - any custom label to help identify the package
  • The result will be available in the same directory ./build-zato.sh is
    in - here it would be zato-2.0-label1_amd64-trusty.deb

Please note that the package needs to be built on the same system that
it’s being prepared for.

The process takes at least 20 minutes, depending on Internet
connectivity and disk I/O.

Hi,

That’s very useful!

Thanks.

On Tue, Nov 4, 2014 at 8:22 AM, Dariusz Suchojad dsuch@zato.io wrote:

Hello,

I’d like to introduce in a separate email a repository my colleagues use
for preparing pre-compiled Zato packages and build scripts.

https://github.com/zatosource/zato-build/

  • deb, rhel6 and rhel7 contain scripts used for building either DEB or
    RPM packages,

  • meta contains the meta-installer, a set of Vagrant templates used for
    building the packages either selectively or all together - Vagrant is
    used to ensure that each package is built in its own system without
    influencing any other,

  • jenkins contains Jenkins jobs that automate build processes.

Unless someone is interested in build packages for all systems, using
deb, rhel6 or rhel7 alone will suffice.

Supposing one wishes to build a DEB package for Ubuntu 14.04 64-bit:

  • Install Ubuntu 14.04 64-bit

  • Clone the repository https://github.com/zatosource/zato-build/

  • cd ./zato-build/deb/

  • ./build-zato.sh master 2.0 label1

    • master - Zato branch on GitHub off which to build the package
    • 2.0 - version the package represents
    • label1 - any custom label to help identify the package
  • The result will be available in the same directory ./build-zato.sh is
    in - here it would be zato-2.0-label1_amd64-trusty.deb

Please note that the package needs to be built on the same system that
it’s being prepared for.

The process takes at least 20 minutes, depending on Internet
connectivity and disk I/O.