Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.3
-
None
-
Jenkins
Description
Jenkins automatically generates a link toward the Maven generated site, which is available there:
http://builds.apache.org/job/sis-trunk/site/
However, in my understanding of JENKINS-6681, Jenkins does not use the mvn site:deploy goal for that purpose. Instead, it performs its own deployment (or simulates a deployment). Unfortunately sub-modules seem to have broken links. Our directory hierarchy is:
root ├── core │ ├── sis-utility │ ├── sis-metadata │ └── sis-referencing ├── storage │ ├── sis-storage │ └── sis-netcdf ...etc...
but Jenkins flattened everything like below:
root ├── core ├── sis-utility ├── sis-metadata ├── sis-referencing ├── storage ├── sis-storage ├── sis-netcdf ...etc...
Consequently there is no way to reach any sis-* module from the links created by Maven. This issue seems to be related to the following discussion:
As a workaround, we could deploy the site on some server using the standard mvn site:deploy goal. But which server?