I just recently went back in my repository and added some new changes. The result after merging in TortoiseHg can be seen in enclosed image ci2.jpg - the interesting row marked with an arrow. Enclosed image ci1.jpg shows what I see in Continua. Note that the rows for setting tag (actually made two tries!) are visible, but there is no row with the text “Case 11384” where it should be. I have done a search for the text, but doesn’t succed. The parent of Rev 5904 is a few weeks back, but in the list, but the Continua listing is >60 weeks back, so I can’t see there should be a problem with parent-hood. Have I stumbled on a bug in Continuas handling of Mercurial repository? /Anders
Hi Anders,
Resetting the repository removes all changesets have not been associated with build and then picks up only the latest changeset on each branch. It looks like the “Case 11384” changeset was not the latest on a branch at the time you did the repository reset.
We currently do not have any way to load the full history of changesets from the repository. We do, however, plan to implement such functionality in a future release - at least to the extent of pulling in a history of changesets which have been tagged.
Returning to this question, as we are facing problems with running correct version:
1. Has the mentioned improvements to the case been implemented? (We see no sign of it)
2. Is there a way to “manually” in the database add the tag?
/Anders
Hi Anders,
We haven’t really had a lot of requests for loading the full changeset history and the work involved is significant so we have been concentrating on other tasks.
If I understand the original issue correctly, the problem was when you tagged that an old changeset, that was not included in the list of changesets for the repository. The changeset was not there either because this was a new repository or it had recently been reset. The new tag did not appear as the changeset it was applied to was not in the database.
If the changeset is in the database and the tag is in the repository then the tag should appear automatically. If the changeset is not there, it’s impossible to manually add a tag as it must refer to a changeset.
It is possible to add a changeset to the database table builds_changeset, but we don’t recommending doing this as it’s quite difficult to get all the correct field values. Ensure you have a backup and the ContinuaCI Server service is shutdown before making any changes to the database.
Why do you need to see a tag of an old changeset - so you can build it? Perhaps you can use a create a named branch for that commit instead?
Hi Dave, thanks for your explanation! As far as we can see, the changesets referred are there, and it all seems a bit random which tags make it into the list and which don’t. The only explanation I can think of is that there should be some messing when we merge different .tag files, but Mercurial seems to handle everything correct.
But of course you are right - for our needs, creating a branch is quite correct! (Sorry to say, we didn’t quite understand how to do it, but we have sorted it all out now 
/Anders