automatic build triggering after main build

Hello *,

I have 2 build configurations (there are more before and after them but they are not important for this issue):

  • Test (including automatic client GUI tests)
  • TestCleanup (which cleans up client specific data causes by the GUI test)


It is my aim to trigger TestCleanup automatically right after Test runs (even if Test failed). Test is triggered by time schedule but can also be triggered by hand. I can not run the cleanup just before starting Test. I must run it right after it.

I could set TestCleanup to be dependent on Test and schedule TestCleanup to run instead of Test but this would be confusing for our developers who just want to run the tests (and trigger it by hand). Furthermore this would conflict other dependencies. Is there a way to trigger TestCleanup right after Test has run?

Thanks in advance for any suggestions on it.

Regards
Enrico

4 comments
Comment actions Permalink

Is making TestCleanup dependent of Test not sufficient?
Just add the Test configuration in the "Build Triggering"/"Dependencies", when the Test configuration is triggered either by hand or automatically the TestCleanup will be run.
The limitation is that Test has to be successful.
But why do you need a separate build for that, would not be sufficient to add cleanup step in the Test build?

0
Comment actions Permalink

Unfortunately I can not merge them into one build. The TestCleanup must run even if something failed in Test (Test starts some services and does some desktop interaction before tests run -  must be stopped/ cleaned up after it). I want to be notified if Test failes, which would not be possible if I continue on errors to do the cleanup in same build.

Your suggestion to make TestCleanup dependent of Test would work just fine if I would have the possibility to run Test even if TestCleanup failed (because Test performs some interactive client/ backend testing and failures from time to time are possible/ intended).

0
Comment actions Permalink

Hello Enrico,

  I'm afraid I cannot see the solution in the current TeamCity version, considering the requirements and limitations you set.

  For future TeamCity versions, the most relevant request, I think, Is Support multiple build runners per build configuration .

  Please vote/watch.

  Kind regards,
  KIR

0
Comment actions Permalink

Thank Regis, thanks Kirill for your fast response and thoughts.

Regards
Enrico

0

Please sign in to leave a comment.