Displaying 4 results from an estimated 4 matches for "email_notifi".
Did you mean:
email_notifier
2010 Jun 24
1
Scheduling a nightly build - config options
..._config.rb at project level
--------------------------------------------
# Project-specific configuration for CruiseControl.rb
Project.configure do |project|
# Send email notifications about broken and fixed builds to email1 at your.site, email2 at your.site (default: send to nobody)
project.email_notifier.emails = [''krishnan.kannan at mydomain.com'']
# Set email ''from'' field to john at doe.com:
project.email_notifier.from = ''cruisecontrolrb at mydomain.com''
# Build the project by invoking rake task ''custom''
#project.r...
2011 Jul 11
0
Email a build fail to the checkin culprit
Hi
I would like to ask how to configure the email address that will email to me and to the person who has checked in the files that has broken the build.
//Currently the email is fixed in the configfile with me as the sole address
project.email_notifier.emails = [''me at myemailaddress.com'']
Does anybody know how to change the email address dynamically following a build fail from the previous SVN commit.
Any help appreciated
Thanks
Rgds
Stuart
Privacy & Confidentiality Notice
------------------------------------------...
2008 Mar 31
0
[CruiseControl] mongrel-trunk-mingw32 build 997.1 failed
...run; ARGV.clear" >> D:\Users\Luis\.cruise\projects\mongrel-trunk-mingw32\build-997.1\build.log 2>&1
exitstatus: 1
STDERR TAIL START
STDERR TAIL END
PROJECT SETTINGS
----------------
# Project-specific configuration for CruiseControl.rb
Project.configure do |project|
project.email_notifier.emails = [''mongrel-development at rubyforge.org'', ''rubyinstaller-devel at rubyforge.org'']
project.rake_task = ''clobber compile test''
project.scheduler.polling_interval = 5.minutes
end
2007 Mar 17
10
a WARNING about cruise task or user-specified build task for Rails
If (like me) you use ccrb to test a Rails app
and (like me) you define your own :cruise task, because, for
example, you use rspec rather than Test::Unit
and (like me) you have the RAILS_ENV ||= ''production'' line in
environment.rb (because, like me, you use crummy shared hosting)
Your build will run in production mode, possibly screwing up your
production database,