CruiseControl for Ruby user mailing list. ()

headers Panayotis Matsinopoulos | 10 Feb 12:16

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Hi

I have setup 3 projects all from the same repository but the point to different level of the repository.  I
would like to trigger a build of the top level of the repository after the detection of a change to any of the
others.  I think this is described in the docs as a quick build triggering a full build.

I have set the following in my cruise_config.rb file

 if(project.name == "myProject")
   project.triggered_by = [SuccessfulBuildTrigger.new(project, "Source")]
   project.triggered_by SuccessfulBuildTrigger.new(project, 'Testbench')
end

I expect the first line to override the default trigger which is any change in myProject.  The second I expect
to add an additional trigger.
This code does not change the default or add another trigger.  (The name is correct)

I have remove the condition statement to:

   project.triggered_by = [SuccessfulBuildTrigger.new(project, "Source")]
   project.triggered_by SuccessfulBuildTrigger.new(project, 'Testbench')

but this now shows "error" below the build button in the dashboard

This code is pretty much straight from the manual so can anybody show me where I am possibly going wrong here?

Thanks

Privacy & Confidentiality Notice
-------------------------------------------------
This message and any attachments contain privileged and confidential information that is intended
solely for the person(s) to whom it is addressed. If you are not an intended recipient you must not: read;
copy; distribute; discuss; take any action in or make any reliance upon the contents of this message; nor
open or read any attachment. If you have received this message in error, please notify us as soon as
possible on the following telephone number and destroy this message including any attachments. Thank you.
-------------------------------------------------
Wolfson Microelectronics plc
Tel: +44 (0)131 272 7000
Fax: +44 (0)131 272 7001
Web: www.wolfsonmicro.com

Registered in Scotland

Company number SC089839

Registered office: 

Westfield House, 26 Westfield Road, Edinburgh, EH11 2QB, UK

We use RVM for gemset management.  The build has its own gemset, say
ree <at> build.  The ccrb was built with ree <at> cruisecontrol, where
cruisecontrol was created specifically for it, switched into, and
filled with bundle install.

When we run our build, it was failing in jasmine, in the part where it
was checking for rspec2.  At the time we had rspec1 and rspec2 both
installed.  We uninstalled rspec 2.6.0 from the gemset build, and it
was still failing.  We then uninstalled rspec 2.6.0 from the gemset
cruisecontrol, and then the build went through.

Our build is not using bundler, but in its own directory we have an
.rvmrc containing the line "ree <at> build".

I wonder how the gemsets for ccrb and build interact -- the worrysome
sign is that rspec gem matters across both.  Would it be limited to
rake and rspec?  How do we know the build gemset is being respected
separately from ccrb's own cruisecontrol gemset?

-- Alexy

Hi All.

We've been using CCRB, v 1.4.0, on a project for nearly a year now and
have found it pretty stable however recently we've had some issues.

The project is cross platform so there are multiple builders monitoring
the same subversion path.

When there are just 2 builders this works fine.
We've recently introduced a new platform so have added another project
which monitors the same subversion path. This has caused some stability
issues.
Every so often, seems like every 2 or 3 builds one of the builders will
die for no apparent reason. The dashboard indicates the builder is
stopped and the log doesn't seem to say anything. It seems random which
builder will die out of the 3 that are running.

Has anyone seen anything like this or have any ideas how I can get them
to be stable again.

Switching the builds in to serial rather than parallel isn't an option
as each build can take up to half an hour, some times longer.
Any ideas gratefully received.

Thanks.
Nick.

Nick Adamson
Software Engineer

Advanced Projects and Technologies  

Bryn Brithdir, Oakdale Business Park, Blackwood, South Wales, NP12 4AA

Telephone: +44 (0) 1495 236467  
Email: nick.adamson@...
<mailto:nick.adamson@...> 
Website: www.generaldynamics.uk.com <http://www.generaldynamics.uk.com/>

Please consider the environment before printing this email 

This email and any files attached are intended for the addressee and may contain information of a
confidential nature. If you are not the intended recipient, be aware that this email was sent to you in
error and you should not disclose, distribute, print, copy or make other use of this email or its
attachments. Such actions, in fact, may be unlawful. In compliance with the various Regulations and
Acts, General Dynamics United Kingdom Limited reserves the right to monitor (and examine for viruses)
all emails and email attachments, both inbound and outbound. Email communications and their
attachments may not be secure or error- or virus-free and the company does not accept liability or
responsibility for such matters or the consequences thereof. General Dynamics United Kingdom Limited,
Registered Office: 21 Holborn Viaduct, London EC1A 2DY. Registered in England and Wales No: 1911653. 

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Hi,

Ruby 1.8.7
Cruise Control 1.4.0
Passenger 3.0.2
git

Since upgrading to Passenger 3 we've noticed that our Cruise projects
try to run the test suite twice which is, in itself, causing some of our
tests to fail (on the second run).

Note that our tests pass (and only run once) on our local boxes, so it's
not some hidden fork call. Also, they pass if run manually on the server
hosting CC (and only run once). It's only the automated testing that
exhibits this behavior.

Any ideas?

Regards,

Dan

Hi,

According to https://github.com/thoughtworks/cruisecontrol.rb#readme
the last release was 1.5 years ago: v1.4 on 2009-06-30.  What version
of Ruby and Rails should I use with that release?

Should I instead just pull something from github?  If so, what version
of Ruby and Rails do you advise?

Thanks,
--
Bil, http://fun3d.larc.nasa.gov

P.S. I'm currently using some hacked up v1.3 version I forked off github
a long while ago.

_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Hi, I use CC.rb for CI in my company. I have problem with one of my
projects. It builds constontly, there are builds: 176.1, 176.2 ....
176.56 I suppose it has no end at all. How can I fix it? I tried to
remove and add it again but it doesn't work.

--

-- 
Pozdrawiam, Sebastian Nowak
http://blog.sebastiannowak.net
XMPP: im@...

1	February 2012
3	September 2011
5	July 2011
2	June 2011
2	May 2011
4	April 2011
2	March 2011
22	January 2011
6	November 2010
7	October 2010
16	September 2010
6	August 2010
11	July 2010
2	June 2010
17	April 2010
12	March 2010
5	February 2010
18	January 2010
2	December 2009
12	November 2009
10	October 2009
10	September 2009
7	August 2009
2	July 2009
2	June 2009
10	May 2009
16	April 2009
12	March 2009
44	February 2009
10	January 2009
3	December 2008
18	November 2008
27	October 2008
47	September 2008
49	August 2008
16	July 2008
13	June 2008
53	May 2008
33	April 2008
27	March 2008
38	February 2008
52	January 2008
17	December 2007
30	November 2007
15	October 2007
12	September 2007

Long build log files are not displayed

My continuous integration server is hitting git too hard

Email a build fail to the checkin culprit

Overriding the default trigger and adding more

ccrb's own gemset vs the build's one

multiple builders, why do they keep stopping.

Using Cruisecontrol for non-rails projects.

CC running tests twice with Passenger 3

Updating my CC.rb instance?

Email configuration for projects

CC.rb constantly building one project

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31