#2097: Jenkins test system should use generic.cfg where possible -------------------------+-------------------------------------------------- Reporter: hinder | Owner: hinder Type: enhancement | Status: new Priority: minor | Milestone: ET_2018_02 Component: Jenkins | Version: development version Keywords: | -------------------------+-------------------------------------------------- We now recommend using generic.cfg instead of OS-specific optionlists, so the Jenkins test system should do the same.
#2097: Jenkins test system should use generic.cfg where possible --------------------------+------------------------------------------------- Reporter: hinder | Owner: hinder Type: enhancement | Status: new Priority: minor | Milestone: ET_2018_02 Component: Jenkins | Version: development version Resolution: | Keywords: --------------------------+-------------------------------------------------
Comment (by hinder):
I will configure Jenkins to use generic.cfg for the current development version, and hard-code the use of ubuntu.cfg for ET_2017_05. I will also create a generic-opt.cfg with highly optimised gcc settings, and run a Jenkins job on it.
#2097: Jenkins test system should use generic.cfg where possible --------------------------+------------------------------------------------- Reporter: hinder | Owner: hinder Type: enhancement | Status: closed Priority: minor | Milestone: ET_2018_02 Component: Jenkins | Version: development version Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by hinder):
* status: new => closed * resolution: => fixed
Comment:
This has now been implemented.
trac@lists.einsteintoolkit.org
-
Einstein Toolkit