Here are steps for generating packages and installers, making them available for download.
Nuxeo Packages
Nuxeo Platform (CS, CAP, DM)
ZIP
The ZIP is produced by IT-nuxeo-5.4-build (or IT-release-on-demand-nuxeo-5.4-build) and pushed to the given UPLOAD_URL if IT-nuxeo-5.4-tests-dm-tomcat (or IT-release-on-demand-nuxeo-5.4-tests-dm-tomcat) succeeds.
This is part of the release process.
IzPack (.jar, .app, .jnlp, .exe)
Run IT-nuxeo-5.4-build-izpack with parameters:
- NXVERSION
- ZIP_DIR: set a path to use local archives, else they will be retrieved from Maven repositories.
- CODEBASE_URL: for use by JNLP
- UPLOAD_URL
This is generating the jar, app, jnlp and exe installers.
NSIS (.exe)
Run IT-nuxeo-5.4-build-windows with parameters:
- LASTBUILD_URL: Jenkins job's URL for downloading artifact to package
- UPLOAD_URL
Debian
Run IT-nuxeo-5.4-build-debian with parameters:
- VERSION
- ARCHIVE_URL_JBOSS
- ARCHIVE_URL_TOMCAT
Debian packages are uploaded to the Nuxeo APT repository.
RPM
Currently not available.
VMs
Addons
Think about building Nuxeo Packages for released addons and publishing them on Nuxeo Connect.
Nuxeo CMF
ZIP
Unzip, chmod +x *.command bin/`.sh bin/*ctl bin/.command`, re-zip.
Upload to nuxeo@styx:/var/www/www.nuxeo.org/static/staging/cmf-${version}/ and generate md5 checksums.
Download from http://community.nuxeo.com/static/staging/cmf-${version}/, test and validate.
If ok, move from cmf-${version}.tmp to cmf-${version}.
IzPack (.jar, .app, .jnlp, .exe)
Script is not enough generic for now. Here's a patch for using https://github.com/nuxeo/nuxeo-distribution-izpack with CMF:
Then, steps for generating the jar, app, jnlp and exe are similar as for Nuxeo EP.
NSIS (.exe)
Debian
Debian packages are uploaded to the Nuxeo APT repository.
RPM
Currently not available.
VMs
Nuxeo DAM
ZIP
IzPack
NSIS (.exe)
Debian
Debian packages are uploaded to the Nuxeo APT repository.
RPM
Currently not available.