How are the issue connectors supposed to be working?
I have a SVN branch aware repository set up. That repository is connected to an Issue Connector which appears to be working in validation mode at least - from a test commit message it creates a valid link.
However when I started a build, Continue detected a test commit done, shows the commit message but does not appear to be acknowledging the issue number in the commit message in any way.
So where should the links generated by the issue connector be shown for a build?
I was mistaken and there is the Issues -tab present. I got probably confused as I was kind of expecting the links to appear at the commit notes shown at the build overview page.
Another thing is that it would appear that at least the SVN repository triggers are currently non functional. I have a trigger monitoring a repository on both branched and non-branched mode. When a commit is made to the repository neither one triggers the corresponding project.
The may or may not be related to the fact that the build priority pick list is empty.
We’re currently investigating a similar issue, our server stopped triggering builds on Friday. Try restarting the service and see if that makes it start triggering, that resolved it for us and it hasn’t happened again, so far we haven’t found the cause but I know it’s not subversion specific as we have a bunch of different repository types running.
Posted By Vincent Parrett on 05 Jun 2012 07:56 AM Hi Ollie
We're currently investigating a similar issue, our server stopped triggering builds on Friday. Try restarting the service and see if that makes it start triggering, that resolved it for us and it hasn't happened again, so far we haven't found the cause but I know it's not subversion specific as we have a bunch of different repository types running.
Hi,
I restarted the service, but it did not appear to affect the issue at all. The service exhibited some similar problems when restarting as did the Agent service when I reported the installation issues. When shutting down it displayed an error about the service not being able to receive control messages.
It would appear that the branched repository detects changes - when clicking the configuration name and clicking changes -tab new changes are displayed there, but they just do not trigger the build.
The non-branched repository does not appear to detect even the changes there.
The non-branched repository emits this kind of issue in the event log: Failed to persist the retrieved changeset data for repository SVN_misc_test_framework_trunk System.InvalidOperationException: Sequence contains more than one element at NHibernate.Linq.DefaultQueryProvider.ExecuteQuery(NhLinqExpression nhLinqExpression, IQuery query, NhLinqExpression nhQuery) at NHibernate.Linq.DefaultQueryProvider.Execute(Expression expression) at NHibernate.Linq.DefaultQueryProvider.Execute[TResult](Expression expression) at System.Linq.Queryable.SingleOrDefault[TSource](IQueryable`1 source, Expression`1 predicate) at Continua.Modules.Builds.Repositories.RepositoryManager.GetMatchingUserMappings(Repository repository, String repositoryUsername) at Continua.Modules.Builds.Repositories.RepositoryMonitor.PersistResult(RepositoryChecker checker)
Thanks for the info, we’ll check it out tomorrow. Can you copy the text on your repository user mappings page so we can try to setup the same scenario here.
The issue with it not triggering on the changes it found may be to do with the settings on the trigger, which also needs to specify which branches it will trigger on. How is the trigger setup?
BTW, we changed the commit message handling today so that the issue id’s are now links in the commit message as well as showing up on the issues tab.
We were able to reproduce this issue here today, build 1.0.0.507 (just uploaded) includes the fix. If you still see issues with builds not triggering, check that the trigger branch pattern is correct.
We just posted a new build (513) which fixes the Priority not rendering correctly (looks like a firefox bug). I don’t see anything else wrong with your trigger setup. What settings do you have on the repository?
