Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: chief1983 on January 05, 2012, 04:18:52 pm
-
Mantis has been upgraded to the latest stable release, 1.2.8. No hiccups were encountered during the upgrade, but please mention if anything suddenly seems strange.
-
what if a bug prevents me from reporting that the bug reporting isnt working ? </zen>
-
And now my brain has just exploded.
-
And now my brain has just exploded.
Known issue
-
Will Not Fix.
-
But it's critical :(
-
But not reproducible :p
-
It's critical, but,
not reproducible,
It's Cobra's braaaaain!
-
Can you post a log please?
-
Sorry to stop the party, but I have more actual news on this front. The new Mantis supports a plugin for integration with various version control systems, such as SVN and Git. I've enabled the SVN integration now, so any SVN commits that have ever referenced a ticket by number are now mentioned in the ticket's detail page under 'Related Changesets.'
-
nice work
-
sweet :yes:
Can the plugin also populate the [ diff ] & [ file ] links as can be seen on this page?
http://scp.indiegames.us/mantis/plugin.php?page=Source/view&id=3739
(the issue was picked at random)
edit: clarify the link names
-
Not without WebSVN unfortunately. We'd have to set up WebSVN on a server and have it point to our repository. I might see how running it remotely on the SCP's website server works, since the SVN is on icculus.org and not indiegames. I'm trying to figure out why the last commit didn't get checked in automatically first though.
-
I'm not sure if this is exactly what you're talking about, but maybe because some commits have a 4 digit mantis reference, not the full 7 digit reference? e.g. svn 8147 (http://svn.icculus.org/fs2open?limit_changes=100&view=rev&revision=8147) & mantis 2545 (http://scp.indiegames.us/mantis/view.php?id=2545)? Fixing this up looks like (http://stackoverflow.com/questions/304383/how-do-i-edit-a-log-message-that-i-already-committed-in-subversion) it'd require a fair bit of taylor's time (he's the SVN admin?) and thus probably isn't worth it for previous commits, but it'd be useful to remember for future commits to include the full 7 digit reference so the auto-mantis-linkage works.
-
remember for future commits to include the full 7 digit reference so the auto-mantis-linkage works.
Do we really have to use the full 7 digit reference to each Mantis report? Seems highly unlikely coders will remember the extraneous leading zeros each time...
-
I made that statement just from the behaviour I've observed from looking through SVN and comparing relevant commits with mantis - maybe there's an option to tweak the mantis plugin? Otherwise, yeah, I haven't bothered to include the leading zeroes in any of my commits so far either...
-
I'm pretty sure that many commits linked fine without a full 7 digit reference. But the last commit tried to tell mantis to run the check in script, and it didn't seem to work. So now I'm trying to figure out why.
-
Can the plugin also populate the [ diff ] & [ file ] links as can be seen on this page?
I've noticed that these links are being populated now. Ditto for a mantis issue being closed automatically by the relevant commit into SVN - awesome work chief! :nod:
-
Actually we're going to turn off auto-resolving for now, it might lead to some confusion I think. We can re-discuss turning it on later maybe once people are more accustomed to how it's all working. And yeah I set up WebSVN on a friend's server to get those links working. Not the fastest but it works.
-
Is this why Zacam has been stealing my resolved bugs? The auto resolver?
-
Yeah.
-
K ill call back the hitmen
-
Yeah it could be automatic, I thought I turned off auto-resolve but it still seems to be doing it.
-
Need heuristic for "dont reassign bug after status == resolved || closed" I'm losing stats fast here.
-
FTFY.