Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am assuming that your Setup Kit build has the following configuration:</p> <ul> <li>A 'Finish Build Trigger' set to the CI Build, so that every time the CI Build is successfully completed, the Setup Kit build will run.</li> <li>A VCS Root so that every time Setup Kit is run, it gets its own source from VCS.</li> </ul> <p>The problem is that if CI Build takes two minutes, and there are more CI changes during that build, the Setup Kit build will use the source of when it started, rather than the source from the triggering CI Build. It's not the VCS Changes that are triggering the build, but the CI project, so it has nothing to do with there being VCS changes or not.</p> <p><strong>Snapshot Dependencies</strong><br> What you are missing is a <a href="http://confluence.jetbrains.com/display/TCD8/Snapshot+Dependencies" rel="nofollow">Snapshot Dependency</a>. This is available through the 'Dependencies' configuration steps (#6). This will still do a project trigger, but will cause the CI Build and the Setup Kit build to use the same exact source code from the same timestamp. You will still get two Setup Kit builds, but each one will be directly correlated to a CI Build.</p> <p><strong>Quiet Periods</strong><br> Because every successful CI Build will trigger a Setup Kit build, another option would be to reduce the number of CI Builds. By enabling a <a href="http://confluence.jetbrains.com/display/TCD8/Configuring+VCS+Triggers#ConfiguringVCSTriggers-quietPeriod" rel="nofollow">quiet period</a> on the CI Build, CI will only kick off when there are changes and there has not been any new commit in X time. "Something changed. Let's wait 30 seconds to see if there are more changes coming. If there is nothing new then, we will trigger a build." This would put the two commits on a single CI Build which would result in a single Setup Kit Build.</p> <p>Similarly, you can remove the Finish Build trigger on Setup Kit, and change it to a VCS Trigger with a quiet period; set the quiet period to slightly more than the time it takes the CI project to run. This will still allow you to have a CI Build for every commit, but will group together the Setup Kit builds when there are many quick commits. The downside is that it will no longer correlate to a successful CI Build. So, after 2 minutes (whatever your quiet period is) with no new changes, Setup Kit will fire, even if the CI Build is in a failed state.</p>
    singulars
    1. This table or related slice is empty.
    1. POTeamCity "Finish Build" trigger fires when no changes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJay Harris
    1. USJay Harris
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTeamCity "Finish Build" trigger fires when no changes
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAh, ok thanks Jay, that makes sense. Is there no way it can be set to not trigger a setup kit build if there are no changes since the last setup kit build? I'm just trying to cut down on un-needed builds.
      singulars
      1. PO
      1. USFetchez la vache
    2. CONo. Setup Kit is being triggered by CI Build Success. There is no consideration for VCS State. Whereas CI is 'Check for changes then start build', Setup is 'Start build then check for changes.'. The build is already underway before VCS is checked for changes, and TeamCity has no way to un-start a build.
      singulars
      1. PO
      1. USJay Harris
    3. COI've added a Quiet Period description as some further alternatives. It's not ideal, either, but may be a better alternative.
      singulars
      1. PO
      1. USJay Harris
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload