BugTracker.NET 3.3.0

Rating: No reviews yet
Downloads: 210
Released: Oct 20, 2009
Updated: Oct 20, 2009 by ctrager
Dev status: Stable Help Icon

Recommended Download

Application BugTracker.NET 3.3.0
application, 1776K, uploaded Oct 20, 2009 - 210 downloads

Release Notes

IMPORTANT - This release contains a reworking of the Subversion
integration. If you have already integrated BugTracker.NET with
Subversion, you will have a little bit of extra work to do when you
upgrade to this release.

Also, this release no longer supports the functionality of displaying
links to the php "WebSvn". If you were using that feature, contact
me at ctrager@yahoo.com and complain, so that I'll have some motivation
to add it back in.

The new svn hook script is subversion\svnhookforbtnet.renameto_py.

The old hook script made a connection to the BugTracker.NET database,
and so there needed to be connectivity between the subversion machine
and the databse machine. The new script does not connect to the
database. Instead, it posts an HTTP request to a bew web page,
svn_hook.aspx, so your subversion machine will need connectivity with
the BugTracker.NET website.

I think for most people, this arrangement is easier, since the website
is typically already exposed, whereas the database is typically behind
a firewall.

Read the instructions in the hook script file itself. You will need
to edit some values in it just like you did with the old one. It will
be easy.

The hook script keeps track of what revision it last processed. The
first time it runs (or whenever it can't find the file that it uses
to keep track of the previously processed revision), it will send the
subversion log for all revisions to svn_hook.aspx. If you delete its
tracking file, it will send the entire log again. The Svn_hook.aspx
webpage is smart enough not to do duplicate inserts. Even revisions
where you forgot to add a bug id will still be inserted into the
revisions table, with a bug id of 0, so you could link them up to
bugs "by hand" yourself, with sql.

The revised web pages won't work with the data you currently have in
the svnrevisions and svnaffected_paths tables. You will need to
delete your data and let the hook script reload the data. It worked
fine for me.

Run this SQL to delete the data in those tables:
delete from svnaffectedpaths
delete from svn_revisions

Then, when your hook script is working, delete "btnetprevrevision.txt"
that it uses keep track of the previously processed revision, change
something, commit, and the two tables will get completely reloaded
with your entire repository log history.

The repository settings in Web.config and the project-specific svn
settings in Web.config are also gone, because the repository info
now is stored in the db. But, if a username and password is required
to read your repository, then you configure that in Web.config.
See Web.config for how to do that.

Run this SQL to get rid of the obsolete db columns:
alter table projects drop column pjsubversionrepository_url
alter table projects drop column pjsubversionusername
alter table projects drop column pjsubversionpassword
alter table projects drop column pjwebsvnurl

Finally, I apologize for the inconvenience but I think the new script
is better. It's more forgiving, because you can always delete your
database data and the script can be used to repopulate it. And, it
connects with the web server, not the database server. Finally,
because each revision is recorded along with the url needed to get
back to the repository, it's very easy to use multiple repositories
with one BugTracker.NET instance. Before I supported having a
different repository per project, but now you can have any sort of
scheme you want - even multiple repositories per bug.

Other changes this release are to the git integration:
  • Git integration was failing if file name contained spaces.
  • Even commits where the message does not contain a bugid are inserted
into the database, so that you could link them up to bugs "by hand".

I think pretty much everything I wrote above about the svn integration
also applies to the git integration. They both follow the same design.
The major differences are that with git, the repos

Reviews for this release

No reviews yet for this release.