What problem would this solve?
Hi,
I do have projects (repositories) where one is based on other's outputs, e.g. use one docker container to build a different one or include a library.
I.e. you have two respositories A and B, where B is based on A, and thus needs to be rebuilt after A has been built.
As far as I can see, this is currently not possible, or just through a dirty workaround, where and the end of A's build process it should trigger through API to rebuild B. Which is not logical, because if B depends on A, B should know about A, but not the other way around.
What do you propose?
It should be possible to use dependencies on other repositories. i.e. if B depends on A, in B's action script it should be possible to add A as a dependency und trigger a rebuild for B whenever A's last successful build is newer then B's.
regards
What problem would this solve?
Hi,
I do have projects (repositories) where one is based on other's outputs, e.g. use one docker container to build a different one or include a library.
I.e. you have two respositories A and B, where B is based on A, and thus needs to be rebuilt after A has been built.
As far as I can see, this is currently not possible, or just through a dirty workaround, where and the end of A's build process it should trigger through API to rebuild B. Which is not logical, because if B depends on A, B should know about A, but not the other way around.
What do you propose?
It should be possible to use dependencies on other repositories. i.e. if B depends on A, in B's action script it should be possible to add A as a dependency und trigger a rebuild for B whenever A's last successful build is newer then B's.
regards