Changes between Version 1 and Version 2 of Topics-2010-07-01


Ignore:
Timestamp:
06/30/10 10:39:10 (12 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Topics-2010-07-01

    v1 v2  
    11= Development discussion =
    22
    3  * Builbot
     3 * [http://buildbot.net/trac Buildbot] ([http://djmitche.github.com/buildbot/docs/0.7.12/ manual])
    44  * How to inform developers of build successes/warnings/failures?
    55   * Using openvpn-devel: ~500 subscribers, most don't care about these
    66   * Using a separate mailinglist (openvpn-commits/builds): requires yet another subscription
     7   * Use an IRC notifier (#openvpn-devel)
    78  * Should we limit access to the buildbot web interface?
    89   * Most people have no use for it
     
    1011   * Ways to limit access: basic AUTH / SSH access + port forwarding / OpenVPN tunnel
    1112  * Where do we get the BuildSlaves?
    12    * Background information: BuildSlaves are responsible for testing the builds. The idea is to have buildslaves running a variety of OSes (e.g. FreeBSD, Debian, Fedora). Each can then build and package OpenVPN for their respective platform.
    13  
     13   * Background information: BuildSlaves are responsible for testing the builds. The idea is to have buildslaves running a variety of OSes (e.g. FreeBSD, Debian, Fedora). Each can then build and package OpenVPN for their respective platform. BuildSlaves run buildbot and connect to the BuildMaster server and accept BuildRequests (commands) from it. They do not need to be online all the time, but that's beneficial. They can work from behind a firewall, as they initiate the TCP connection to the BuildMaster.
     14   * Should we ask our community members to provide BuildSlaves?
     15   * Should we create "always online" virtual machines to provide BuildSlaves?
     16   * Should we combine both approaches?
     17  * What setup do we want to use to trigger builds?
     18   * Option 1: use a commit mailinglist and configure BuildBot to detect commits from the mails - should be relatively clean and well supported option
     19   * Option 2: developer sends a git push -> sf.net server accepts the push and updates the remote git tree -> server side calls .git/hooks/post-update which does a 'curl https://community.openvpn.net/buildbot/git-updated' -> community.openvpn.net executes a script by the webserver which executes the git_buildbot.py script in the background and responds OK -> git_buildbot.py will then trigger a fetch and do a build
     20
     21 * [http://thread.gmane.org/gmane.network.openvpn.devel/3806 Issues with SVN in the Beta 2.2 branch]
     22
     23 * Launch date for forums.openvpn.net