Hi all,
I have a question on how Continuum works.
I set up a script to check things out of SVN and burn it to a CD every
night.
However, Continuum doesn't seem to be executing the script on a nightly
basis.
The script did seem to work on Jun 29, when the revision number was at 245.
This was th
I have voted for your issue.
I am not sure if they are exactly the same. I am thinking that when
Continuum cannot even begin to execute the build because of some problem
such as an SCM error when trying to update the working copy, it should
only send one error notification the first time it ha
It seems that something was changed in Google talk connection :
http://www.jivesoftware.org/community/thread.jspa?messageID=122893
We use the jivesoftware smack library for jabber/google connection.
Emmanuel
Emmanuel Venisse a écrit :
jvm 1| Caused by: XMPPError connecting to talk.google.
jvm 1| Caused by: XMPPError connecting to talk.google.com:5222.: (502)
jvm 1| -- caused by: java.net.ConnectException: Connection timed out:
connect
Are you behind a proxy?
Emmanuel
Jeff Mutonho a écrit :
On 7/5/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
A message is sent only
On 7/5/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
A message is sent only if the build state is changed between two builds like it
was in failure and
now it is in success.
So in your case, the message isn't sent because the build is always in success.
Emmanuel
Thanks.Now I induced a buil
In 1.1, we'll have the group of projects features. I don't know for now if we'll have group
notifiers. If we decide to have it, CONTINUUM-634 will be in 1.1
Emmanuel
Vincent Massol a écrit :
Hi Mark,
I'd love this too. See http://jira.codehaus.org/browse/CONTINUUM-634. You
can even vote for i
The internal continuum repo (that can be configured in the configuration screen) is independant of
local/remote maven repository. Continuum copy artifacts in it (even without deploy goal) when the
build is in success and maven copy artifacts in local repo with install goal and in the remote repo
A message is sent only if the build state is changed between two builds like it was in failure and
now it is in success.
So in your case, the message isn't sent because the build is always in success.
Emmanuel
Jeff Mutonho a écrit :
On 7/5/06, Jeff Mutonho <[EMAIL PROTECTED]> wrote:
On 7/4/0
