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

      Key areas of focus:

      1. Automatically track and link through to Clovers HTML reports
      2. 'One-click' clover integration into Ant and Maven2 builds
      3. Improved support for Clover in a mult-agent build environment
      4. exposing Clover's line level coverage data via a REST api
      5. host Clover gadgets to allow other applications to embed Clover data

            [BAM-4048] Improve Clover-Bamboo Plugin

            Nick added a comment - - edited

            where SWAG == Stupid Wild-Ass Guess ?

            Sounds good. 1 and 2 is slightly ambiguous already on this page - could you please clarify.
            cheers,
            nick

            UPDATE Thanks for the clarification, Paul.

            Nick added a comment - - edited where SWAG == Stupid Wild-Ass Guess ? Sounds good. 1 and 2 is slightly ambiguous already on this page - could you please clarify. cheers, nick UPDATE Thanks for the clarification, Paul.

            sladey added a comment - - edited

            Bamboo assume that Nick will do the following and submit patches for Bamboo for review.

            • Provide a plugin point to decorate the builder command line
            • Return builds related to a changeset or file revision via remote API

            The Bamboo team will do the remaining items. SWAG for remaining items is 2-3 weeks.

            • Allow artifacts to be passed from Server to Agent
            • Provide Plan level artifacts in Bamboo
            • Provide means to store 'system artifacts' - that can be configured by plugins

            We (ie Bamboo) will do these in the first 1 or 2 iterations of 2.4. We can determine the order we do them in based on what is good for Nick. We will do all three, although with "host Clover gadgets to allow other applications to embed Clover data" I assum you mean publish Clover gadgets to other apps that have dashboards like JIRA. We could release this work in something like a 2.3.1 if it helps get Clover 2.6 get to market quicker.

            sladey added a comment - - edited Bamboo assume that Nick will do the following and submit patches for Bamboo for review. Provide a plugin point to decorate the builder command line Return builds related to a changeset or file revision via remote API The Bamboo team will do the remaining items. SWAG for remaining items is 2-3 weeks. Allow artifacts to be passed from Server to Agent Provide Plan level artifacts in Bamboo Provide means to store 'system artifacts' - that can be configured by plugins We (ie Bamboo) will do these in the first 1 or 2 iterations of 2.4. We can determine the order we do them in based on what is good for Nick. We will do all three, although with "host Clover gadgets to allow other applications to embed Clover data" I assum you mean publish Clover gadgets to other apps that have dashboards like JIRA. We could release this work in something like a 2.3.1 if it helps get Clover 2.6 get to market quicker.

            MarkC added a comment -
            1. Provide a plugin point to decorate the builder command line
            2. Return builds related to a changeset or file revision via remote API

            Are something that can be picked up

            The rest will need more speccing work

            MarkC added a comment - Provide a plugin point to decorate the builder command line Return builds related to a changeset or file revision via remote API Are something that can be picked up The rest will need more speccing work

              Unassigned Unassigned
              npellow Nick
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: