SourceGear Support

I have written a utility that our team uses to deploy files directly from fortress to our test or production web servers based on a change ticket. They select a project, and then they select a ticket, and they are given a list of all files that are associated with that ticket (usually .aspx or .cfm files). From there, they select the files that they want to deploy and this tool will extract those files and place them on the server that they chose. The 'problem' is that the files are not associated with a ticket until they are changed, so users who are using this tool to get files on the server that have never changed, don't have a way of associating them without making some sort of insignificant change to the file in order to trigger an association.

I understand that Fortress is for tracking 'changes' to items and checking an item in is really not a change. That considered, is there any way that we can associate a source item with a ticket at the time that it is checked in? We are currently using Fortress 1.1.3 (18336). Might this be a feature in a more recent release of Fortress? Otherwise, maybe there is already be an example that you know of for doing something like this with a custom server plugin?

Any suggestions that you have are welcome!

Thanks,
Stephen

Just to verify, your team is committing the changes from the GUI client, correct?

The issue at work here is probably that they have the Auto-commit option checked. If you uncheck that option, then Add File operations are pended, and go through the regular commit dialog. In that dialog, they can associate bugs as usual.

Another user had a similar issue here:

http://support.sourcegear.com/viewtopic ... 30&t=11566

Jeremy,

I posted your response on our wiki and have gotten nothing but positive feedback on it. Your answer is exactly what we needed.

Thanks!

Stephen