This is a job to maintain builds of OVA image as well as to publish them on NAS (and remove older to keep sane amount of drive storage). false false false false OSIMAGE_DISTRO Our directly developed product can be bundled into OS images based on various third-party OS distributions. Pick the flavour here. true NoFilter OSIMAGE_DISTROS IMAGE_PREFIX Part of the filename leading up to IMAGETYPE and IMAGE_SUFFIX and finally IMAGEVERSION number/tag. Usually correlates with IMGTYPE used to build the OS image. true NoFilter CompletedUnstable fty-arm-ova fty-master-ova IMAGETYPE Type of OVA image to be built. Correlates with IMGTYPE used to build the OS image. devel deploy IMAGE_SUFFIX "-image" for fty* builds, empty (or a couple of quote characters) for IPM_Infra and IPM_Editions* true NoFilter CompletedUnstable -image '' IMAGE_DIR Optional directory name for hosting the image type (its branches and arches). If empty, is deduced from prefix+type+suffix e.g. "featureimage-bigdevel-image" or "IPM_Editions-va" (empty suffix). true IMAGEVERSION SquashFS image name without prefix, type and suffix like "16.08.04-10.28.57-2_x86_64" or "1.4+123". The default value of "CURRENT" will try to find the latest build matching the other parameters. CURRENT false FEATURE_BRANCH Feature branch (upstream), QA level (master, arm), or release number name (1.4) - subdirectory on NAS for squashfs image storage true NoFilter CompletedUnstable arm 1.4 upstream Test master 1.5.0 CPUCOUNT Number of CPUs allocated for OVA appliance. 2 false MEMSIZE Size of memory allocated for OVA appliance. Units are MB! 4096 false BB_REPO_FORK GIT Repo with boot-loader codebase, a fork of ssh://git@bitbucket-prod.localdomain:7999/BIOS/bios-boot true NoFilter Triggered BB_REPO_FORK BB_REPO_BRANCH refs/remotes/origin/master false BB_REPO_REFSPEC Default (empty) is ok for usual builds; can be customized for e.g. PR builds. false FIX_COMPATIBILITY Fix compatibility for Virtual Box? true SANITYCHECK_ALLOW_OVERWRITE If set (is not by default) allow replacing an existing file on NAS. Should be constrained to custom rebuilds while experimenting (with non-standard CPU and RAM variables). false SANITYCHECK_ALLOW_MKDIR Normally this job requires that target directory exists and is usable. For experiments, new releases and feature branches, one can force creation of those. false CUSTOM_IMAGE_URL Custom image URL, assumed to be on the NAS and served from relative paths from OBS or Tomcat on the web. If this parameter is used, it overrides the common components of image file name and location defined above and used to construct such an URL for the standard builds. The resulting appliance would be published to the same directory as the OS image. true CUSTOM_OVALOADER_URL Do not build an OVA loader from scratch according to BB_REPO settings, but re-use one from the URL true CUSTOM_EMPTYOVA_URL Do not build an OVA from scratch according to BB_REPO settings, but re-use one (including its loader disk image) from the URL. Can be mixed with CUSTOM_OVALOADER_URL. false 1 4 true project true 1 job-info true false last-saved true false time true false 1605094803155 UTC false user true false display-name true false SYSTEM full-name true false SYSTEM 2 ${BB_REPO_REFSPEC} ${BB_REPO_FORK} a4cb8b58-30ab-4914-a306-6ba4567890b2 ${BB_REPO_BRANCH} false false false /home/abuild/jenkins-gitcache 0 false bios-boot 2 https://github.com/42ity/fty-core.git 955c217d-8133-41c2-9235-901234567ca6 */master false false false /home/abuild/jenkins-gitcache 0 false fty-core ova-build false false false false (System) thisIsTheToken true false ./prepare-ova.sh 42 **/config.xml true false false true true true ALL false false false false false ONLY_CONFIGURATIONS ./cleanup-build-dir.sh true