Community
Participate
Working Groups
During the course of an iteration, the development team makes changes to APIs in COSMOS code that force corresponding changes to the test projects (e.g. JUnits). Currently, the test projects are not being tagged, so if there was ever a need to go back and test an earlier tagged build, there is no reasonable way to load the version of the test code that corresponds with the APIs found in the earlier build. We need to start tagging test projects when we tag test drivers and candidate drivers, so we have the ability to execute our test framework when it is necessary to against older code.
Is this being considered for i8? I would suggest so, and also a priority of at least P2.
There are various plugins in tests folder corresponding to various modules. Do you want the tagging to be done for all of the plugins. Please elaborate, what is required to be done.
For any plugins that contain testing code, I would say yes. There should be a repeatable way to extract testing code for CVS that corresponds to a specific build level of code. Since projects & plugins change all the time, I would think in general we'd want everything like that tagged. Including the CMDBf example project, the datacenter example, etc. Why use a version control system, if there is no way to extract versions of such high level aggregates?
Hubert should be able to help with that, I suppose there was a similar process in TPTP
It will be better if we tag the complete test module. Also this work item, is to be done, when I announce the candidate driver. As of now will test the tagging.
That sounds reasonable. Please also consider testing the examples and samples I mentioned as well, as part of the same process.
Tagged the test folder (tag used: COSMOS-i_8_0115_2008). Command used: cvs -d cosmos:/cvsroot/technology rtag -b -r HEAD COSMOS-i_8_0115_2008 org.eclipse.cosmos/tests > log0115 2>&1
Jagmit, please don't use the -b flag when tagging code. It will create a branch from the snapshot.
Tagged the plugins/features of i8 stable driver with V1_0_0i8. Also tagged the test module. Will document the tag commands on the wiki.
Added the documentation to perform tagging to cosmos release engineering page (http://wiki.eclipse.org/COSMOS_RE_AND_BUILD). Under title "Tagging the Builds"
marking this as fixed
