Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-853

If you specify an includes, only request the included paths, rather than requesting all paths then filtering out those that do not belong to the includes.

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Created from FSH-1378.

      If I create a repository with branch //depot/dir1/dir2/dir3 with no includes/excludes specified I get exactly what I expect. I would also expect to get exactly the same results if I specified the same branch using a different root and using include directories. ie, branch //depot and include directory dir1/dir2/dir3. However, this second configuration results in the entire depot being scanned which eventually dies because of maxScanRows being exceeded.

            [FE-853] If you specify an includes, only request the included paths, rather than requesting all paths then filtering out those that do not belong to the includes.

            Marek Parfianowicz added a comment -
            Atlassian Update – 5 October 2018

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Regards
            Marek Parfianowicz
            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 5 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

            MSDE added a comment -

            This fix would be greatly appreciated.

            Testing shows on the new 2.1.3 release, only scanning the 'needed' areas as separate repositories is nearly 70% faster than trying to run using an 'include'. Disk Drive usage is 50% higher on repositories using "include" or "exclude".

            MSDE added a comment - This fix would be greatly appreciated. Testing shows on the new 2.1.3 release, only scanning the 'needed' areas as separate repositories is nearly 70% faster than trying to run using an 'include'. Disk Drive usage is 50% higher on repositories using "include" or "exclude".

            MSDE added a comment -

            See FSH-1941 as well

            This is a critical fix. It is causing many issues here.

            MSDE added a comment - See FSH-1941 as well This is a critical fix. It is causing many issues here.

            BrendanA added a comment -

            estimate from Conor

            BrendanA added a comment - estimate from Conor

            Partha added a comment -

            One possible solution may be to change the depot path from being a
            single branch to a multiple branch path similar to the UNIX shell PATH
            environment variable, e,g.
            //depot/main/<project>://depot/dev/<project>://depot/release/<project>
            and restrict the initial scan to each of these root branches.

            Partha added a comment - One possible solution may be to change the depot path from being a single branch to a multiple branch path similar to the UNIX shell PATH environment variable, e,g. //depot/main/<project>://depot/dev/<project>://depot/release/<project> and restrict the initial scan to each of these root branches.

              Unassigned Unassigned
              pkamal Partha
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - 32h
                  32h
                  Remaining:
                  Remaining Estimate - 32h
                  32h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified