-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
149
-
1
-
p4 2011.1 introduced a new feature called "streams" which is similar, but not the exactly the same as a branch. while fisheye will index commits on a "streams" depot, the streams will not be recognised as separate branches.
we should be checking for streams as well as branch specs when indexing commits.
a current workaround is to create branch specs to match the streams.
----------------
here you can see the commits that were actually made:
And the fact that all commits appear on the "head" branch:
Using the workaround, i created 2 branch specs:
MAIN (//depot/... //depot/MAIN/...)
DEV (//depot/MAIN/... //depot/DEV/...)
The commits are now represented in the following way (note the DEV branch spec):
And they appear like the following when browsing in FishEye:
 |
 |
- is duplicated by
-
- Closed
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[FE-3886] Support for Streams in p4
| Link | New: This issue depends on FECRU-8737 [ FECRU-8737 ] |
| Comment | [ My team uses Perforce with streams, and I'm evaluating moving from Helix Swarm to a more featured code review product. Due to this missing feature, and as it appears you have no intention of ever addressing this, we will unfortunately not be using Crucible. I am sure I'm not the first person to conclude this when evaluating this product. Hopefully this comment and others in this vein will eventually get this bumped up your roadmap. ] |
| Remote Link | Original: This issue links to "Page (Confluence)" [ 461555 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 461555 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3023303 ] | New: JAC Suggestion Workflow 3 [ 3639942 ] |
Bumping this again - We currently have to maintain several hacks/workarounds to use both FishEye and Bamboo as a result of this, which limits the functionality of both products.
At some point in the not distant future this will no longer be a viable option and we will need to consider other solutions.
Thanks!
| UIS | New: 149 | |
| Summary | Original: support for Streams in p4 | New: Support for Streams in p4 |
| Component/s | New: Indexing [ 41890 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2948440 ] | New: JAC Suggestion Workflow [ 3023303 ] |
Hi everyone,
thank you very much for reporting this suggestion and your involvement in the conversations around it. This suggestion is in the 'Reviewing' state which means it awaits assessment by our team.
As Fisheye and Crucible have entered basic maintenance mode, our team currently focuses more on bug-fixes and platform updates rather than on feature development. We may still deliver some small improvements if they fit into the maintenance theme. However, suggestions which have been assessed already and are in the Under consideration state have higher priority.
It means it may take time until we review this suggestion and decide whether to put it on the roadmap or reject it. You can expect an update from us in couple of months. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Kind regards
Marek Parfianowicz
Development Team Lead
Fisheye/Crucible Team