Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313898 - [BUILD_SCRIPT] EPP package build depends on EPP repository build
Summary: [BUILD_SCRIPT] EPP package build depends on EPP repository build
Status: RESOLVED FIXED
Alias: None
Product: EPP
Classification: Technology
Component: Packager (show other bugs)
Version: 1.3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.3.0 RC2   Edit
Assignee: Markus Knauer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-21 07:34 EDT by Markus Knauer CLA
Modified: 2010-05-22 09:56 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Knauer CLA 2010-05-21 07:34:31 EDT 
The EPP build consists of two 'independent' jobs:

# build an EPP p2 repository with the package definitions (product, feature, bundles)
# run the p2 director to build the packages (see startEPP36.sh)

At the moment, startEPP36.sh is using the p2 repository created in the first job, but if the first job is re-executed while the second job is being performed, an error occurs because the input p2 repository is renewed on the fly. Usually this is prevented by the lock mechanisms in Hudson, but from time to time this is inappropriate.

It would be better if the second step could create a local copy of the repo for its own operations. With this copy in place it could operate independently from the first job.
Comment 1 Markus Knauer CLA 2010-05-22 09:56:36 EDT 
start36.sh now uses its own copy of the EPP repository from the first step.