| Re: [eclipselink-dev] EclipseLink Update Compdeps fails |
Hi Will,sorry, but this job wasn't migrated into new Eclipse.org build (cloud based) infrastructure. Because in the new Jenkins there is no persistence store to keep files across builds. Directories like /opt/public/rt/eclipselink or /home/data/httpd/archive.eclipse.org/rt/eclipselink must be populated every time, when job is started/ended.
In 2.7 branch build job during a start download dependencies see: https://github.com/eclipse-ee4j/eclipselink/blob/2.7/etc/jenkins/build.groovy https://github.com/eclipse-ee4j/eclipselink/blob/2.7/etc/jenkins/init.sh and compilation dependencies are prepared https://github.com/eclipse-ee4j/eclipselink/blob/2.7/buildsystem/compdeps/pom.xml At the end it uploads results with https://github.com/eclipse-ee4j/eclipselink/blob/2.7/etc/jenkins/publish_nightly.shThe simplest solution could be just on the beging of the job via scp,http (wget) download/populate all required directories and at the end push via scp results to the Eclipse.org download server (before migration mounted as /home/data/httpd/archive.eclipse.org/rt/eclipselink directory).
Thank You Radek Felcman On 12/12/19 8:38 PM, William Dazey wrote:
Hello! We recently have been working on updating EclipseLink for ASM 7.2, but we are hitting an issue running the compdeps build for 2.6_WAS! Does anyone have access/experience with this?https://ci.eclipse.org/eclipselink/job/eclipselink-update-compdeps/54/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__ci.eclipse.org_eclipselink_job_eclipselink-2Dupdate-2Dcompdeps_54_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=OUs7j4cNH6SfkQnqG1ZWFHkOXrqXJqlkLTBBNve2ne8&m=qZBec4o8a4xcGaW3WGsSZMmIHAX0k168iGLGopR2bwo&s=lyRQAJ8rvH5_4nAkcHgvGdtSbX11Izgy-s-Jz9s4Q1c&e=>Thanks, Will Dazey