Community
Participate
Working Groups
It is difficult to set up a development workspace to correspond with a specific stable build. Various projects are tagged differently so it's hard to figure out the right combination from within Eclipse. Downloading a stable build doesn't help because no source is provided, and neither are the test projects. I recommend that we produce a project set file (PSF) with each stable (end of iteration) build. This would contain the exact combination of projects (development and testing) as they stood at the point in time the stable build was made. This would very useful for at least 3 consumers: * the adopter who wishes to setup for COSMOS development (such as to build a new MDR) * the developer who wants to debug a customer issue related to a specific stable build * the person conducting a corporate code scan for legal violations at the end of an iteration I suggest that this should be tackled sooner rather than later, as we've run into the need for this multiple times already with a lot of pain involved.
Hubert pointed out to me that PSF files don't contain version information. I thought I remembered there being some mechanism for this. Anyone?
*** Bug 215603 has been marked as a duplicate of this bug. ***
In cosmos we have 3 map files(cosmos,dc,dr) and in similar way we are creating 3 project set files for them. Does it look ok or do we need only one project set file.
Created attachment 96141 [details] Patch to create psf files Please apply this patch. This patch will create 3 different psf files corresponding to cosmos.map, dr.map and dc.map. Beside this following changes should be made to build dashboard page to show these files. BuildID | Status | Quality | Logs | Drivers | Dependencies | ProjectSet -------------------------------------------------------------------------- | | | | | | Cosmos Data-collection Data-reporting
Please change the status of this bug. Project set files are made available on Eclipse build dashboard.
Fixed in build COSMOS-1.0.0-200804231200.
