Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Pavel Georgiev-3
Hi,

I wanted to ask if it is possible to gather the time it takes to execute each of the build steps (as a starter) and display it somehow? Part of an efficient CI solution is to have fast builds, but if the build consists of several steps and you do not know the time it takes to complete each step it is very difficult to analyze and decide what to improve.

Thanks in advance.
Reply | Threaded
Open this post in threaded view
|

RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

Adam Purkiss
if you have an ant script you could echo a message with times maybe ? and then manually scan the output for those log messages. Not aware of a plugin that does it
 
Possibly a modifies descriptor plugin could bring up all matches of a reg ex and the reg ex picks up the ant messages. It could then set a builds description to those times.





Date: Sat, 17 May 2008 14:40:33 -0700
From: [hidden email]
To: [hidden email]
Subject: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Hi,

I wanted to ask if it is possible to gather the time it takes to execute each of the build steps (as a starter) and display it somehow? Part of an efficient CI solution is to have fast builds, but if the build consists of several steps and you do not know the time it takes to complete each step it is very difficult to analyze and decide what to improve.

Thanks in advance.


Reply | Threaded
Open this post in threaded view
|

RE: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

Lehman, Curtis

If you doing the build on a UNIX machine, you could insert into the scripts you’re build scripts calls to the UNIX time option. The command will report how long it takes to do specific action. It might not help you with the portions of the build that are done automatically from Hudson, but maybe it’s a start. You might also have access to a similar time command if you use something like Cygwin or MSK tools in your build.

 


From: Adam Purkiss [mailto:[hidden email]]
Sent: Saturday, May 17, 2008 3:45 PM
To: [hidden email]
Subject: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

 

if you have an ant script you could echo a message with times maybe ? and then manually scan the output for those log messages. Not aware of a plugin that does it
 
Possibly a modifies descriptor plugin could bring up all matches of a reg ex and the reg ex picks up the ant messages. It could then set a builds description to those times.




Date: Sat, 17 May 2008 14:40:33 -0700
From: [hidden email]
To: [hidden email]
Subject: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Hi,

I wanted to ask if it is possible to gather the time it takes to execute each of the build steps (as a starter) and display it somehow? Part of an efficient CI solution is to have fast builds, but if the build consists of several steps and you do not know the time it takes to complete each step it is very difficult to analyze and decide what to improve.

Thanks in advance.

 


Reply | Threaded
Open this post in threaded view
|

Re: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

Pavel Georgiev-3
Thanks for the feedback.

I still think that this should be done by hudson as this should be easier and i would not have to modify the build scripts to get these statistics:).

On Mon, May 19, 2008 at 8:31 AM, Lehman, Curtis <[hidden email]> wrote:

If you doing the build on a UNIX machine, you could insert into the scripts you're build scripts calls to the UNIX time option. The command will report how long it takes to do specific action. It might not help you with the portions of the build that are done automatically from Hudson, but maybe it's a start. You might also have access to a similar time command if you use something like Cygwin or MSK tools in your build.

 


From: Adam Purkiss [mailto:[hidden email]]
Sent: Saturday, May 17, 2008 3:45 PM

Subject: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

 

if you have an ant script you could echo a message with times maybe ? and then manually scan the output for those log messages. Not aware of a plugin that does it
 
Possibly a modifies descriptor plugin could bring up all matches of a reg ex and the reg ex picks up the ant messages. It could then set a builds description to those times.




Date: Sat, 17 May 2008 14:40:33 -0700
From: [hidden email]
To: [hidden email]
Subject: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Hi,

I wanted to ask if it is possible to gather the time it takes to execute each of the build steps (as a starter) and display it somehow? Part of an efficient CI solution is to have fast builds, but if the build consists of several steps and you do not know the time it takes to complete each step it is very difficult to analyze and decide what to improve.

Thanks in advance.

 



Reply | Threaded
Open this post in threaded view
|

RE: Re: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

Lehman, Curtis

I agree, it would be a nice feature on Hudson.

 

Just throwing out an idea, but I was wondering if it could be as simple as changing the prompt from [workspace] $ to one that was [<time>:<pwd>]. Most UNIX and windows shells allow the prompt to contain this. It would be probably only accurate to the minute, but I was thinking that would give you a good idea of witch peaces were taking the longest. I’m guessing that anything less than a minute probably wouldn’t be worth bothering with.

 

Thanks,
Curt


From: Pavel Georgiev [mailto:[hidden email]]
Sent: Monday, May 19, 2008 9:42 AM
To: [hidden email]
Subject: Re: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

 

Thanks for the feedback.

I still think that this should be done by hudson as this should be easier and i would not have to modify the build scripts to get these statistics:).

On Mon, May 19, 2008 at 8:31 AM, Lehman, Curtis <[hidden email]> wrote:

If you doing the build on a UNIX machine, you could insert into the scripts you're build scripts calls to the UNIX time option. The command will report how long it takes to do specific action. It might not help you with the portions of the build that are done automatically from Hudson, but maybe it's a start. You might also have access to a similar time command if you use something like Cygwin or MSK tools in your build.

 


From: Adam Purkiss [mailto:[hidden email]]
Sent: Saturday, May 17, 2008 3:45 PM

Subject: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

 

if you have an ant script you could echo a message with times maybe ? and then manually scan the output for those log messages. Not aware of a plugin that does it
 
Possibly a modifies descriptor plugin could bring up all matches of a reg ex and the reg ex picks up the ant messages. It could then set a builds description to those times.



Date: Sat, 17 May 2008 14:40:33 -0700
From: [hidden email]
To: [hidden email]
Subject: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Hi,

I wanted to ask if it is possible to gather the time it takes to execute each of the build steps (as a starter) and display it somehow? Part of an efficient CI solution is to have fast builds, but if the build consists of several steps and you do not know the time it takes to complete each step it is very difficult to analyze and decide what to improve.

Thanks in advance.

 


 

Reply | Threaded
Open this post in threaded view
|

Re: Re: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

Pavel Georgiev-3
An accuracy up to the minute is ok. It would be also nice if i can compare the stats between two builds and easily see if there is an improvement in any pf the steps (green, red colors, etc) :).

On Mon, May 19, 2008 at 8:52 AM, Lehman, Curtis <[hidden email]> wrote:

I agree, it would be a nice feature on Hudson.

 

Just throwing out an idea, but I was wondering if it could be as simple as changing the prompt from [workspace] $ to one that was [<time>:<pwd>]. Most UNIX and windows shells allow the prompt to contain this. It would be probably only accurate to the minute, but I was thinking that would give you a good idea of witch peaces were taking the longest. I'm guessing that anything less than a minute probably wouldn't be worth bothering with.

 

Thanks,
Curt


From: Pavel Georgiev [mailto:[hidden email]]
Sent: Monday, May 19, 2008 9:42 AM

Subject: Re: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

 

Thanks for the feedback.

I still think that this should be done by hudson as this should be easier and i would not have to modify the build scripts to get these statistics:).

On Mon, May 19, 2008 at 8:31 AM, Lehman, Curtis <[hidden email]> wrote:

If you doing the build on a UNIX machine, you could insert into the scripts you're build scripts calls to the UNIX time option. The command will report how long it takes to do specific action. It might not help you with the portions of the build that are done automatically from Hudson, but maybe it's a start. You might also have access to a similar time command if you use something like Cygwin or MSK tools in your build.

 


From: Adam Purkiss [mailto:[hidden email]]
Sent: Saturday, May 17, 2008 3:45 PM

Subject: RE: Display time to execute each of the build steps (and any other steps, like deploy, scp the artif

 

if you have an ant script you could echo a message with times maybe ? and then manually scan the output for those log messages. Not aware of a plugin that does it
 
Possibly a modifies descriptor plugin could bring up all matches of a reg ex and the reg ex picks up the ant messages. It could then set a builds description to those times.



Date: Sat, 17 May 2008 14:40:33 -0700
From: [hidden email]
To: [hidden email]
Subject: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Hi,

I wanted to ask if it is possible to gather the time it takes to execute each of the build steps (as a starter) and display it somehow? Part of an efficient CI solution is to have fast builds, but if the build consists of several steps and you do not know the time it takes to complete each step it is very difficult to analyze and decide what to improve.

Thanks in advance.

 


 


Reply | Threaded
Open this post in threaded view
|

Re: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Kohsuke Kawaguchi
Administrator
In reply to this post by Pavel Georgiev-3
Pavel Georgiev wrote:
> Hi,
>
> I wanted to ask if it is possible to gather the time it takes to execute
> each of the build steps (as a starter) and display it somehow? Part of an
> efficient CI solution is to have fast builds, but if the build consists of
> several steps and you do not know the time it takes to complete each step it
> is very difficult to analyze and decide what to improve.

When you say "each step", what granularity are you talking about?

I guess the solution depends on that a lot.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Pavel Georgiev-3
As a starters the "build steps" (Build Section). Actually these are the most important ones. I was also thinking about "Deploy WAR", and maybe "Publish artefacts to SCP repository" but these do not seem that important.

On Mon, May 19, 2008 at 10:56 AM, Kohsuke Kawaguchi <[hidden email]> wrote:
Pavel Georgiev wrote:
Hi,

I wanted to ask if it is possible to gather the time it takes to execute
each of the build steps (as a starter) and display it somehow? Part of an
efficient CI solution is to have fast builds, but if the build consists of
several steps and you do not know the time it takes to complete each step it
is very difficult to analyze and decide what to improve.

When you say "each step", what granularity are you talking about?

I guess the solution depends on that a lot.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Kohsuke Kawaguchi
Administrator
Pavel Georgiev wrote:
> As a starters the "build steps" (Build Section). Actually these are the most
> important ones. I was also thinking about "Deploy WAR", and maybe "Publish
> artefacts to SCP repository" but these do not seem that important.

Ah, OK, so it's only at Hudson level.

I briefly thought maybe you wanted to go deep inside Ant or something.

Hudson should be able to keep track of the drill down and show the time.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Michael Wiles
I find that every hudson job that is executed consists of 3 steps...

1. update from SCM
2. Run ant/maven
3. Do Post processing, i.e. pull build artifacts, publish test reports etc

Hudson clearly documents how long 2 takes, and when there are 2 steps, each step's time is logged.

Would however be nice to know how long 1st and 3rd steps took. For instance, when transferring large files from windows to linux (windows slave) it is _very_ slow, though it is unknown exactly how long it takes. And if you have a really big source tree if you knew how long the scm update/checkout was taking you might take steps to optimise that area.

On Mon, May 19, 2008 at 9:03 PM, Kohsuke Kawaguchi <[hidden email]> wrote:
Pavel Georgiev wrote:
As a starters the "build steps" (Build Section). Actually these are the most
important ones. I was also thinking about "Deploy WAR", and maybe "Publish
artefacts to SCP repository" but these do not seem that important.

Ah, OK, so it's only at Hudson level.

I briefly thought maybe you wanted to go deep inside Ant or something.

Hudson should be able to keep track of the drill down and show the time.


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]



--
see my blog:
http://analysis102.blogspot.com
http://audiblethoughts.blogspot.com
http://outsideofficehours.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Pavel Georgiev-3
Inline.

On Tue, May 20, 2008 at 6:51 AM, Michael Wiles <[hidden email]> wrote:
I find that every hudson job that is executed consists of 3 steps...

1. update from SCM
2. Run ant/maven
3. Do Post processing, i.e. pull build artifacts, publish test reports etc

Hudson clearly documents how long 2 takes, and when there are 2 steps, each step's time is logged.
 
[Pavel] I have a job with 3 build steps and all i see is the total time. Where can i see thew info for each steps?


Would however be nice to know how long 1st and 3rd steps took. For instance, when transferring large files from windows to linux (windows slave) it is _very_ slow, though it is unknown exactly how long it takes. And if you have a really big source tree if you knew how long the scm update/checkout was taking you might take steps to optimise that area.
 
[Pavel] Seems that i forgot about the SCM update. This is also very important.


On Mon, May 19, 2008 at 9:03 PM, Kohsuke Kawaguchi <[hidden email]> wrote:
Pavel Georgiev wrote:
As a starters the "build steps" (Build Section). Actually these are the most
important ones. I was also thinking about "Deploy WAR", and maybe "Publish
artefacts to SCP repository" but these do not seem that important.

Ah, OK, so it's only at Hudson level.

I briefly thought maybe you wanted to go deep inside Ant or something.

Hudson should be able to keep track of the drill down and show the time.


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]



--
see my blog:
http://analysis102.blogspot.com
http://audiblethoughts.blogspot.com
http://outsideofficehours.blogspot.com

Reply | Threaded
Open this post in threaded view
|

Re: Display time to execute each of the build steps (and any other steps, like deploy, scp the artifact, etc)

Pavel Georgiev-3
So can i see these stats now or something needs to be changed (it's not very clear from your email:) ).

Thanks.

p.s.
Do i need to submit a Feature Request?

On Tue, May 20, 2008 at 8:06 AM, Pavel Georgiev <[hidden email]> wrote:
Inline.

On Tue, May 20, 2008 at 6:51 AM, Michael Wiles <[hidden email]> wrote:
I find that every hudson job that is executed consists of 3 steps...

1. update from SCM
2. Run ant/maven
3. Do Post processing, i.e. pull build artifacts, publish test reports etc

Hudson clearly documents how long 2 takes, and when there are 2 steps, each step's time is logged.
 
[Pavel] I have a job with 3 build steps and all i see is the total time. Where can i see thew info for each steps?


Would however be nice to know how long 1st and 3rd steps took. For instance, when transferring large files from windows to linux (windows slave) it is _very_ slow, though it is unknown exactly how long it takes. And if you have a really big source tree if you knew how long the scm update/checkout was taking you might take steps to optimise that area.
 
[Pavel] Seems that i forgot about the SCM update. This is also very important.


On Mon, May 19, 2008 at 9:03 PM, Kohsuke Kawaguchi <[hidden email]> wrote:
Pavel Georgiev wrote:
As a starters the "build steps" (Build Section). Actually these are the most
important ones. I was also thinking about "Deploy WAR", and maybe "Publish
artefacts to SCP repository" but these do not seem that important.

Ah, OK, so it's only at Hudson level.

I briefly thought maybe you wanted to go deep inside Ant or something.

Hudson should be able to keep track of the drill down and show the time.


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]



--
see my blog:
http://analysis102.blogspot.com
http://audiblethoughts.blogspot.com
http://outsideofficehours.blogspot.com