New features

[Poliana Corrêa]

Hello,

I am doing a study for my project to completion of a course that
includes the plugin for CC.
For this, I develop more features to the plugin CC as automatic
creation of tickets.

Have you ever thought that? What do you think?

I appreciate any help and / or suggestion.

Poliana Corrêa.

[velappan velappan]

Hi Poliana,

That was a nice idea to create tickets based on that failed messages.
I would like to add some more features and some for am doing the
process also I will list what are all the things I have came across

1) Ticket creation based on failure messages

2) Downloading the WAR.files as ZIP

3)Show the current build logs (i.e) the last 5 builds and

4) Some metrics based on build

These are my views share your ideas and some more if you have any
ideas.

Regards
vela.velappan

[Poliana Corrêa]

Hi vela.velappan,

Good suggestions! Thanks for your time in answering me.

I had some doubts:

Do you think interesting to show the log of the last 5 build on the current page? While you can select them in the menu on the left?
What won it?

What about the metrics you thought about that?
Already have something in mind?

See you soon,
Poliana.

2009/8/20 velappan velappan <vela...@gmail.com>

--
(>" "<)
(  'o'  )/")
(,(")(")

Poliana.

[velappan velappan]

Hi polina,

Yes, show the lat 5 builds show the others in build log history .

My view for this is create one new page called build histroy show all
the build here. Why like this means build always going to be a
increasing one if we shown all in the single page your page load will
be very high.

Add your thoughts on this :).

I thought about deriving the build log metrics based on the date how
any build and failure happens on the day week and month. What are all
your ideas.

Regards
vela.velappan

On Aug 24, 6:58 pm, Poliana Corrêa <poliana.cor...@gmail.com> wrote:
> Hi vela.velappan,
>
> Good suggestions! Thanks for your time in answering me.
>
> I had some doubts:
>
> Do you think interesting to show the log of the last 5 build on the current
> page? While you can select them in the menu on the left?
> What won it?
>
> What about the metrics you thought about that?
> Already have something in mind?
>
> See you soon,
> Poliana.
>

> 2009/8/20 velappan velappan <velapp...@gmail.com>

[Poliana Corrêa]

Hi!

Really is a good idea, but is more oriented interface.

At this point I would like to contribute something that adds more value to the plugin and its use in the process of software development.
To present my work of completion.

I'm thinking of more advanced metrics, for example, try to identify where the developer more misses and how often, among others.

What do you think?

When I started my work the focus was to automate the process of unit testing, notify the person who gave the last commit that caused the failure of the build and register the error.
However, during the research I realized that the tools for continuous integration already do that, so I'm looking for some differential for my work, see?

Believes is possible and feasible?

Hugs,
Poliana.

2009/8/25 velappan velappan <vela...@gmail.com>

[velappan velappan]

Hi Polina,

Its a nice idea showing on failure reasons and show metrics there yes that is possible you can show it.

"I'm thinking of more advanced metrics, for example, try to identify where the developer more misses and how often, among others. " This is didn't get the clear picture of it can you explain bit more on this :)

Regards
vela.velappan

2009/8/25 Poliana Corrêa <poliana...@gmail.com>

[Poliana Corrêa]

Hi Velappan,

Well, does not define what are the metrics or how to obtain them. However, I refer to measures relevant to project management and software quality.

In terms of project management could measure what stage of the project we have more failures in quality builds and identify where most developers make mistakes, encouraging them to revise their source before sending to the repository.

Ate!

[velappan velappan]

Hi Polina,

Any updates on your project. :)

On Aug 25, 5:41 pm, Poliana Corrêa <poliana.cor...@gmail.com> wrote:
> Hi Velappan,
>
> Well, does not define what are the metrics or how to obtain them. However, I
> refer to measures relevant to project management and software quality.
>
> In terms of project management could measure what stage of the project we
> have more failures in quality builds and identify where most developers make
> mistakes, encouraging them to revise their source before sending to the
> repository.
>
> Ate!
> Poliana.
>

> 2009/8/25 velappan velappan <velapp...@gmail.com>

>
>
>
> > Hi Polina,
>
> > Its a nice idea showing on failure reasons and show metrics there yes that
> > is possible you can show it.
>
> > "I'm thinking of more advanced metrics, for example, try to identify where
> > the developer more misses and how often, among others. " This is didn't get
> > the clear picture of it can you explain bit more on this :)
>
> > Regards
> > vela.velappan
>

> > 2009/8/25 Poliana Corrêa <poliana.cor...@gmail.com>

>
> > Hi!
>
> >> Really is a good idea, but is more oriented interface.
>
> >> At this point I would like to contribute something that adds more value to
> >> the plugin and its use in the process of software development.
> >> To present my work of completion.
>
> >> I'm thinking of more advanced metrics, for example, try to identify where
> >> the developer more misses and how often, among others.
>
> >> What do you think?
>
> >> When I started my work the focus was to automate the process of unit
> >> testing, notify the person who gave the last commit that caused the failure
> >> of the build and register the error.
> >> However, during the research I realized that the tools for continuous
> >> integration already do that, so I'm looking for some differential for my
> >> work, see?
>
> >> Believes is possible and feasible?
>
> >> Hugs,
> >> Poliana.
>

> >> 2009/8/25 velappan velappan <velapp...@gmail.com>