[
http://jira.codehaus.org/browse/CONTINUUM-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Goeser updated CONTINUUM-567:
-----------------------------------
Attachment: continuum-bug.png
I think we got some sort of a regression in 1.1see the attached screenshot.
Client and Server are two build definitions of a single project using the same
working copy (subversion). "Sometimes" both build definitions are build after
an SVN update, but sometimes the stdout of the server just says something like
"No SCM changes, not building".
Just a guess: could it be, that a forced build somehow confuses the scheduler?
> A build must be launched if we have changes since last build (for same build
> definition) and not only if we have detected changes when we run scm update
> commad
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-567
> URL: http://jira.codehaus.org/browse/CONTINUUM-567
> Project: Continuum
> Issue Type: Improvement
> Components: Core system
> Affects Versions: 1.0.2
> Reporter: Emmanuel Venisse
> Assignee: Emmanuel Venisse
> Fix For: 1.0.3
>
> Attachments: continuum-bug.png
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
