[
https://issues.jboss.org/browse/JBDS-1473?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-1473:
-------------------------------------
Yes, for p2 enabled product build I moved final update site to
jbds-build/site/nightly/${version} to get it picked up by devstudio-nightly.sh script.
Thats why it is published in locations you mentioned in [3] and issue is fixed.
[0] is useless for p2 product if "Help" -> "Check for Updates ..."
is used. [0] doesn't contain com.jboss.jbds.all feature and p2 product is not able to
find updates from it.
Publish p2 product update site created during nightly product build
-------------------------------------------------------------------
Key: JBDS-1473
URL:
https://issues.jboss.org/browse/JBDS-1473
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: Build, P2 Enabled Product
Affects Versions: 4.0.0.CR1
Reporter: Denis Golovin
Assignee: Denis Golovin
Priority: Blocker
Fix For: 4.0.0.CR1
Every nightly product build creates p2 repo which is literary the update site that can be
used to update previously installed p2 enabled JBDS.
Example of location this p2 repo in build results is
http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4....
It should be published and available from static location so QA can use this URL to
verify update. This URL could be
http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4....
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira