You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2024. It is now read-only.
I'm working on the configuration of the runbot for OCA project, and this requires setting up the dependencies of the various projects, a process which is quite tedious, and also related to the writing of .travis.yml where such dependencies need to be manually coded.
I was thinking of a metadata file at the project level describing the inter-repository dependencies which could be used to help in the process. In the simplest form, it would be a plain text file, with 1 repository per line giving the names of the repository on which the current project depends. The scripts launched by travis could be updated so that in case the file is present, they would checkout the listed repository with the ${VERSION} branch. And having this information available would allow for an easier configuration of the runbot (at the moment, I'm grepping for git clone lines in .travis.yml...)
If people agree with this idea, I'll propose an implementation.
The text was updated successfully, but these errors were encountered:
+1 for the idea.
But remember that some projects require other dependencies, sometimes python (pip install), sometimes deb packages (apt-get install). It would be nice to also cover those.
I'm working on the configuration of the runbot for OCA project, and this requires setting up the dependencies of the various projects, a process which is quite tedious, and also related to the writing of
.travis.yml
where such dependencies need to be manually coded.I was thinking of a metadata file at the project level describing the inter-repository dependencies which could be used to help in the process. In the simplest form, it would be a plain text file, with 1 repository per line giving the names of the repository on which the current project depends. The scripts launched by travis could be updated so that in case the file is present, they would checkout the listed repository with the
${VERSION}
branch. And having this information available would allow for an easier configuration of the runbot (at the moment, I'm grepping forgit clone
lines in.travis.yml
...)If people agree with this idea, I'll propose an implementation.
The text was updated successfully, but these errors were encountered: