Community
Participate
Working Groups
The categories do not appear in our maintenance release repo. Not sure why. They seem to be in the "individual" ones, but not in the final one that's created by a p2.mirror task. Not sure why the script would work during the release, but not the service release, as I don't think that part of the scripts have changed. I'm discovering this late, but I don't think it is a "blocking" problem, though is admittedly pretty bad.
In looking into this, I've discovered the problem(s) are worse than I thought. Our "release" repository, for 3.2.0, also does not have categories. It is also missing the "download stats" properties, and the mirrorURL property. It does have packed bundles, however. There appears to be a combination of errors. First, the "categories" are apparently not created during build (or mirrored?) as I assumed. Not sure what broke there. That will take future investigation ... this bug will document repairing 3.2.0 and 3.2.1 repositories. Second, there's three steps to do when promoting a build ... I think I thought these had been automated, but no. From shell, there's some scripts I need to run to finish processing: process artifacts: does the "pack200". addRepoProperties: custom app to add mirrorURL and download stats properties and, for now, addCategories: requires a for now manually maintained category.xml file, and runs CategoryPublisher app. All of these only change the repo's metadata ... no change to code, relationships, etc.
Essentially fixed, using "manual" scripts. I've added those scripts to a folder in releng.wtpbuilder, named manualStepScripts, for safekeeping, with a very brief description.txt file there to outline what has to be done. I'll work on automating more of this in future.
