Bug 454255 - eclipse-repository may have missing artifacts after a successful build
Summary: eclipse-repository may have missing artifacts after a successful build
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 378794
Blocks:
  Show dependency tree
 
Reported: 2014-12-05 10:05 EST by Tobias Oberlies CLA
Modified: 2021-04-28 16:51 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Oberlies CLA 2014-12-05 10:05:06 EST
This is a more general bug description of e.g. the situation described in bug 378794: In certain conditions, p2 repositories built by eclipse-repository are inconsistent: they contain IUs but the artifacts referenced by the IUs are not there.

The build does not fail in this situation. To make things worse there may not even be a warning if for some reason (e.g. the snapshot issue discussed in bug 416543 comment #9) the source artifact repositories don't matching have IArtifactDescriptors. The reason are the following p2 Mirroring lines

   IArtifactDescriptor[] descriptors = source.getArtifactDescriptors(key);
   for (int j = 0; j < descriptors.length; j++) ...
Comment 1 Tobias Oberlies CLA 2014-12-08 06:16:17 EST
The workaround for this problem is to configure the verify-repository [1] goal, which checks for missing and broken artifacts.

[1] https://www.eclipse.org/tycho/sitedocs/tycho-p2/tycho-p2-repository-plugin/verify-repository-mojo.html
Comment 2 Mickael Istria CLA 2021-04-08 18:14:36 EDT
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse/tycho/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.