[#BAM-1152] Bamboo should accept repository triggers for Perforce builds

Bamboo

Bamboo should accept repository triggers for Perforce builds

Created: 25/Apr/07 08:41 AM Updated: 20/Jul/07 08:11 PM

Component/s:

Build Triggers, Repository (Perforce)

Affects Version/s:

1.0.5, 1.1, 1.1.1, 1.1.2

Fix Version/s:

1.2

Time Tracking:

Not Specified

Participants:	Ajay Sridhar [Atlassian], Bob Swift, Brydie McCoy [Atlassian] and Richard Hyde
Since last comment:	1 year, 11 weeks, 2 days ago
Number of comments:	5
Labels:

Description

« Hide

The documentation says Perforce does not support build triggers to kick off a build on a commit. Looking at the perforce documentation, it appears that there is a change-commit trigger that can do the appropriate thing. http://perforce.com/perforce/doc.062/manuals/p4sag/06_scripting.html#1061665

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Ajay Sridhar [Atlassian] added a comment - 25/Apr/07 09:21 PM

Hi Bob,

Thank you for raising the issue. I have corrected the confluence document with regards to perforce triggers.

Cheers,
Ajay

[ Permlink | « Hide ]

Richard Hyde added a comment - 15/Jun/07 05:58 PM

Would love to see this actually work. IMO a pretty big chunk of functionality missing for the perforce integration. As the reporter pointed out, perforce has all the needed functionality to make this happen.

[ Permlink | « Hide ]

Richard Hyde added a comment - 19/Jun/07 12:32 PM

When trying to start on of these builds manually using the REST API (or through a P4 trigger), the PerforceRepository.java will throw a UnsupportedOperationException when trying to execute the getHost() method. I'm not sure why the host of the repository is relevant for kicking off a build but ....

It's easy to get the host of the repository in perforce.

The "p4 info" command returns ...

User name: user
Client name: client
Client host: foo.example.com
Client root: /home/user/localsource
Current directory: /home/user
Client address: 192.168.1.200:50014
Server address: perforce.server.example.com:1666
Server root: /home/perforce/repository
Server date: 2007/06/19 10:26:13 -0700 PDT
Server version: P4D/LINUX26X86/2007.2/122958 (2007/05/23)
Server license: Some Company 10 users (support ends 2007/06/20)

Unless there is something else blocking builds via the REST API this should be an easy one to fix.

[ Permlink | « Hide ]

Brydie McCoy [Atlassian] added a comment - 24/Jun/07 07:41 PM

Hi,

Thanks for your help, Perforce build triggering will now be a 'supported operation'. The changes will be included with release 1.2 - coming soon !!

Cheers,
Brydie

[ Permlink | « Hide ]

Richard Hyde added a comment - 20/Jul/07 08:11 PM

Rock on. Upgraded to 1.2.1 and Perforce triggering is working great! Thanks for getting it in so quickly.