Anyone have any thoughts on this?
On 20/08/2007, at 10:59 AM, Brett Porter wrote:
I think I understand this problem more now.
the svn errors are a transient problem - it occurs before a build
takes place, but they are recorded as a built result. So when they
succeed again, no build occurs
Brett Porter a écrit :
I think I understand this problem more now.
the svn errors are a transient problem - it occurs before a build takes
place, but they are recorded as a built result. So when they succeed
again, no build occurs because no update has taken place.
I see two possible corre
The problem is in beta-2 when the "fresh build" option is checked and the
project contains lot of files in scm. The build controller merged scm results with old
build results but it mustn't do it.
I fixed this problem yesterday.
Emmanuel
Brett Porter a écrit :
We get this occasionally on vmbu
On 29/08/2007, at 7:48 PM, Emmanuel Venisse wrote:
2) rebuild a project that was in error state before.
I think it's the best solution for now and won't be a lot of work.
agreed... can we sneak this into the 1.1 JIRA? :D
Only the first would also address the problem of having
difficul
The patch doesn't seem to be complete, it's only a new class with a patch in
other classes or components.xml
I'll look at it in details to see if we can include it in 1.1
Emmanuel
Brett Porter a écrit :
Hi,
I know where in feature freeze, but I'd really like this and it has a
patch :)
Any
Brett Porter a écrit :
On 29/08/2007, at 7:48 PM, Emmanuel Venisse wrote:
2) rebuild a project that was in error state before.
I think it's the best solution for now and won't be a lot of work.
agreed... can we sneak this into the 1.1 JIRA? :D
sure, I don't think we already have an is
And this is what I did...
I pulled the database someplace that I could run squirrelsql and ran the
following sql statements to update the database, then I put the database
back into place and started the updated version.
--
ALTER TABLE INSTALLATION ADD installation_id integer not null defaul
