search

perryl / concourse-scripts

GNU General Public License v2.0
0 stars 0 forks source link

Artifacts #5

Open mwilliams-ct opened 8 years ago

mwilliams-ct commented 8 years ago

Consider a case where two stratum are built. Stratum2 build-depends on stratum1. In this instance, stratum2 needs a passed: keyword to depend on stratum1. However, this cannot be made part of the job explicitly, it must be part of a "get" command. Therefore, we need to pass artifacts from stratum1 to stratum2.

There is no reason for these artifacts to be any more than an empty file.. but it probably makes more sense to pass actual artifacts to the final system build.

mwilliams-ct commented 8 years ago

Note: I don't mean to imply that this is the best way to do things. I'm not sure right now, part of this issue will be investigating and figuring it out

perryl commented 8 years ago

This would be simple if resources could take strata; as it is we would need to create the stratum1 as a separate job, then parse in the same way as system strata, and ensure all strata are listed in the required build order.

mwilliams-ct commented 8 years ago

For a first pass, I'm using definitions (as in BR definitions) as a resource that every stratum requires. This does the job, though I'm not convinced it's the right approach

perryl commented 8 years ago

I think it will need to be the case anyway; definitions has to be cloned in order for YBD to attempt to build the stratum (for the same reason we need YBD as a resource itself) if I'm reading you right?