---------- Forwarded message ---------- From: Nilo Garcia Silveira <[email protected]> Date: 2009/8/12 Subject: Re: [scmbug-users] Validation of committed archives on SCM with the bug/issue on bugtracker To: Kristis Makris <[email protected]>
Hi Kristis, Sorry my bad english but I'll try explain what I think about this feature: 2009/8/11 Kristis Makris <[email protected]> > I thought you might want to only validate the installation worked, > similar to: > > http://bugzilla.mkgnu.net/show_bug.cgi?id=358 What is your context ? The company where I work (Visual Systems Informática Ltda.<http://www.visualsystems.com.br>) it's in adaptation process to MPS-Br (that's a similar methodology of CMMI) and we'll implement the Management Configuration process with this combination: Bugzilla 3.2.3, Subversion 1.6 and ScmBug 0.26.15. But to do this, we'll need validate if the committed files on Subversion are related with the bug/issue on Bugzilla. For sample, I open the bug #15 and I related the files build.xml and AppMain.java to it. If the developer try commit to Subversion the file FrmMain.java refering the bug #15, the ScmBug couldn't validate this transaction, because the file FrmMain.java not is listed on bug #15. Another policy that I thought to be useful is the following: if the committed file was a new file on the project, the ScmBug could insert it on bugtracker and related it with the bug. > included on the bug/issue on bugtracker. So, I'll implement a new > > policie on the Glue script. > > In my first analisis, I'll need change the following files: > > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Glue\Glue.pm > > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Daemon\Bugtracker.pm > > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Daemon\Bugzilla.pm > > C:\tools\scmbug-0.26.15\share\scmbug\lib\Scmbug\Daemon\Integration.pm > When I first read this email, I thought you wanted to add a policy in > the daemon to verify that what was attempted to be added in the > issue-tracker was in fact added. Is this what you are trying to > accomplish ? In fact, the validation will be made on the Daemon. That's right. If so, why would you need to modify Glue.pm ? This sounds like it should be developed entirely on the Daemon. > So, I read some the source codes of ScmBug and I noted that the policies of validation are written on Glue's configuration file. So, I think that the Glue.pm will be change only to verify if the configuration file is correct with this new policies. > > If you thing this a nice feature, tell me how I can share it. > > Do you have some tip to give me? > > How can you be sure that your validation is correct ? How will you do > it ? The validation will need query this information on bugtracker. I read some of Bugzilla's source code and I saw that this will be possible. > How can you be sure that if a new version of the issue tracker > becomes available that your validation policy will work against it ? > Will you need another policy that validates the validation ? > Well, I'll try implement this policies only on the Bugzilla 3.2.3 context Thank you for your attention, Nilo Sun Java Programmer Certified
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
