Bug 321674 - Upload platform/filetransfer feature integration build to archive.eclipse.org instead download.eclipse.org
Summary: Upload platform/filetransfer feature integration build to archive.eclipse.org...
Status: CLOSED FIXED
Alias: None
Product: ECF
Classification: RT
Component: ecf.releng (show other bugs)
Version: 3.3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.4.0   Edit
Assignee: Markus Kuppe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 315727 (view as bug list)
Depends on:
Blocks: 321676
  Show dependency tree
 
Reported: 2010-08-04 03:51 EDT by Markus Kuppe CLA
Modified: 2010-10-25 12:58 EDT (History)
2 users (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 Kuppe CLA 2010-08-04 03:51:13 EDT 
I-HEAD-platform.feature build should not be uploaded to download.eclipse.org to keep it from being mirrored (worldwide). The only platform.feature consumer is the Equinox team that accesses archive.eclipse.org
Comment 1 Markus Kuppe CLA 2010-08-04 03:52:34 EDT 
Adding Kim as she knows if this has any implications for Equinox/Platform.
Comment 2 Markus Kuppe CLA 2010-08-04 04:38:30 EDT 
*** Bug 315727 has been marked as a duplicate of this bug. ***
Comment 3 Kim Moir CLA 2010-08-04 10:12:10 EDT 
They're not currently mirrored worldwide.  Denis has an exclude list so the only builds that are sent to the mirrors are milestone and release builds.
Comment 4 Kim Moir CLA 2010-08-04 10:45:01 EDT 
Again, I thought this was an platform releng bug when it's an ECF bug. So I'm going to remove myself from this bug.  Not sure how ECF mirrors their content, will leave it up to them to comment.
Comment 5 Scott Lewis CLA 2010-10-18 14:20:41 EDT 
Closing this bug.  What really needs to happen is that a bug needs to be opened against platform releng (rather than ECF) to consume ECF filetransfer bundles in a completely different way (rather than us uploading to either download or archive).
Comment 6 Kim Moir CLA 2010-10-25 10:02:53 EDT 
I'm not sure if I understand comment comment #5.  How are we supposed to consume your bundles if they don't reside in a public repository? Download.eclipse.org and archive.eclipse.org are public repositories where we consume bundles from other eclipse projects.  Could you clarify?
Comment 7 Markus Kuppe CLA 2010-10-25 12:58:38 EDT 
(In reply to comment #6)
> I'm not sure if I understand comment comment #5.  How are we supposed to
> consume your bundles if they don't reside in a public repository?
> Download.eclipse.org and archive.eclipse.org are public repositories where we
> consume bundles from other eclipse projects.  Could you clarify?

What Scott means is the dedicated platform feature that is only consumed by p2. He is not talking about where the bits are made available from.