6 comments
Comment actions Permalink

Hello derrick,

  Please provide more information:
  - what version of TeamCity you're using
  - what kind of build triggers do you have set up for the build configuration (all of the triggers)
  - what is indicated as a build triggering reason in "Triggered By" field on build results page

  Kind regards,  KIR

0
Comment actions Permalink

I am using version 4.0
I am using TFS
I only have a 6:00am scheduled trigger set
I was triggered by my daily build name "JURISDaily" scheduled for 06:00am

Thank you for your assistance.

0
Comment actions Permalink

Hello Derrick,

   Do I understand correctly that your build is triggered by a 6:00 scheduled trigger,
   but runs again and again after that? Or you have a build trigger dependency to another build configuration,
   which is triggered in 6:00?

  Whether all repeating builds have the same "Triggered by" value on the build overview page?

  I'd appreciate if you make screenshot about build trigger settings and overview of the triggered builds.

  Thanks,
  KIR

0
Comment actions Permalink

You understand correctly all my builds are triggered by a 6:00 scheduled trigger. No other dependencies exist. I attached all pertinent screenshots. Strange thing is the behavior didn't occur Sunday or Monday, because the 600am trigger didnt fire at all.. I haven't made any changes in the triggering, I only stopped the builds Saturday after 470+ builds. I investigating why this happened.



Attachment(s):
snapshots.zip
0
Comment actions Permalink

Ok figured one thing out, why there wasn't any builds done since Saturday. On the build trigger, I had the option set to not build if there wasn't any pending changes. (You'll see the checkbox is checked in the screen shots) There weren't any changes till after 0800 today. but, once it is triggered it continues to build, so even more perplexing. This has to be a sychronization with TFS then.

0
Comment actions Permalink

Hello Derrick,

  In fact, you've setup self-triggering dependency, which is definitely not what you need.
  To fix the problem, please remove trigger on the Dependencies tab (build5.jpg in your archive).

  Kind regards,
  KIR

0

Please sign in to leave a comment.