-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
0
-
Anywhere that references a change should (please?) have a web link to the Perforce changlist, or file, that changed (like in Jira!) Knowing what changed is a good start, but it would be convenient to be able to click on it and see the dffs, history, etc.
- relates to
-
BAM-823 Web Repository URL is not persisted for Perforce repositories
-
- Closed
-
[BAM-682] Add web link to perforce changelist
I unvoted for this now that we have moved to Fisheye. It is a much better solution verses p4web.
Thomas Wehner
added a comment - Hi,
I have recently posted our experiences with Perforce Web Repository URLs to the Bamboo forum (http://forums.atlassian.com/thread.jspa?threadID=21748). There, I have indicated what we think the correct syntax for p4web links should be. The complete P4Web URL Reference reference can be found here: http://www.perforce.com/perforce/doc.072/manuals/p4web/help/actioncodes.html.
Thomas
Thomas Wehner
added a comment - Hi,
I have recently posted our experiences with Perforce Web Repository URLs to the Bamboo forum ( http://forums.atlassian.com/thread.jspa?threadID=21748 ). There, I have indicated what we think the correct syntax for p4web links should be. The complete P4Web URL Reference reference can be found here: http://www.perforce.com/perforce/doc.072/manuals/p4web/help/actioncodes.html .
Thomas Hi Matt,
Just letting you know that since Bamboo 1.1.2 Perforce change links have been setup to work for Fisheye. Unfortunately we still dont have anything available for p4web.
Cheers,
Brydie
MattyJ
added a comment - The general format for p4web URL's (pointing to a changelist) is:
http://[P4WEBPORT]/@md=d&cd=//&c=8XD@/30597?ac=10
"30597" is the changelist number. The rest of the parameters have to do with how the web page is displayed and whatnot. It looks a little odd/weird, but it looks to be consistent across the dozen or so changelists I just opened. I've been using this format for our notification e-mails for over three years and it hasn't changed.
To get the changelist of a particular revision of a file you can do an API call equivalent to something like this:
p4 changes -m 1 //Installation/main/OnlineActivationWebInstaller.wix/OnlineActivationWebInstaller.wxs#12
Which will yield this, where you can parse out the changelist number.
Change 30597 on 2007/01/10 by matthewja@__automation 'Adding Attempts logfile path ed'
They're online documentation doesn't seem to have any API kinds of things, just user stuff. You might want to E-mail Perforce to see if they can provide that.
Thanks!
-Matt
MattyJ
added a comment - The general format for p4web URL's (pointing to a changelist) is:
http://[P4WEBPORT]/@md=d&cd=//&c=8XD@/30597?ac=10
"30597" is the changelist number. The rest of the parameters have to do with how the web page is displayed and whatnot. It looks a little odd/weird, but it looks to be consistent across the dozen or so changelists I just opened. I've been using this format for our notification e-mails for over three years and it hasn't changed.
To get the changelist of a particular revision of a file you can do an API call equivalent to something like this:
p4 changes -m 1 //Installation/main/OnlineActivationWebInstaller.wix/OnlineActivationWebInstaller.wxs#12
Which will yield this, where you can parse out the changelist number.
Change 30597 on 2007/01/10 by matthewja@__automation 'Adding Attempts logfile path ed'
They're online documentation doesn't seem to have any API kinds of things, just user stuff. You might want to E-mail Perforce to see if they can provide that.
Thanks!
-Matt Matty,
Anywhere that references a change should (please?) have a web link to the Perforce changlist
We'd love to do this! We've already done this for CVS & SVN, but our experience with Perforce is a little more limited.
Can you tell us the format of the link to a perforce changelist? Or point out to use where we could go a try to find out that information?
Thanks
Mark C
Hi everyone,
Thank you for your interest in this issue but we're unable to implement all of the excellent suggestions you make.
We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including:
We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.
To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Bamboo Team