[OSSTEST PATCH] production-config: Publish per-flight osstest git refs in separate tree

[OSSTEST PATCH] production-config: Publish per-flight osstest git refs in separate tree

[Ian Jackson]

Those refs need to be somewhere public so that the relevant git
objects are accessible.  I think they probably have to be in
refs/tags/ or refs/heads/ of some repo.

But it doesn't have to be the main one on xenbits.  Most people won't
want these refs.  Most git commits they are interested in (eg git
commits referred to in flight reports) will be available on the
osstest master branch.  And having these refs there makes git fetch
and git clone of the main repo slow.

Deployment note:

I have already created the destination repo.  Once this commit makes
it to master, I will manually transfer all the flight-* refs from the
main tree to osstest/osstest-massachusetts.git.

Reported-by: George Dunlap <George.Dunlap@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
 production-config | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/production-config b/production-config
index 8d94990..0e6a51e 100644
--- a/production-config
+++ b/production-config
@@ -62,8 +62,8 @@ GlobalLockDir /home/osstest/testing.git
 LogsPublish= "$c{Publish}/logs"
 ResultsPublish= "$c{Publish}/results"
 
-HarnessPublishGitUserHost xen@xenbits.xen.org
-HarnessPublishGitRepoDir git/osstest.git
+HarnessPublishGitUserHost osstest@xenbits.xen.org
+HarnessPublishGitRepoDir ext/osstest-massachusetts.git
 
 ReportTrailer= <<END
 Logs, config files, etc. are available at
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel