Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319734 - If SVN goes down after build is started, build will fail before publishing is complete.
Summary: If SVN goes down after build is started, build will fail before publishing is...
Status: ASSIGNED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-13 10:40 EDT by Eric Gwin CLA
Modified: 2022-06-09 10:35 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 Eric Gwin CLA 2010-07-13 10:40:47 EDT 
This affects all active build branches (1.1.x, 1.2.x, 2.0.x, 2.1.x, and trunk:2.2.0). 

Due to the order tasks are called the build will run, test, and begin publishing when it fails (merging the new eclipselink and source jars). The jars are only merged to help with Testing.

To allow build to fully publish in case of SVN failure, the merge should be done last.
Comment 1 Eric Gwin CLA 2010-07-13 13:26:52 EDT 
Tested fix on oracle build machine, and passed cb. Will be watching closely tonight.

If successful, I will modify autobuild changes for use on the other active branches tomorrow.
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:35:47 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink