Details
-
Bug
-
Resolution: Fixed
-
Medium
-
1.0.2
-
None
-
Bamboo version:
standalone 1.0.2Wednesday, 14 Mar 2007
User Timezone:
US/CentralUser Locale:
English (United States)System Encoding:
UTF-8Operating System:
Linux 2.6.9-42.0.8.ELsmpOperating System Architecture:
i386Available Processors:
2Application Server Container:
Jetty/5.1.4Java Version:
1.5.0_11Java Vendor:
Sun Microsystems Inc.JVM Version:
1.0JVM Vendor:
Sun Microsystems Inc.JVM Implementation Version:
1.5.0_11-b03Java Runtime:
Java(TM) 2 Runtime Environment, Standard EditionJava VM:
Java HotSpot(TM) Server VM
Java VM Memory Statistics
Total Memory:
466 MBFree Memory:
340 MBUsed Memory:
126 MBBamboo version: standalone 1.0.2 Wednesday, 14 Mar 2007 User Timezone: US/Central User Locale: English (United States) System Encoding: UTF-8 Operating System: Linux 2.6.9-42.0.8.ELsmp Operating System Architecture: i386 Available Processors: 2 Application Server Container: Jetty/5.1.4 Java Version: 1.5.0_11 Java Vendor: Sun Microsystems Inc. JVM Version: 1.0 JVM Vendor: Sun Microsystems Inc. JVM Implementation Version: 1.5.0_11-b03 Java Runtime: Java(TM) 2 Runtime Environment, Standard Edition Java VM: Java HotSpot(TM) Server VM Java VM Memory Statistics Total Memory: 466 MB Free Memory: 340 MB Used Memory: 126 MB
Description
Yesterday (13 March 2007) at 15:08:22 and 22:00:26, code was checked into our Subversion repository and the plans were not executed. We have two plans set up and the source repository configuration for both is:
Repository: Subversion
Repository URL: svn+ssh://svn.xxx.xxx.xxx/xxx/xxx/xxx/xxx/xxx/xxx
Username: xxx
Web Repository URL: http://xxx.xxx.xxx.xxx
Build Strategy: Repository Polling
Polling Frequency: 180
See atlassian-bamboo.log for more info
