#16 ✓resolved
ronin-278 (at lighthouseapp)

"Build manually" should be Rebuild

Reported by ronin-278 (at lighthouseapp) | July 25th, 2008 @ 10:18 AM | in 0.1.9

Considering that we are going to build for each commit when we get commits from github (same as when we poll non-gh repos), "build manually" as a project option doesn't make sense once you have the first build in place.

I'm thinking that instead, showing it in each build (very very very dissimulated on the green/red box until you hover over it) makes more sense.

In this case, it'd be "Rebuild" (for example, if your build had some system configuration error that needed to be done because of a new component -- ie, copy the database.sample.yml to database.yml or something like that.

Thoughts?

Comments and changes to this ticket

  • Simon Rozet

    Simon Rozet July 27th, 2008 @ 12:42 AM

    I definitely agree. It sounds much more unobstrusive than the actual big-bold-and-ugly button we have :)

    Maybe that we don't even need to display "Rebuild" but simply an image arrows disposed in circle (uh?). I think that their's even an Unicode char for that.

  • Simon Rozet

    Simon Rozet August 9th, 2008 @ 03:53 PM

    • State changed from “new” to “open”
    • Milestone set to 0.1.9
  • Simon Rozet

    Simon Rozet September 20th, 2008 @ 08:19 PM

    • Tag changed from feature, ui-web to feature, ui-web

    now that I read the ticket again, I am wondering... are you saying that the "rebuild" button should erase the previous build or that it creates another build?

  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 15th, 2009 @ 07:19 AM

    With the coming refactoring to have Commits and Builds separate, this should just create a new build for the commit from where it's called.

    For now, we can just display on the website the newest build, but later on can add some UI to display build history per commit, if someone finds it valuable.

  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 19th, 2009 @ 07:48 AM

    • Tag changed from feature, ui-web to feature, hackfest, ui-web

    (from [7721421daf7d2ca4e1b52da66c12d41bb09538b9]) Refactor Build into Commit and Build [#61 state:resolved]

    • Migrations are fixed, and should work out of the box. Just run integrity create_db config.yml and your database should be migrated (backup the database just in case before, and let us know if something goes wrong).

    • Build manually is broken if you don't have commits in your project already. If there's a build already, it will just rebuild that commit This ties into [#16] but breaks a few things. Mainly building for the first time to test the config is working (before we get sent a push).

    • Posting to /push requires more information. All the information is already sent by Github, so no harm done if you're using that. If not, you need to provide, for each commit, a timestamp, the author name and email (in 'name ' format), and the commit message. We will publish a custom ruby script that you can run as your post-receive hook and that supplies all this information.

    • Building is still done in the foreground, but all the "dirty" work is done and making it build in background should be easy now.

    • Some styles and views need work. need work (at least, to handle commits that haven't been built yet), but maybe something else I'm missing. http://github.com/foca/integrity...

  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 25th, 2009 @ 11:23 PM

    • Tag changed from feature, hackfest, ui-web to feature, ui-web

    (from [b8af16d60721441fbfec76f3dfdc738dfff88e04]) Refactor Build into Commit and Build [#61 state:resolved]

    • Migrations are fixed, and should work out of the box. Just run integrity create_db config.yml and your database should be migrated (backup the database just in case before, and let us know if something goes wrong).

    • Build manually is broken if you don't have commits in your project already. If there's a build already, it will just rebuild that commit This ties into [#16] but breaks a few things. Mainly building for the first time to test the config is working (before we get sent a push).

    • Posting to /push requires more information. All the information is already sent by Github, so no harm done if you're using that. If not, you need to provide, for each commit, a timestamp, the author name and email (in 'name ' format), and the commit message. We will publish a custom ruby script that you can run as your post-receive hook and that supplies all this information.

    • Building is still done in the foreground, but all the "dirty" work is done and making it build in background should be easy now.

    • Some styles and views need work. need work (at least, to handle commits that haven't been built yet), but maybe something else I'm missing. http://github.com/foca/integrity...

  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 26th, 2009 @ 10:12 AM

    • State changed from “open” to “resolved”

    (from [85d5f320aac29be3e922337a3444ba1db225de05]) Fix manual commits, add an option to rebuild any given commit [#16 state:resolved] http://github.com/foca/integrity...

  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 26th, 2009 @ 10:14 AM

    • Assigned user set to “ronin-278 (at lighthouseapp)”

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Automated continuous integration server that doesn't suck.

Shared Ticket Bins

People watching this ticket

Referenced by

Pages