Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Build activity "Accepting changes" never ends

Sometimes the build activity "Accepting changes" never ends.

Once we abandon the build request, the associate build engine becomes not available but in fact the jbe process is still running.
Any advice? We cannot find any evidence on server and/or jbe log files.
Thanks in advance. Cheers.

0 votes



2 answers

Permanent link

 If a build activity doesn't change it means that it was never closed by a build process.  Everything is driven by build events, so an activity is started by the JBE when it does the integrated SCM fetch, but if that process terminated unexpectedly (engine terminated, server shutdown, etc) then there is never an event to close the activity.  I suppose it could also be an exception in the build script as well.  Anything that would terminate the build early and ungracefully.  Generally it should pass back through the close build activity logic, but if its runtime exception or something like that then it could skip it.


I'm assuming we are talking about the build result getting abandoned, that marks the build state as terminated so nothing else will update that build result after that moment.  By JBE process does that mean the build loop (waiting for build request), or is it actually doing build work (running the build)?

~Spencer

0 votes


Permanent link
If a build activity doesn't change it means that it was never closed by a build process.  Everything is driven by build events, so an activity is started by the JBE when it does the integrated SCM fetch, but if that process terminated unexpectedly (engine terminated, server shutdown, etc) then there is never an event to close the activity.

OK, sounds right. Problem is we see:

  • JBE process running
    • build result running
      • build activity "Accepting changes" running
but activity never goes ahead/ends.
Logfiles from:
  • JBE process
  • build result
  • CCM server
seem not logging anything usefull.

I suppose it could also be an exception in the build script as well.
Not the case, scripts are always the same since 5+ years. Only thing we changed recently is the JBE version from v5.0.2 to v6.0.2.

 
By JBE process does that mean the build loop (waiting for build request), or is it actually doing build work (running the build)?
Yes, JBE process started and is running the build; On the Activities tab of build result we see:
  • Jazz Source Control setup <never completed>
    • Accepting changes <never completed>
Any advice on how to find what's the issue?
Thanks in advance.
Cheers.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 76

Question asked: Nov 12 '19, 8:56 a.m.

Question was seen: 1,466 times

Last updated: Nov 21 '19, 4:30 a.m.

Confirmation Cancel Confirm