#44 ✓wontfix

Scheduled builds?

Reported by dbr/Ben | January 1st, 2009 @ 01:53 PM

Something I miss from using Hudson - being able to have builds run periodically (say, build this project at 01:00, once per day)

Hackishly it could be done by cron'ing a request to the "Manual rebuild" page, but it would be far nice to have it built into integrity..

Comments and changes to this ticket

  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 5th, 2009 @ 05:02 AM

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

    What's the use case for this? If all commits are built after every push, what would you win by rebuilding them at a set time?

  • dbr/Ben

    dbr/Ben January 5th, 2009 @ 09:40 AM

    Well, if you are using a non-github repo, you don't get the build-on-push feature (or in my case, I'm not running Integrity on a machine reachable by github's services stuff) Also, if you have tests that interact with other services (APIs) it's nice to know if the API changes and your code breaks (even if you don't change the code for a while)

  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 5th, 2009 @ 01:31 PM

    Right. Regarding the non-github repos, you can add your own post-commit-hook to your repo (this one might work).

    About a network unreachable repo... can you access the firewall to setup a forward? Or maybe do some ssh-tunneling if you can ssh into your firewall.

    About the external libs part, let me think about it.

    This would be a "big" feature (in the sense that you need a background worker checking who needs to be built when), so it's not something I'm keen on adding unless it's really necessary :)

    Keep it clean, keep it simple, keep it small :)

  • ronin-278 (at lighthouseapp)
  • ronin-278 (at lighthouseapp)

    ronin-278 (at lighthouseapp) January 17th, 2009 @ 05:27 PM

    • State changed from “new” to “discuss”
  • dbr/Ben

    dbr/Ben January 21st, 2009 @ 10:34 AM

    I was thinking, could there be a similar system to the notifiers, but rather than calling the module when a notification must be made, a thread is created on startup for each one..

    Shouldn't be horrendous to implement, and it gives you lots of flexibility, not only scheduled builds, but perhaps this could be used for background building? Persistent notifier bots (where they remain connected to Jabber, or IRC etc), polling repositories for changes and so on.

  • Simon Rozet

    Simon Rozet January 22nd, 2009 @ 02:46 AM

    As you pointed out, cron would work just fine, and this without any code/feature addition. Part of what makes Integrity awesome is that it IMO is small/KISS, so I am marking this as wontfix. Thanks.

    I opened #72 to discuss the permanent notifiers

  • Simon Rozet

    Simon Rozet January 22nd, 2009 @ 02:46 AM

    • Milestone cleared.
    • State changed from “discuss” to “wontfix”
    • Assigned user changed from “ronin-278 (at lighthouseapp)” to “Simon Rozet”

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