Einstein Toolkit Documentation:Git Super Repository - Revision history

Hinder at 03:31, 24 June 2011

2011-06-24T03:31:39Z

Hinder at 03:24, 24 June 2011

2011-06-24T03:24:56Z

Hinder at 03:20, 24 June 2011

2011-06-24T03:20:46Z

New page

The current method for checking out and updating components of the Einstein Toolkit has several shortcomings. We propose an additional layer of management around a Cactus tree achieved by storing it in a Git repository. This provides a uniform version control interface to the code with all the version control information from the source repositories available. It also allows the entire Cactus tree to be treated as a single repository, and allows "versions" of the code to be identified by a single Git revision.

This project is still in the early stages. We (Barry Wardell and Ian Hinder) are developing a set of techniques and tools which enable what we consider to be better workflows for using Cactus. As we use these ourselves, we will learn about what works and what doesn't, and hopefully will be able to provide recommended workflows for end-users.

==Documents==

* [[GitSuperRepoRationale|Rationale]]
* [[GitSuperRepoUsersGuide|User's guide]]
* [[GitSuperRepoServerGuide|Server administrator's guide]]

==Progress==

* We have set up a repository which implements most of what is described in the [[GitSuperRepoRationale|Rationale]].

* Repository is updated from the source repositories every hour

==Planned work==

* Integrate with build-and-test system so that there is always a branch which passes build-and-test

* Implement a technique for storing version control information (revision plus differences) into simulation output

* Interacting with the repository could be made easier by a couple of small user-friendly scripts

←Older revision		Revision as of 03:31, 24 June 2011
Line 1:		Line 1:
−	The current method for checking out and updating components of the Einstein Toolkit has several shortcomings. We propose an additional layer of management around a Cactus tree achieved by storing it in a Git repository. This provides a uniform version control interface to the code with all the version control information from the source repositories available. It also allows the entire Cactus tree to be treated as a single repository, and allows "versions" of the code to be identified by a single Git revision.

−	This project is still in the early stages. We (Barry Wardell and Ian Hinder) are developing a set of techniques and tools which enable what we consider to be better workflows for using Cactus. As we use these ourselves, we will learn about what works and what doesn't, and hopefully will be able to provide recommended workflows for end-users.
−
−	~~==Documents==~~
−
−	* [[/Rationale]]
−	* [[/User's guide]]
−	* [[/Server administrator's guide]]
−
−	~~==Progress==~~
−
−	* We have set up a repository which implements most of what is described in the [[GitSuperRepoRationale\|Rationale]].
−
−	* Repository is updated from the source repositories every hour
−
−	~~==Planned work==~~
−
−	* Integrate with build-and-test system so that there is always a branch which passes build-and-test
−
−	* Implement a technique for storing version control information (revision plus differences) into simulation output
−
−	* Interacting with the repository could be made easier by a couple of small user-friendly scripts

@@ Line 5: / Line 5: @@
 ==Documents==
-* [[GitSuperRepoRationale|Rationale]]
+* [[/Rationale]]
-* [[GitSuperRepoUsersGuide|User's guide]]
+* [[/User's guide]]
-* [[GitSuperRepoServerGuide|Server administrator's guide]]
+* [[/Server administrator's guide]]
 ==Progress==