Scheduling a Build in RTC
Hi,
I'm trying to schedule a build in RTC and my environment is like this:
1. I have a Jazz repository located in US server
2. I've created a build definition and mentioned in the Schedule time as my system time (IST timings) lets say to build at 16:15 PM everyday (So i want the build to happen at IST 16:15pm everyday).
3. And i have my Jazz build engine executed on a server which is located in US (EDT timings)
Now the build doesn't get triggered at this time... Could anyone help me where exactly i'm going wrong or if somethings missing?
I've also tried giving the time in EDT format also, but no luck.
Any help would be appreciated..
Thanks,
Vidhya
I'm trying to schedule a build in RTC and my environment is like this:
1. I have a Jazz repository located in US server
2. I've created a build definition and mentioned in the Schedule time as my system time (IST timings) lets say to build at 16:15 PM everyday (So i want the build to happen at IST 16:15pm everyday).
3. And i have my Jazz build engine executed on a server which is located in US (EDT timings)
Now the build doesn't get triggered at this time... Could anyone help me where exactly i'm going wrong or if somethings missing?
I've also tried giving the time in EDT format also, but no luck.
Any help would be appreciated..
Thanks,
Vidhya
10 answers
On 2010/09/07 3:53, vidhprak wrote:
When is the build being triggered? Or is the problem that it is not
being triggered at all, even if you leave things alone for an entire
day? Can you run the build if you request a build manually?
Do you have the "Build only if there are changes accepted" box checked?
Is the build running as scheduled, but the build is being skipped
because there are no new changes?
I'm trying to schedule a build in RTC and my environment is like
this:
1. I have a Jazz repository located in US server
2. I've created a build definition and mentioned in the Schedule time
as my system time (IST timings) lets say to build at 16:15 PM
everyday (So i want the build to happen at IST 16:15pm everyday).
3. And i have my Jazz build engine executed on a server which is
located in US (EDT timings)
Now the build doesn't get triggered at this time... Could anyone help
me where exactly i'm going wrong or if somethings missing?
I've also tried giving the time in EDT format also, but no luck.
When is the build being triggered? Or is the problem that it is not
being triggered at all, even if you leave things alone for an entire
day? Can you run the build if you request a build manually?
Do you have the "Build only if there are changes accepted" box checked?
Is the build running as scheduled, but the build is being skipped
because there are no new changes?
On 2010/09/07 3:53, vidhprak wrote:
I'm trying to schedule a build in RTC and my environment is like
this:
1. I have a Jazz repository located in US server
2. I've created a build definition and mentioned in the Schedule time
as my system time (IST timings) lets say to build at 16:15 PM
everyday (So i want the build to happen at IST 16:15pm everyday).
3. And i have my Jazz build engine executed on a server which is
located in US (EDT timings)
Now the build doesn't get triggered at this time... Could anyone help
me where exactly i'm going wrong or if somethings missing?
I've also tried giving the time in EDT format also, but no luck.
When is the build being triggered? Or is the problem that it is not
being triggered at all, even if you leave things alone for an entire
day? Can you run the build if you request a build manually?
Do you have the "Build only if there are changes accepted" box checked?
Is the build running as scheduled, but the build is being skipped
because there are no new changes?
Hi David,
The build should be triggered at 16:15PM , but it doesn't get triggered at all when its scheduled. But when its manually requested, it works perfectly fine. And also in the build definition the condition "Build only if there are changes accepted" is not selected.
Rgds,
Vidhya
On 2010/09/08 0:23, vidhprak wrote:
A couple more obvious things to double check. (I assume you have
already double checked these, but I have to ask.) Is the "Enabled" box
on the Schedule tab of the build definition checked? In the Build Days
section of the Schedule tab of the build definition, are the correct
days of the week selected?
Have you left the schedule active and untouched for a couple days to see
if the scheduled build is kicked off at some odd time?
If you still can't find the problem, then I have no idea. You will have
to open a defect against RTC, or hope that someone who knows more about
Jazz Build replies in this forum.
The build should be triggered at 16:15PM , but it doesn't get
triggered at all when its scheduled. But when its manually requested,
it works perfectly fine. And also in the build definition the
condition "Build only if there are changes accepted" is not
selected.
A couple more obvious things to double check. (I assume you have
already double checked these, but I have to ask.) Is the "Enabled" box
on the Schedule tab of the build definition checked? In the Build Days
section of the Schedule tab of the build definition, are the correct
days of the week selected?
Have you left the schedule active and untouched for a couple days to see
if the scheduled build is kicked off at some odd time?
If you still can't find the problem, then I have no idea. You will have
to open a defect against RTC, or hope that someone who knows more about
Jazz Build replies in this forum.
Dave asked whether your build runs at all during the day. It would be good to know.
Which version of RTC are you using? There was a defect in 2.x whereby the time zone adjustment would only adjust for hours, not minute offsets. IST has time offset of UTC+05:30, so it would act as if the offset was +5:00. This is fixed in 3.0.
Which version of RTC are you using? There was a defect in 2.x whereby the time zone adjustment would only adjust for hours, not minute offsets. IST has time offset of UTC+05:30, so it would act as if the offset was +5:00. This is fixed in 3.0.
I'm having a similar problem triggering scheduled builds. I am using RTC 2.0, and my builds work when triggered manually.
I have checked the 'enable schedule' checkbox, and i have configured it to check every 10 minutes.
I see in my jbe output that it says 'Found a schedule request for...', and then it goes into waiting mode, and doesn't actually do the build. So it seems that the scheduling is working, but it's not really doing the build. I made sure that there was some fresh changes in code so that it would/should detect a change.
I can run my build manually with no problem.
Question 1: what am I doing wrong?
Question 2: is scheduled build only supposed to run when it detects a change?
Question 3: is there a log file on the build agent that I can look at to get details of why scheduled build was seemingly abandoned?
I have checked the 'enable schedule' checkbox, and i have configured it to check every 10 minutes.
I see in my jbe output that it says 'Found a schedule request for...', and then it goes into waiting mode, and doesn't actually do the build. So it seems that the scheduling is working, but it's not really doing the build. I made sure that there was some fresh changes in code so that it would/should detect a change.
I can run my build manually with no problem.
Question 1: what am I doing wrong?
Question 2: is scheduled build only supposed to run when it detects a change?
Question 3: is there a log file on the build agent that I can look at to get details of why scheduled build was seemingly abandoned?
On 2011/01/27 15:08, haydenmarchant wrote:
That's exactly the behavior you would see if the build is configured to
run only if new changes are available and there are no new changes
available.
I'm not sure. Make sure that new changes really are available. Open
the build definition, go to the Jazz Source Control tab, and check the
Workspace field near the top. Is it the correct workspace? Is that
workspace used only for builds, or is someone using it for other
purposes? Open the repository workspace editor for the build's
workspace by clicking on the "Workspace:*" link. Check the flow targets
section at the bottom of the page. Is the workspace flowing with the
correct stream? Did you deliver some changes to that stream before
testing the build scheduling, without also putting those changes in the
build workspace?
That is configurable. Open the build definition, go to the Jazz Source
Control tab, and look for the check box "Build only if there are changes
accepted" near the bottom. From your description, I assume that that
box is checked.
Do you want scheduled builds to run only if there are new changes? Or
do you want scheduled builds to run every time.
Not that I know of.
--
David Olsen
IBM Rational
I'm having a similar problem triggering scheduled builds. I am using
RTC 2.0, and my builds work when triggered manually.
I have checked the 'enable schedule' checkbox, and i have configured
it to check every 10 minutes.
I see in my jbe output that it says 'Found a schedule request for...',
and then it goes into waiting mode, and doesn't actually do the build.
That's exactly the behavior you would see if the build is configured to
run only if new changes are available and there are no new changes
available.
So it seems that the scheduling is working, but it's not really doing
the build. I made sure that there was some fresh changes in code so
that it would/should detect a change.
I can run my build manually with no problem.
Question 1: what am I doing wrong?
I'm not sure. Make sure that new changes really are available. Open
the build definition, go to the Jazz Source Control tab, and check the
Workspace field near the top. Is it the correct workspace? Is that
workspace used only for builds, or is someone using it for other
purposes? Open the repository workspace editor for the build's
workspace by clicking on the "Workspace:*" link. Check the flow targets
section at the bottom of the page. Is the workspace flowing with the
correct stream? Did you deliver some changes to that stream before
testing the build scheduling, without also putting those changes in the
build workspace?
Question 2: is scheduled build only supposed to run when it detects a
change?
That is configurable. Open the build definition, go to the Jazz Source
Control tab, and look for the check box "Build only if there are changes
accepted" near the bottom. From your description, I assume that that
box is checked.
Do you want scheduled builds to run only if there are new changes? Or
do you want scheduled builds to run every time.
Question 3: is there a log file on the build agent that I can look at
to get details of why scheduled build was seemingly abandoned?
Not that I know of.
--
David Olsen
IBM Rational
David,
My problem was that I was using the main stream as source for build, and not a specific workspace. When I created a special workspace just for building, based on the stream, it found changes, and the scheduled builds ran as expected.
Buggy user, not buggy product!
Thanks for your help,
Hayden
That's exactly the behavior you would see if the build is configured to
run only if new changes are available and there are no new changes
available.
I'm not sure. Make sure that new changes really are available. Open
the build definition, go to the Jazz Source Control tab, and check the
Workspace field near the top. Is it the correct workspace? Is that
workspace used only for builds, or is someone using it for other
purposes? Open the repository workspace editor for the build's
workspace by clicking on the "Workspace:*" link. Check the flow targets
section at the bottom of the page. Is the workspace flowing with the
correct stream? Did you deliver some changes to that stream before
testing the build scheduling, without also putting those changes in the
build workspace?
That is configurable. Open the build definition, go to the Jazz Source
Control tab, and look for the check box "Build only if there are changes
accepted" near the bottom. From your description, I assume that that
box is checked.
Do you want scheduled builds to run only if there are new changes? Or
do you want scheduled builds to run every time.
Not that I know of.
--
David Olsen
IBM Rational
My problem was that I was using the main stream as source for build, and not a specific workspace. When I created a special workspace just for building, based on the stream, it found changes, and the scheduled builds ran as expected.
Buggy user, not buggy product!
Thanks for your help,
Hayden
On 2011/01/27 15:08, haydenmarchant wrote:
I'm having a similar problem triggering scheduled builds. I am using
RTC 2.0, and my builds work when triggered manually.
I have checked the 'enable schedule' checkbox, and i have configured
it to check every 10 minutes.
I see in my jbe output that it says 'Found a schedule request for...',
and then it goes into waiting mode, and doesn't actually do the build.
That's exactly the behavior you would see if the build is configured to
run only if new changes are available and there are no new changes
available.
So it seems that the scheduling is working, but it's not really doing
the build. I made sure that there was some fresh changes in code so
that it would/should detect a change.
I can run my build manually with no problem.
Question 1: what am I doing wrong?
I'm not sure. Make sure that new changes really are available. Open
the build definition, go to the Jazz Source Control tab, and check the
Workspace field near the top. Is it the correct workspace? Is that
workspace used only for builds, or is someone using it for other
purposes? Open the repository workspace editor for the build's
workspace by clicking on the "Workspace:*" link. Check the flow targets
section at the bottom of the page. Is the workspace flowing with the
correct stream? Did you deliver some changes to that stream before
testing the build scheduling, without also putting those changes in the
build workspace?
Question 2: is scheduled build only supposed to run when it detects a
change?
That is configurable. Open the build definition, go to the Jazz Source
Control tab, and look for the check box "Build only if there are changes
accepted" near the bottom. From your description, I assume that that
box is checked.
Do you want scheduled builds to run only if there are new changes? Or
do you want scheduled builds to run every time.
Question 3: is there a log file on the build agent that I can look at
to get details of why scheduled build was seemingly abandoned?
Not that I know of.
--
David Olsen
IBM Rational
In the next release, you should get a warning when you set up a build to
work directly from a stream ... although I personally would prefer to
just remove the ability to build directly from a stream ... sometimes it
is the fault of the person who left the noose hanging from the ceiling,
and not the people that walked into it by mistake and hung themselves (:-).
Cheers,
Geoff
On 2/6/2011 3:38 AM, haydenmarchant wrote:
work directly from a stream ... although I personally would prefer to
just remove the ability to build directly from a stream ... sometimes it
is the fault of the person who left the noose hanging from the ceiling,
and not the people that walked into it by mistake and hung themselves (:-).
Cheers,
Geoff
On 2/6/2011 3:38 AM, haydenmarchant wrote:
David,
My problem was that I was using the main stream as source for build,
and not a specific workspace. When I created a special workspace just
for building, based on the stream, it found changes, and the scheduled
builds ran as expected.
Buggy user, not buggy product!
Thanks for your help,
Hayden
David Olsenwrote:
On 2011/01/27 15:08, haydenmarchant wrote:
I'm having a similar problem triggering scheduled builds. I am
using
RTC 2.0, and my builds work when triggered manually.
I have checked the 'enable schedule' checkbox, and i have
configured
it to check every 10 minutes.
I see in my jbe output that it says 'Found a schedule request
for...',
and then it goes into waiting mode, and doesn't actually do the
build.
That's exactly the behavior you would see if the build is configured
to
run only if new changes are available and there are no new changes
available.
So it seems that the scheduling is working, but it's not really
doing
the build. I made sure that there was some fresh changes in code so
that it would/should detect a change.
I can run my build manually with no problem.
Question 1: what am I doing wrong?
I'm not sure. Make sure that new changes really are available. Open
the build definition, go to the Jazz Source Control tab, and check the
Workspace field near the top. Is it the correct workspace? Is that
workspace used only for builds, or is someone using it for other
purposes? Open the repository workspace editor for the build's
workspace by clicking on the "Workspace:*" link. Check the
flow targets
section at the bottom of the page. Is the workspace flowing with the
correct stream? Did you deliver some changes to that stream before
testing the build scheduling, without also putting those changes in
the
build workspace?
Question 2: is scheduled build only supposed to run when it detects
a
change?
That is configurable. Open the build definition, go to the Jazz
Source
Control tab, and look for the check box "Build only if there are
changes
accepted" near the bottom. From your description, I assume that
that
box is checked.
Do you want scheduled builds to run only if there are new changes? Or
do you want scheduled builds to run every time.
Question 3: is there a log file on the build agent that I can look
at
to get details of why scheduled build was seemingly abandoned?
Not that I know of.
--
David Olsen
IBM Rational
Geoffrey Clemm <geoffrey> writes:
Out of curiousity has the SCM team ever shared with you why building
directly from the stream was ever implemented? It sure has caused some
head scratching here until we figured out what was going on.
-Garrett Rolfs
In the next release, you should get a warning when you set up a build
to work directly from a stream ... although I personally would prefer
to just remove the ability to build directly from a stream
Out of curiousity has the SCM team ever shared with you why building
directly from the stream was ever implemented? It sure has caused some
head scratching here until we figured out what was going on.
-Garrett Rolfs