-
Type: User story
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.3.1107
-
Component/s: Packaging / Build
-
Epic Link:
-
Sprint:Sprint Drive 5.9.4-2, Sprint Drive 5.9.5-1, Sprint Drive 5.9.6-1
-
Story Points:5
After NXP-13815
The Jenkins chain will need to be updated to have a release job that will at least:
Set the right version in the client code
Tag the repository (there we need to think about separating the Java server project and Python client one in 2 distinct Github repositories, and have a dedicated JIRA project for Drive with specific versions)
Trigger both msi and dmg frozen apps
Trigger IT jobs under the 3 platforms using the previously frozen apps
If OK publish the releases to the update site and update the index with a new line
- depends on
-
NXDRIVE-146 Code sign ZIP update packages
- Resolved
-
NXDRIVE-335 Use virtualenv for FT jobs
- Resolved
-
NXP-14919 Drive: split the nuxeo-drive GitHub repository into 2 repositories: Python client and Java server addon
- Resolved
-
NXDRIVE-28 Cleanup build file: setup.py
- Resolved
-
NXP-13815 Drive: set up Drive update site, versioning policy
- Resolved
- is required by
-
NXDRIVE-7 Update Github DEVELOPERS doc with a section about Esky and the whole application update system
- Resolved
-
NXDRIVE-9 Write and test different update scenarios
- Resolved
-
NXDRIVE-15 Stop synchronization if no compatible version is available from update site
- Resolved
-
NXP-13825 Drive: allow client-server compatibility functional tests
- Open