Setting Progress and Percentage in Jazz Build
I'm tuning up my build processes adding <startBuildActivity>
tasks to my ant. Those are straighforward enough but I'm noticing
that when the fetch is done, the percentage shows 99% even though my
PDE build and JUnit take about 1m45s of the total 2 minute build.
Is there a way to assign % to various build activities? How does Jazz
determine what my estimated build time is?
tasks to my ant. Those are straighforward enough but I'm noticing
that when the fetch is done, the percentage shows 99% even though my
PDE build and JUnit take about 1m45s of the total 2 minute build.
Is there a way to assign % to various build activities? How does Jazz
determine what my estimated build time is?
2 answers
You cannot assign a percentage.
Jazz build is tracking two different averages in the build definition
history: number of activites, and build duration. These are used to display
a percent complete, and estimated completion time. These are independent
guesses about how much work, or how much time, is left in a build.
If the number of activities or duration change significantly (you add or
remove function in your build), it can take several builds before the
guesses "look right" for your build definition.
The progress percentage is based on the number of historical activities in
the build. So, if you have completed 9 of 10 activities, then you will get
90% progress, even if the last activity takes the majority of time.
This is why we have the two numbers: the percent complete, and the estimated
completion time.
If you want to know approximately when the build will be done, look at the
estimated completion time. If you want to know what steps have been
completed, look at progress percentage.
We have some enhancements that we would like to consider after 1.0 is
released. First, if you have multiple build machines with different speeds,
the estimated completion can be misleading. Second, we would like to provide
a way to "reset" the averages, so you don't need to wait for several builds
before accuracy improves.
---
Ryan Manwiller
Jazz Team Build
Jazz build is tracking two different averages in the build definition
history: number of activites, and build duration. These are used to display
a percent complete, and estimated completion time. These are independent
guesses about how much work, or how much time, is left in a build.
If the number of activities or duration change significantly (you add or
remove function in your build), it can take several builds before the
guesses "look right" for your build definition.
The progress percentage is based on the number of historical activities in
the build. So, if you have completed 9 of 10 activities, then you will get
90% progress, even if the last activity takes the majority of time.
This is why we have the two numbers: the percent complete, and the estimated
completion time.
If you want to know approximately when the build will be done, look at the
estimated completion time. If you want to know what steps have been
completed, look at progress percentage.
We have some enhancements that we would like to consider after 1.0 is
released. First, if you have multiple build machines with different speeds,
the estimated completion can be misleading. Second, we would like to provide
a way to "reset" the averages, so you don't need to wait for several builds
before accuracy improves.
---
Ryan Manwiller
Jazz Team Build
Note: I also submitted a workitem a while back to allow the build to
state explicitly what per-cent done it is (i.e. "I'm 45% done"). It's
workitem 43757.
Cheers,
Geoff
Ryan Manwiller wrote:
state explicitly what per-cent done it is (i.e. "I'm 45% done"). It's
workitem 43757.
Cheers,
Geoff
Ryan Manwiller wrote:
You cannot assign a percentage.
Jazz build is tracking two different averages in the build definition
history: number of activites, and build duration. These are used to
display a percent complete, and estimated completion time. These are
independent guesses about how much work, or how much time, is left in a
build.
If the number of activities or duration change significantly (you add or
remove function in your build), it can take several builds before the
guesses "look right" for your build definition.
The progress percentage is based on the number of historical activities
in the build. So, if you have completed 9 of 10 activities, then you
will get 90% progress, even if the last activity takes the majority of
time.
This is why we have the two numbers: the percent complete, and the
estimated completion time.
If you want to know approximately when the build will be done, look at
the estimated completion time. If you want to know what steps have been
completed, look at progress percentage.
We have some enhancements that we would like to consider after 1.0 is
released. First, if you have multiple build machines with different
speeds, the estimated completion can be misleading. Second, we would
like to provide a way to "reset" the averages, so you don't need to wait
for several builds before accuracy improves.
---
Ryan Manwiller
Jazz Team Build