VirtualTam's bookmarks

  1.  1for (agent in hudson.model.Hudson.instance.slaves) {
     2  println('====================');
     3  println('Name: ' + agent.name);
     4  println('getLabelString: ' + agent.getLabelString());
     5  println('getNumExectutors: ' + agent.getNumExecutors());
     6  println('getRemoteFS: ' + agent.getRemoteFS());
     7  println('getMode: ' + agent.getMode());
     8  println('getRootPath: ' + agent.getRootPath());
     9  println('getDescriptor: ' + agent.getDescriptor());
    10  println('getComputer: ' + agent.getComputer());
    11  println('\tcomputer.isAcceptingTasks: ' + agent.getComputer().isAcceptingTasks());
    12  println('\tcomputer.isLaunchSupported: ' + agent.getComputer().isLaunchSupported());
    13  println('\tcomputer.getConnectTime: ' + agent.getComputer().getConnectTime());
    14  println('\tcomputer.getDemandStartMilliseconds: ' + agent.getComputer().getDemandStartMilliseconds());
    15  println('\tcomputer.isOffline: ' + agent.getComputer().isOffline());
    16  println('\tcomputer.countBusy: ' + agent.getComputer().countBusy());
    17  //if (agent.name == 'NAME OF NODE TO DELETE') {
    18  //  println('Shutting down node!!!!');
    19  //  agent.getComputer().setTemporarilyOffline(true,null);
    20  //  agent.getComputer().doDoDelete();
    21  //}
    22  println('\tcomputer.getLog: ' + agent.getComputer().getLog());
    23  println('\tcomputer.getBuilds: ' + agent.getComputer().getBuilds());
    24}
    
  2. item = Jenkins.instance.getItemByFullName("your-job-name-here")
    
    // THIS WILL REMOVE ALL BUILD HISTORY
    item.builds.each() { build ->
      build.delete()
    }
    item.updateNextBuildNumber(1)
    
  3. Unboxing Minitel 1 2015-05-26

    Trve Minitel 1.0 build #3615

  4. A collection of misc. resources: FLOSS, ecology, architecture...

  5. Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)

    I'm currently looking for more dev-friendly solutions, the key points being:

    • writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
    • parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
    • complete feature set!
      • we don't want to just run tests...
      • coverage reports (find dead/weak/untested code sections)
      • output formatting (JUnit-XML seems to be quite a common format out there)

    There seem to be 3 solutions in Python:

    • stock unittest + project-dependent customizations / test helpers
    • nosetests
    • py.test

    And 2 ways of gettings things done:

    • keeping things stock: no external dependency, project-specific implementation...
    • using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)

    Some links:

  6. Minetest Essentials 2014-09-18

    [Core]

    [Mapper]

    [Mods:Trivia] (this is going to be an incremental section, I guess)

    [Mods:Biomes]

    [Mods:Blocks]

    [Mods:Gameplay]

    [Mods:Misc]

    [Mods:Nature]

    [Mods:Tech]

    [Mods:World]

    [Textures]