-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: NXP-8.x
-
Fix Version/s: NXP-8.x
-
Component/s: Continuous Integration
-
Epic Link:
-
Sprint:nxsupport 9.3.9
-
Story Points:2
Detects if nuxeo-jsf-ui package has to be released again.
This could use the same mechanism for making a diff between used libs. (see NXBT-1421)
The source folder should be nuxeo-distribution/nuxeo-nxr-jsf-ui
Based on the 3 generated files:
HF10_jsf_added.out HF10_jsf_deleted.out HF10_jsfmodified.out
If any of those files is not empty then it means there was a change and the package should be published again.
Publishing the package should consist in retrieving the newly built JSF package present in the current HF build job archived artifact.
- Retrieve the ZIP, for example at this location:
https://qa2.nuxeo.org/jenkins/view/Depl/job/Deploy/job/IT-release-on-demand-build-nx810/39/artifact/archives/mp-nuxeo-server-8.10-HF11/ - Uncompress the ZIP
- Retrieve from connect the latest JSF-UI published version (say 8.10.1) (request to be written and executed on the available packages)
- modify the package.xml:
- increase the version in
<package type="addon" name="nuxeo-jsf-ui" version="8.10-HF11">
- add a dependency directive on the current HF built:
<dependencies> <package>nuxeo-8.10-HF10</package> </dependencies>
- compress the ZIP
- upload the package ZIP to connect
- increase the version in
The upload has to happen after the current HF is available on connect since there is a dependency.
An alert should be sent to the support-team channel to make them aware of this.
- depends on
-
NXBT-1421 Compute the added/modified/deleted libs and deleted/added bundles
- Resolved