New App Release: Submodule Changes for Bitbucket

September 17, 2019
#News#Bitbucket
4 min

We have recently released a new app – Submodule Changes for Bitbucket. This free app is created to improve the experience with the Git submodule workflow. No more unreadable pull requests with changes to submodules and skipping the code review process!

Dealing with submodules can be annoying

Our company develops Awesome Graphs for Bitbucket – the app that provides the statistics for projects and repositories and helps to analyze and evaluate development team performance, code review practices and personal activity of each team member. Awesome Graphs for Bitbucket is very popular and has more than 2600 installs on the Marketplace at the moment. It’s available for Bitbucket Server, Data Center and Cloud. We use Git submodules that contain features which are similar for all the versions in order to achieve the fastest delivery.

If you use it in your projects too, you may face the situations when the commits made to a submodule are shown as two hashes in the Diff tab instead of displaying the lines of code, folders, and files that have actually been modified.

It creates the greatest difficulty to the reviewers of pull requests since there’s no chance to review changes and leave comments on the commits of the submodule repository.

Review Pull Requests Easily

If you don’t want to skip such an important part of the development process as the code review, you can try the solution we created: Submodule Changes for Bitbucket. At first, this app came as software that we were using internally, but then we discovered that lots of other developers face similar issues.

Submodule Changes for Bitbucket replaces two commit hashes with the files modified in a commit or pull request. It highlights the changes with a submodule update in the Diff tab as if all of them were made to a parental repository.

The app also gives you the possibility to watch the Blame view, leave comments and suggest improvements in pull requests. It makes the process similar to reviewing changes in the original repository.

Submodule Changes for Bitbucket is a completely free app that can simplify the code review process for the teams that use Git submodules for their projects.

Try it and see how it fits your workflow!

Related posts

    3 New Bitbucket Apps to Increase Your Productivity – Q2 2019

    September 6, 2019
    #How To#Bitbucket
    6 min

    In this blog post, we will help you kit out your Bitbucket with three new apps released in the second quarter of 2019. So if you want to check out some new interesting solutions on the Marketplace, we’ve got you covered. Needless to say, these apps will not only help you be productive but will also enhance your overall Bitbucket experience.

    Here is our selection of some of the new add-ons appeared between April 1st and June 30th:

    Let’s check how your team can benefit from using these solutions.

    Confluence Hooks for Bitbucket

    All software development products require some related documentation. If you are using Atlassian products for your software development, you need to check the Confluence Hooks for Bitbucket app. This useful app helps you link two processes: software development in Bitbucket and development of related technical documentation in Confluence.

    Now you can make sure that your software documentation is created and discussed before you make any code changes. This app allows you to identify Confluence pages by a CQL rule checking any page properties base on the Page Properties macro.

    You can define certain rules in Confluence for special use cases. If the app fails to find the related documentation in Confluence, users will see an error message and can get a hint how they can solve the problem. If a rule could not be successfully evaluated, the app prevents pushes or merges.

    Now you can easily link two processes of software development mapping the workflow between Confluence and Bitbucket.

    Pricing: Confluence Hooks for Bitbucket is free to use.

    Advanced Admin Suite for Bitbucket

    Advanced Admin Suite for Bitbucket is a powerful tool that can make Bitbucket administrator’s life easy. This app allows administrators to perform bulk operations both on projects and repositories.

    Bitbucket administrators can easily detect inactive and empty projects without repositories. They can search repositories and projects by name, permissions, activity and hooks and swiftly change settings for them.

    Administrators can easily perform activation of hooks for multiple repositories and change of access keys using this app. And all these and many more operations are available in five easy steps.

    This solution saves Bitbucket administrators time completing their everyday tasks and helps them do more in less time.

    Pricing: The pricing of Advanced Admin Suite for Bitbucket starts from $25 for 25 users and ends at $2,000 for 2,000 users.

    Pull Request Review for Bitbucket

    Pull Request Review for Bitbucket is a free plugin that provides Bitbucket users with an informative dashboard showing pull request statuses. Users can quickly change the status of their pull requests moving the cards on the dashboard from one column to another.

    This app allows you to visualize the workflow of your pull requests. You just need to move your pull request to the In review status, when you start reviewing it. Pull requests get a special badge after approval. After PR is merged the card will be moved to the Done status automatically.

    This way users can get an overview of all pull requests and effectively work with them with the help of this dashboard moving them to the proper status. You can use this neat solution to get a detailed overview of your PRs.

    Pricing: The Pull Request Review for Bitbucket app is free to use.

     

    So, if you want to improve your Bitbucket experience, give a shot to these new Bitbucket apps. Share your feedback with us in the comments below.

    Missed last quarter’s edition of the most interesting Bitbucket solutions? Check out the apps in our previous blog post.

    Don’t forget to subscribe for email notifications about new posts in our blog – enter your email in the Newsletter section on the sidebar.

    Related posts

      How to Perform Code Review and Track Team Activity in Bitbucket

      August 8, 2019
      #Case Study#How To#Bitbucket
      6 min

      Resolution Time Distribution Reports have helped a lot during the development of a high priority module to increase the reviewers, review frequency and also track team activity in Bitbucket.

      Eduard Pal, Innoface

      Innoface GmbH, one of our customers, is one of the leading providers of interfaces between PDM and ERP systems worldwide. Its applications help ensure a direct and reliable flow of information between engineering and logistics. They also offer additional products and services in order to facilitate seamless integration of the involved systems.

      Innoface product development team uses Awesome Graphs for Bitbucket mostly for making data-driven management decisions. They find it very useful to:

      • track the activity of each developer and a team in general;
      • check if code review goes according to the plans;
      • predict time to resolve pull requests.

      Let’s see how Innoface benefits from using Awesome Graphs for Bitbucket.

      Tracking team activity in Bitbucket

      Activity graph helps Innoface have a high-level overview of the total number of commits and contributors in a specific period, for example, a week. It also provides an opportunity to track the number of open pull requests from all the contributors and the repositories.

      Using this graph, the manager can assess the activeness of a contributor. This gives the manager an idea of whether an employee is following the company’s development policy or not as well.

      tracking team activity in Bitbucket

      Based on the number of open pull requests, the manager in Innoface can actually plan time to review the code and merge them. This graph also gives an opportunity to process the pull requests from the contributors that are working on the high-priority projects.

      Analyzing code review practices

      Innoface management finds Resolution Time Report very helpful when it comes to tracking the frequency of processing the pull requests.

      analyze code review in Bitbcuket

      The manager uses this report in order to see the frequency with which the reviewers are processing the pull requests. Based on the data that this report provides, it’s easier to make a reasonable decision and to assign either more reviewers or increase the frequency of the reviewers, especially for the high-priority projects.

      Predicting pull requests resolution time

      Resolution Time Distribution report helps Innoface estimate resolution time for future pull requests to make more accurate release dates planning.

      pull request resolution time in Bitbucket

      The manager of a product team uses this report in addition to the Resolution Time Report in order to estimate the resolution time for future pull requests.

      Conclusion

      Awesome Graphs greatly enriches the Bitbucket user experience for Innoface. With its help, it becomes much easier to make decisions based on data and keep an eye on how efficient their development practices are.

      Read more case studies to see how our customers benefit from using Awesome Graphs for Bitbucket in their work:

      Start a free trial of Awesome Graphs

      Related posts

        New Bitbucket Apps to Bolster Productivity – First Quarter 2019

        June 4, 2019
        #Bitbucket
        5 min

        Today we want to show you our pick of the most useful Bitbucket apps released in the first quarter of this year. We’ve chosen the most interesting ones that can help you bolster your team productivity and ease your work in Bitbucket.

        Let’s discuss each of these apps in more details.

        Add Groups to Pull Request

        Bitbucket allows you to add only individual users to pull request reviewers to notify them. Adding multiple users to this field can be a rather tedious and error-prone process. It also makes things complicated in case you have a team of people that performs code review and all the time you need to add all the members of this group to every pull request (especially if you have more than 20 RPs per day).

        The developers of Add Groups to Pull Request created the app that allows you to add a group of users or even multiple groups to a pull request. It can be very useful in situations when you don’t know every single individual of the team that will review your pull request. You can just add the required group of users. Moreover, you can also avoid the situation when all pull requests are assigned only to one person.

        The feature this simple tool suggests seems obvious and very useful to facilitate the code review process. Some more features are coming in the next release, stay tuned and we will update the blog post accordingly.

        Pricing: The price of Add Groups to Pull Request starts from $25 for 25 users and ends at $500 for 2,000 users.

        Bitbucket PlantUML Viewer

        If you deal with PlantUML diagrams in project markdown files and want to use these diagrams in Bitbucket, Bitbucket PlantUML Viewer can be a great solution. This app allows you to view these files right in your source files in Bitbucket and this add-on is free to use.

        If you want to easily view your files in various formats right in Bitbucket, you can also try File Viewer for Bitbucket Server. This app can be very useful when you need to work with CSV and TSV files as tables in Bitbucket because it provides you with a detailed view with header and sorting capability.

        You can also use this solution to view STL files as 3D models right in Bitbucket spinning them and zooming them in and out. Moreover, you can view PDF files and toggle between the pages of your PDF document on the fly. And if you deal with GeoJSON files, you can interact with maps right on Bitbucket pages.

        If you have any questions, feel free to comment on this blog post.

        Related posts

          Awesome Graphs for Bitbucket: Exclude Files from Lines of Code Statistics

          March 22, 2019
          #How To#Bitbucket
          9 min

          Awesome Graphs for Bitbucket is an app visualizing statistics of Git repositories in terms of commits, pull requests, and lines of code. The Contributors graph, and the Code Frequency graph show how many lines of code were added and deleted in the repository in general and by each developer. 

          Sometimes lines of code statistics doesn’t represent correctly the actual effort and value that developers bring to the repository. For example, if a new library was added, it will bring hundreds of new lines while a task itself was easy to do and took half an hour.

          To make your data more precise and informative, there’s a feature in Awesome Graphs that allows the exclusion of files from lines of code (LOC) statistics.

          Why Exclude Files from LOC Stats

          This feature will be helpful for users, who:

          • Include source code from third-party libraries, and don’t want to count it towards individual code contributions.
          • Want automated code generated files not to be included into LOC statistics. 
          • Version a lot of configuration in very large xml files, and don’t want to count their updates as additions of thousands of LOC.
          • Want to include in LOC statistics only files with selected extensions (i.e. c, cpp, h).
          • Want to count in LOC statistics only files from the selected directory (i.e. src).

          How it works

          Repository administrators can add patterns in a gitignore format telling what files have to be excluded from LOC statistics of a repository.  

          bitbucket repository settings

          It is possible to exclude:

          • particular files
          • all files with selected extensions
          • all files from selected directories
          • everything except files with selected extensions
          • everything except files from selected directories

          When an administrator adds or modifies patterns, Awesome Graphs re-indexes the repository and displays graphs with new LOC statistics.

          Benefits Examples

          You can see examples of this feature usage in public repositories.

          Statistics for the main directory of a repository

          Let’s view the Contributors graph for the jquery repository. It shows additions of LOC in the whole repository.

          contributors bitbucket

          The repository exists since 2006, but according to the graph there was no significant activity there till 2014.

          It would be great to make the graph more informative and calculate LOC statistics only for the directory containing the main source code – src. We exclude from statistics all files except files from this directory and get a new graph showing the most important activity happened in the key folder of the repository. 

          contributors graph bitbucket

          Exclusion of files helped to get new insights:

          • There was intensive activity in 2006-2008, 2011, and 2014.
          • There was no significant activity after 2016.
          • Only two of top four contributors to the repository are also in the top four contributors to main source code.

          In the first graph there were peaks of activity showing additions of 50K and even 250K lines of code per week. In the second graph the largest peak shows addition of 25K lines of code, others – about 5K. This data represents the real work of developers more accurately.

          Exclusion of third-party libraries from statistics

          Let’s view the  graph for the kubernetes repository.

          Bitbucket Code Frequency

          There are two peaks of activity: addition and deletion of more than 300K lines of code. They represent not actual work, but operations with third party libraries. Huge peaks of additions and deletions caused a large scale of Y axis. Due to this all other activity seems to be non-significant.

          Let’s exclude from lines of code statistics files from the directory third_party.

          The graph has become more accurate. Peak values disappeared. The scale of Y axis decreased allowing to get a better understanding of the activity in the repository.

          Get more informative LOC statistics

          Using Awesome Graphs for Bitbucket, you can enrich your commits, lines of code reporting with the REST API the app provides. For example, you can easily count each pull request size to decide whether it needs to be decreased. Read more about it in our blog post.

          Try the app for free discover more benefits and unleash the potential of your teams.

          Related posts

            3 New Bitbucket Apps to Take Care of Your PRs – Fourth Quarter 2018

            January 31, 2019
            #How To#Bitbucket
            7 min

            It can be a bit hard to keep up with all of the great new apps that appear on the Atlassian Marketplace every quarter. Luckily, we are doing the work for you and share our picks of the most interesting solutions for Atlassian products in our blog. This time we’ve chosen the most interesting apps for Bitbucket users released between October 1 and December 31.

            Check out our top 3 apps for Bitbucket Server:

            Here are the best Bitbucket apps released in the first, second and third quarters of 2018 you may have missed.

            You can also try Awesome Graphs for Bitbucket for free, this app helps you analyze the average time taken to resolve pull requests and build even more useful reports to visualize your team’s work. Learn more about how this solution can make your life easier.

            Pull Request Labels

            Pull Request Labels is an app that helps you assign labels to your pull requests to better organize your work on projects. For a big project with lots of contributors and pull requests, the capability to label PRs seems invaluable. This way all members of your team can get quick insights into a pull request seeing its state and purpose.

            After you created a label, you can use it for any pull request within the repository it is tied to signifying its priority or any other information you find useful. You can easily manage and edit labels staying on the pull request page by clicking the Edit button.

            So when you open a pull request and want your colleague to review it, you can now mark it with the Review Required label letting others know that your PR is ready for review. Just find the required label in the drop-down menu.

            You can check all labels related to the PR in the pull request table.

            This app is currently in alpha stage and its developer is planning to add more features in the nearest future.

            Pricing: Pull Request Labels is free to use.

            Prevent merge when needs work

            When you work with multiple reviewers on your pull requests, you may want to prevent merge in case one of your colleagues marks the pull request as ‘Needs Work. Prevent merge when needs work is an app that makes your merge operations easier.

            Now you can disable the Merge button when one of reviewers sets the Needs Work status on a pull request preventing the automerge.

            When one of your teammates commits new changes after approval, all approvals will be deleted.

            Pricing: Prevent merge when needs work is free to use.

            Pull request’s dependencies

            Pull request’s dependencies is a useful app if you are working on several separate projects in different Bitbucket repositories and need to make changes in one project that will later require an update to another project. Now you can create and add dependencies to all open pull requests choosing the type of dependency (blocking or non blocking).

            This app prevents you from merging PRs with open pull requests in dependencies. You can see the detailed list of related dependencies with their statuses.

            You can add several dependent pull requests from any project and repository. If you activate the Is blocker for merge option during this process, you can close the current pull request only when the linked one is closed.

            This app also allows you to remove any irrelevant dependencies.

            Pricing: The price of Pull request’s dependencies starts from $25 for 25 users and ends at $2,000 for 2,000 users.

            If you have any questions, feel free to comment on this blog post. Stay tuned and subscribe for email notifications about new posts in our blog – enter your email in the ‘Newsletter’ section on the sidebar.

             

             

             

            Related posts