I am trying to figure what process a project should employ to validate that an about-to-be-released simrel repository indeed contains project's final contribution.
For instance, I am trying to verify Sapphire's contribution to Juno SR1 before aggregation locks down for the quiet week later today. On Hudson, I see the relevant commit has cleared through the aggregator job [1], but the Hudson job does not archive its result, so I cannot check it there. The listed staging repository URL [2] appears to be manually updated and doesn't include the change in question. Suggestions? Is the current process to request an update of the staging repository? Would it be possible to modify the aggregator job to archive the result of aggregation? The retention of bits can be configured to one or two runs to keep disk usage down. If we had this, one could always access the latest aggregator result from Hudson [3] and there wouldn't be a need to manually maintain the current staging repositories. - Konstantin [1] https://hudson.eclipse.org/hudson/job/simrel.juno.runAggregator/ [2] http://download.eclipse.org/releases/maintenance/ [3] https://hudson.eclipse.org/hudson/job/simrel.juno.runAggregator/lastSuccessf ulBuild/artifact/repository
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
