[#BAM-1096] Change the way bamboo detects changes in perforce

Bamboo

Change the way bamboo detects changes in perforce

Created: 03/Apr/07 06:12 PM Updated: 11/Apr/07 08:34 PM

Component/s:

Build Triggers

Affects Version/s:

1.0.3

Fix Version/s:

1.0.4

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~BAM-750~~ Perforce changes are not displayed when a manual build is executed

Reference

This issue relates to:

~~BAM-979~~ Different time zone on Perforce server does not work

Participants:	Brydie McCoy [Atlassian]
Since last comment:	1 year, 18 weeks, 5 days ago
Internal Work Bucket:	Confirmed
Number of comments:	1
Labels:

Description

« Hide

Currently bamboo uses the time stamp of the last build to detect changes. If the bamboo server clock is out of sync with the perforce server clock, then bamboo can easily miss changes and not trigger builds if there are changes.

Therefore, bamboo needs to change the way it detects changes.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brydie McCoy [Atlassian] added a comment - 11/Apr/07 08:20 PM

Hi,

Bamboo has now been configured to use perforce change numbers rather than time stamps to detect changes. This should resolve any time based issues that were occuring.

These changes will be included in release 1.0.4 (to be released this week) .

Cheers
Brydie