Hello,
Using the Jenkins build target, I noticed that the build process goes through building the SCAP content at least 3 times. It builds it once for `all`, once for 'dist`, and finally once for `validate`.
I wonder if this is by design? It would be nice to consolidate it down to building it once for a faster Jenkins run. Maybe the Jenkins target could be the following:
jenkins: clean all
instead of:
jenkins: clean all dist validate
This would greatly reduce Jenkins tests and the amount of time those tests are run.
Gabe
On 01/22/2016 05:07 PM, Gabe Alford wrote:
Hello,
Using the Jenkins build target, I noticed that the build process
goes through building the SCAP content at least 3 times. It builds it once for `all`, once for 'dist`, and finally once for `validate`.
I wonder if this is by design? It would be nice to consolidate it down to building it once for a faster Jenkins run. Maybe the Jenkins target could be the following:
jenkins: clean all
instead of:
jenkins: clean all dist validate
This would greatly reduce Jenkins tests and the amount of time those tests are run.
Gabe
Gabe,
Your observations are correct.
The problem is that current build system is a me^W^W complex. It builds the stuff fine. However, it is hard to make all the targets without repeating itself.
I have started way out of here during Christmas at
https://github.com/OpenSCAP/scap-security-guide/blob/master/shared/product-m...
As a result the XCCDF file (xccdf-unlinked-final.xml) builds only once. There is still a lot of work to be done though.
~š.
scap-security-guide@lists.fedorahosted.org