Making changes on a dependent build visible

Here's my problem, we are currently using TC Enterprise 4.1combined with Perforce 2008.

I've three build configurations:
(1) - "Product" compilation to artifacts (use a VCS repository root A)
(2) - "QA environment" compilation to artifacts (use a specific VCS repository root B)
(3) - "'QA tests" run with artifacts from (1) and (2) and is mainly dependent of (1)

I would like to make the detected change list from (1) part of the changes of (3), is there any way to do this?
The best solution would be to have a clear change list enlighting the build number for (1) and (2) with their own changes.
I've tried to make (3) scanning (1) and (2) VCS repository without checking out the whole set of files, but it doesn't help...

4 comments
Comment actions Permalink

I've tried to make (3) scanning (1) and (2) VCS repository without checking out the whole set of files, but it doesn't help...


   I believe this should help. So if you attach VCS roots to the configuration (3) with option "Do not checkout files" you still should be able to see the changes in the VCS roots.
  And, I'd suggest to set snapshot dependency from (3) to (1), (2).

   Would such configuration work for you?

  Kind regards,
  KIR

0
Comment actions Permalink

The problem here is that checking the "Do not checkout files" option is global and apply to all roots...
Actually the ANT build file for "QA Test" is the one used to run the tests.
I'm going to check if we can use the snapshot dependency to get the scripts from the "QA compilation".

0
Comment actions Permalink

I come back on this subject, since we have done some tests and some progress on our side.
The snapshot dependency system is not suitable for our requirement, the artifact dependency is really the solution.

(1) -> artifact set 1 (last pinned)
(2) -> artifact set 2 (last successful)
(3) depends on artifact set 1 and artifact set 2 and directly runs against some scripts of (1) and (2)

And that's enough, no need to have any SCM dependencies.

We have the links to the two dependencies in the result of the build in the corresponding tab, which is interesting but difficult to access easily.

What we would like to have in the change log of 3 would be the merged change log of last pinned change log 1 and last successful change log 2.
Any idea?

0
Comment actions Permalink

Is there any plan to allow this?
Do we have to create a feature request?

0

Please sign in to leave a comment.