• 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.

      There are both advanced and very simple Clover gadgets written during ShipIt attack of the Gadgets, looking for a good server home.
      see also: CLOV-561

      This could be a quick win piece of low hanging fruit.

      Lets start with the simplest form of Clover gadget: "Display the Red/Green Clover Coverage bar".
      e.g.

      This gadget will:

      • pull the coverage data from a user specified Artifact (that is a Clover HTML report) from the latest Bamboo build for a specified Bamboo Plan
      • render a red/green coverage bar showing the percentage of code coverage for a specific project
      • display the raw total percentage figure
      • support all gadget display sizes

      If the Artifact points to the root directory of a Clover HTML report, then the gadget can assume there will be a 'project.js' available.
      e.g. http://clover.atlassian.com/browse/webtest/project.js

      If the Artifact points to a single .js file (presumably project.js), the gadget should just use it as the data source.

      An example gadget (done during ShipIt 10) is available on Labs: http://labs.atlassian.com/browse/GOGO .
      The sub-project 'clover' contains the gadget: http://labs.atlassian.com/svn/GOGO/trunk/src/clover/ .
      This gadget is actually deployed and can be installed in any Open Social container. The URL is: http://labs.atlassian.com/gadgets/npellow/src/clover-gadget.xml

      This gadget also uses the historical json to generate a visualization of coverage and project metric trends. This can be added to the gadget for a phase #2.

        1. clover-gadget-config.png
          19 kB
          Krystian Brazulewicz
        2. clover-gadget-view.png
          16 kB
          Krystian Brazulewicz
        3. clover-gadget-view-2.png
          19 kB
          Krystian Brazulewicz

            [BAM-4364] Expose a single Clover Gadget via Bamboo

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3550190 ] New: JAC Suggestion Workflow 3 [ 3611954 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Backlog Order (Obsolete) Original: 18770000000
            Parent Original: BAM-4048 [ 86651 ]
            Workflow Original: JAC Sub-task Workflow [ 3380171 ] New: JAC Suggestion Workflow [ 3550190 ]
            Issue Type Original: Sub-task [ 6 ] New: Suggestion [ 10000 ]
            Priority Original: Low [ 4 ]
            Status Original: Closed [ 6 ] New: RESOLVED [ 5 ]
            set-jac-bot made changes -
            Link New: This issue is detailed by BAM-4048 [ BAM-4048 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1436599 ] New: JAC Sub-task Workflow [ 3380171 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1418226 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1436599 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 609409 ] New: Bamboo Workflow 2016 v1 [ 1418226 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2014 [ 601424 ] New: Bamboo Workflow 2014 v2 [ 609409 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2010 [ 202989 ] New: Bamboo Workflow 2014 [ 601424 ]
            LyA made changes -
            Description Original: There are both advanced and very simple Clover gadgets written during ShipIt attack of the Gadgets, looking for a good server home.
            see also: CLOV-561

            This could be a quick win piece of low hanging fruit.

            Lets start with the simplest form of Clover gadget: "Display the Red/Green Clover Coverage bar".
            e.g.
            !http://img.skitch.com/20090824-ti2wwfuet8mfaqpw8hiw8h6k8a.jpg!

            This gadget will:
             * pull the coverage data from a user specified Artifact (that is a Clover HTML report) from the latest Bamboo build for a specified Bamboo Plan
             * render a red/green coverage bar showing the percentage of code coverage for a specific project
             * display the raw total percentage figure
             * support all gadget display sizes

            If the Artifact points to the root directory of a Clover HTML report, then the gadget can assume there will be a 'project.js' available.
            e.g. http://clover.atlassian.com/browse/webtest/project.js

            If the Artifact points to a single .js file (presumably project.js), the gadget should just use it as the data source.

            An example gadget (done during FedEx 10) is available on Labs: http://labs.atlassian.com/browse/GOGO .
            The sub-project 'clover' contains the gadget: http://labs.atlassian.com/svn/GOGO/trunk/src/clover/ .
            This gadget is actually deployed and can be installed in any Open Social container. The URL is: http://labs.atlassian.com/gadgets/npellow/src/clover-gadget.xml

            This gadget also uses the historical json to generate a visualization of coverage and project metric trends. This can be added to the gadget for a phase #2.




            New: There are both advanced and very simple Clover gadgets written during ShipIt attack of the Gadgets, looking for a good server home.
            see also: CLOV-561

            This could be a quick win piece of low hanging fruit.

            Lets start with the simplest form of Clover gadget: "Display the Red/Green Clover Coverage bar".
            e.g.
            !http://img.skitch.com/20090824-ti2wwfuet8mfaqpw8hiw8h6k8a.jpg!

            This gadget will:
             * pull the coverage data from a user specified Artifact (that is a Clover HTML report) from the latest Bamboo build for a specified Bamboo Plan
             * render a red/green coverage bar showing the percentage of code coverage for a specific project
             * display the raw total percentage figure
             * support all gadget display sizes

            If the Artifact points to the root directory of a Clover HTML report, then the gadget can assume there will be a 'project.js' available.
            e.g. http://clover.atlassian.com/browse/webtest/project.js

            If the Artifact points to a single .js file (presumably project.js), the gadget should just use it as the data source.

            An example gadget (done during ShipIt 10) is available on Labs: http://labs.atlassian.com/browse/GOGO .
            The sub-project 'clover' contains the gadget: http://labs.atlassian.com/svn/GOGO/trunk/src/clover/ .
            This gadget is actually deployed and can be installed in any Open Social container. The URL is: http://labs.atlassian.com/gadgets/npellow/src/clover-gadget.xml

            This gadget also uses the historical json to generate a visualization of coverage and project metric trends. This can be added to the gadget for a phase #2.




            LyA made changes -
            Description Original: There are both advanced and very simple Clover gadgets written during FedEx attack of the Gadgets, looking for a good server home.
            see also: CLOV-561

            This could be a quick win piece of low hanging fruit.

            Lets start with the simplest form of Clover gadget: "Display the Red/Green Clover Coverage bar".
            e.g.
            !http://img.skitch.com/20090824-ti2wwfuet8mfaqpw8hiw8h6k8a.jpg!

            This gadget will:
             * pull the coverage data from a user specified Artifact (that is a Clover HTML report) from the latest Bamboo build for a specified Bamboo Plan
             * render a red/green coverage bar showing the percentage of code coverage for a specific project
             * display the raw total percentage figure
             * support all gadget display sizes

            If the Artifact points to the root directory of a Clover HTML report, then the gadget can assume there will be a 'project.js' available.
            e.g. http://clover.atlassian.com/browse/webtest/project.js

            If the Artifact points to a single .js file (presumably project.js), the gadget should just use it as the data source.

            An example gadget (done during FedEx 10) is available on Labs: http://labs.atlassian.com/browse/GOGO .
            The sub-project 'clover' contains the gadget: http://labs.atlassian.com/svn/GOGO/trunk/src/clover/ .
            This gadget is actually deployed and can be installed in any Open Social container. The URL is: http://labs.atlassian.com/gadgets/npellow/src/clover-gadget.xml

            This gadget also uses the historical json to generate a visualization of coverage and project metric trends. This can be added to the gadget for a phase #2.




            New: There are both advanced and very simple Clover gadgets written during ShipIt attack of the Gadgets, looking for a good server home.
            see also: CLOV-561

            This could be a quick win piece of low hanging fruit.

            Lets start with the simplest form of Clover gadget: "Display the Red/Green Clover Coverage bar".
            e.g.
            !http://img.skitch.com/20090824-ti2wwfuet8mfaqpw8hiw8h6k8a.jpg!

            This gadget will:
             * pull the coverage data from a user specified Artifact (that is a Clover HTML report) from the latest Bamboo build for a specified Bamboo Plan
             * render a red/green coverage bar showing the percentage of code coverage for a specific project
             * display the raw total percentage figure
             * support all gadget display sizes

            If the Artifact points to the root directory of a Clover HTML report, then the gadget can assume there will be a 'project.js' available.
            e.g. http://clover.atlassian.com/browse/webtest/project.js

            If the Artifact points to a single .js file (presumably project.js), the gadget should just use it as the data source.

            An example gadget (done during FedEx 10) is available on Labs: http://labs.atlassian.com/browse/GOGO .
            The sub-project 'clover' contains the gadget: http://labs.atlassian.com/svn/GOGO/trunk/src/clover/ .
            This gadget is actually deployed and can be installed in any Open Social container. The URL is: http://labs.atlassian.com/gadgets/npellow/src/clover-gadget.xml

            This gadget also uses the historical json to generate a visualization of coverage and project metric trends. This can be added to the gadget for a phase #2.




              kbrazulewicz Krystian Brazulewicz
              npellow Nick
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

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