Every repository with this icon (
Every repository with this icon (
| Fork of foca/integrity | |
| Description: | The easy and fun Continuous Integration server edit |
-
- Bobette's API
- POST /:project/builds
Comments
-
That's actually a DataMapper issue: http://datamapper.lighthouseapp.com/projects/20609/tickets/965-sel-not-working-for-11-association
Comments
-
It appears that's a bug in DataMapper. There is more details on http://integrity.lighthouseapp.com/projects/14308/tickets/154
Comments
-
Add a json action so that users can track the status of their builds in other applications and provide a badge / button / image / bit of markup and js that updates that status on the projects github page.
This could also be done down to the current branch the user was viewing, such that I could tell that the 0.1.7 tag was broken, but the 0.1.6 tag had a successful build.
-- Ben Schwarz, http://integrity.lighthouseapp.com/projects/14308/tickets/90-feature-build-status-badgesComments
-
Using Integrity from a non-subdomain breaks Cucumber/WebRat features for Rails
1 comment Created about 1 month ago by srFrom the original ticket on LightHouse http://integrity.lighthouseapp.com/projects/14308/tickets/191
I have Integrity set up as a subdirectory, instead of a subdomain (i.e. dev.mydomain.com/integrity) and it is breaking my Cucumber/WebRat steps for a Rails application. Most features pass fine, but a few of them gives errors like this:No route matches "/integrity/" with {:method=>:get} (ActionView::TemplateError) features/sign_out.feature:8:in `When I sign in as "email@person.com/password"' No route matches "/integrity/" with {:method=>:get} (ActionView::TemplateError) features/sign_out.feature:16:in `When I sign in with "remember me" as "email@person.com/password"' No route matches "/integrity/" with {:method=>:get} (ActionView::TemplateError) features/dashboard.feature:8:in `When I go to the homepage'Since all features run fine on my machine, and they all mention /integrity/, which is part of my base URI for Integrity, I assumed it was a problem with Integrity. And sure enough, setting up and using ci.mydomain.com makes all the features pass.
But I want to keep the dev-subdomain, and have /integrity/ instead.
Comments
We had this problem when running Integrity on Passenger. Passenger will set the environment variable RAILS_RELATIVE_URL_ROOT to whatever subdomain you're running on. When the tests run this variable will be picked by Rails and sets it as the relative_url_root, thus causing the tests to fail.
You can work around this by explicitly setting the configuration in your test.rb:
config.action_controller.relative_url_root = '' -
All links disregard a subdomain when setting base_uri.
Comments
-
Dan Kubb suggested to use a custom DM type to compress the build output using ZLib.
Comments
-
Patched integrity to show output as its being run. This is great to ensure processes are running and the current state of the current build.
http://github.com/jsmestad/integrity/commit/9bd908b517a3b7b710f687698e33518bdbb5e0c6
Comments
-
Comments
-
Integrity's disk usage is pretty high right now over time (each project, each build, is a complete clone of the repository). Given that all build information is saved in the database, could Integrity get an action to clean all but the last 5 builds from the system, or even make this automatic?
Comments
-
I started a new project with Rails 2.3.4 and when I built I ended up with this error:
rake aborted!
can't activate rack (~> 1.0.1, runtime) for [], already activated rack-1.0.0 for []Comments











