Pushing code to ISS GIT repo

[Tomy Rolo]

Following up on Wolfgagngs e-mail concerning the ISS GIT repository, I would suggest the following:

• Create GIT repository on the ISS repo for the last stable version of PyHST, the stable libUCA+libPCO libraries, and the stable branch of ufo-ore

Push to these repositories whenever something in our stable branch changes.

• not sure if we have a stable branch of the filters yet. If yes, proceed as above. If not, push once per week, as recommended in the description page for the usage of the ISS repository.

The description is here:

​http://ankawiki.ka.fzk.de/mediawiki/index.php/Git-Repository#Einsatz_von_GIT_im_ISS

We should configure our VCS to do these tasks automatically.

[Suren A. Chilingaryan]

We have a place for the stable branches within UFO repository. All UFO stuff should go here:
​http://ufo.kit.edu/ufo/browser/framework
And the stable PyHST is here:
​http://ufo.kit.edu/ufo/browser/pyhst

It is easier to support everything in one place. Allows to point cross-reference source, patches, and tickets. Wolfgang, should just setup scripts which will automatically get data from this places and push in his repository.

[Matthias Vogelgesang]

I haven't received Wolfgang's original mail, so bear with me.

Replying to csa:

We have a place for the stable branches within UFO repository. All UFO stuff should go here:
​http://ufo.kit.edu/ufo/browser/framework

This is actually not the best idea and also a reason why I setup the top-level ufo-core repository. A shared bzr repository is supposed to contain branches of the same ancestry to share history (and save some space).

Therefore, it doesn't make much (neither logical nor infrastructural) sense to keep pcitool, ufo-core and whatnot in the same shared repository. I will also continue with this practice for all major tools (libuca, libpco and ufo-filters).

It is easier to support everything in one place. Allows to point cross-reference source, patches, and tickets. Wolfgang, should just setup scripts which will automatically get data from this places and push in his repository.

The problem is to determine when to pull. Monitoring the stable branches with inotify and pushing seems to be more feasible IMHO.

[Suren A. Chilingaryan]

Replying to Vogelgesang:

I haven't received Wolfgang's original mail, so bear with me.

Hallo,
here the information about the central repository for software of the ISS. 
You should use this repository for saving your developed code.
http://ankawiki.ka.fzk.de/mediawiki/index.php/Git-Repository#Einsatz_von_GIT_im_ISS

This is actually not the best idea and also a reason why I setup the top-level ufo-core repository. A shared bzr repository is supposed to contain branches of the same ancestry to share history (and save some space).

Therefore, it doesn't make much (neither logical nor infrastructural) sense to keep pcitool, ufo-core and whatnot in the same shared repository. I will also continue with this practice for all major tools (libuca, libpco and ufo-filters).

I don't get the problem about the common ancestry, but anyway it is irrelevant here. The point is we have place for stable branches.

The problem is to determine when to pull. Monitoring the stable branches with inotify and pushing seems to be more feasible IMHO.

For pulling, I'd just write a cron script which will pull daily. Of course, if you are volunteering to write synchronization scripts based on inotify triggers, you are very welcome.

[Matthias Vogelgesang]

Replying to csa:

Replying to Vogelgesang:

I haven't received Wolfgang's original mail, so bear with me.

Hallo,
here the information about the central repository for software of the ISS. 
You should use this repository for saving your developed code.
http://ankawiki.ka.fzk.de/mediawiki/index.php/Git-Repository#Einsatz_von_GIT_im_ISS

Erm, okay. I guess we all agree that this here is the place to be :-)

Therefore, it doesn't make much (neither logical nor infrastructural) sense to keep pcitool, ufo-core and whatnot in the same shared repository. I will also continue with this practice for all major tools (libuca, libpco and ufo-filters).

I don't get the problem about the common ancestry, but anyway it is irrelevant here.

There simply is no common ancestry.

For pulling, I'd just write a cron script which will pull daily. Of course, if you are volunteering to write synchronization scripts based on inotify triggers, you are very welcome.

Go for the cron-job ;-)

[Matthias Vogelgesang]

We had a quick discussion and it would be really helpful if this integrated sooner than later. Big advantage is that Volker can setup Jenkins CI at ISS and test against the Tango server.

I also re-assigned it to you Suren, because you said you'd do it.

[Suren A. Chilingaryan]

I have said how I would do it if I have to do it ;) For Jenkins, I propose just to use UFO repository. It should be accessible from ISS and IPE without passwords (r/o). If not, just send me an IP of Tango server.

[Suren A. Chilingaryan]

1. iss-repo.ka.fzk.de is not accessible from ufo.kit.edu
2. I don't have access to iss-repo.ka.fzk.de