Sha256: d84cc188a41d510322e0b98d8ef720acf47a7e316ee0b817c511de7eae5062a8

Contents?: true

Size: 801 Bytes

Versions: 10

Compression:

Stored size: 801 Bytes

Contents

Feature: Running a Hudson Server
  As a hudson server administrator
  I want to be able to easily control a hudson server 
  In order to spend my time on how the process operates, not how to start stop and control it. 
  
  Scenario: Start a Hudson Server (hudson server)
    Given env variable $HOME set to project path "home"
      And "home/.hudson" folder is deleted
      And there is nothing listening on port 5001
      And there is nothing listening on port 5002
      And I cleanup any hudson processes with control port 5002
    When I run hudson server with arguments "--port 5001 --control 5002 --daemon --logfile=server.log"
    Then I should see a hudson server on port 5001
      And folder "home/.hudson/server" is created
      And folder "home/.hudson/server/javatmp" is created
    

Version data entries

10 entries across 10 versions & 1 rubygems

Version Path
hudson-0.3.1 features/launch_server.feature
hudson-0.3.0 features/launch_server.feature
hudson-0.3.0.beta.19 features/launch_server.feature
hudson-0.3.0.beta.18 features/launch_server.feature
hudson-0.3.0.beta.17 features/launch_server.feature
hudson-0.3.0.beta.16 features/launch_server.feature
hudson-0.3.0.beta.15 features/launch_server.feature
hudson-0.3.0.beta.14 features/launch_server.feature
hudson-0.3.0.beta.13 features/launch_server.feature
hudson-0.3.0.beta.12 features/launch_server.feature