Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 521310

Summary:	[Papyrus] Mirroring problems during publish
Product:	Community	Reporter:	Quentin Le Menez <quentin.lemenez>
Component:	Servers	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	quentin.lemenez
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Quentin Le Menez

2017-08-23 08:31:14 EDT

Hi,

Upon publishing the latest papyrus releases I found out that when some of the artifacts were fetched during the installation the installer was automatically redirected to a mirror that does not yet contain the file. This is problematic as it breaks the installation process with "artifacts not found" errors.

Is it due to some forgotten variable/step on my end ?

Thanks,
Quentin

Ps: this may be related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=516754

Comment 1 Quentin Le Menez

2017-08-23 09:17:51 EDT

I did not see it at first but this bug may also be related to the previous: https://bugs.eclipse.org/bugs/show_bug.cgi?id=520252

Comment 2 Eclipse Webmaster

2017-08-23 14:18:14 EDT

This does sound like you didn't wait enough time for the artefacts to be picked up by mirrors.

Bug 520252 should help with this so I'm going to close this as the update has been submitted.

-M.

Comment 3 Quentin Le Menez

2017-08-24 03:17:25 EDT

It does indeed seems to work today (mirrors must have been populated).

I had a question about that however, as I did not find any reference to it on the interwebs: what is the delay between a mirror being assigned to the artifact and the time the mirror is actually populated ? As I understand Bug 520252 it seems that it should not be mirrored before the 3rd hour is that correct ?

I am asking that because we had that same trouble when we tried to publish nighties, replacing them every morning, that failed to install because of "artifacts not found" errors.

Comment 4 Eclipse Webmaster

2017-08-24 09:51:18 EDT

Since we don't control when mirrors update, and we don't have a 'managed' download object tool, we make certain assumptions about what the availability of any given file.  We tend to test for mirror 'freshness' by downloading a random selection of files, and tracking the success rate over time.  Past a certain point the mirror doesn't contain enough new stuff and is delisted.

-M.