•  
     
    story #7522 tuleap generates grokmirror manifest
Summary
site admin
tuleap generates grokmirror manifest
  • We control exactly which repositories are included in
  • We don't have to install grokmirror on the master server

Note:

  • Grokmirror can do a partial update (just for one repository) of the manifest but for this to work, the manifest file should already exists.
  • We cannot rely on this behaviour because if the manifest file disappear, all the repositories will be included in the manifest file
  • Tuleap generates a manifest file compatible with grokmirror format
  • The file contains only gladmin dir + selected mirror repositories
  • The file is updated when gladmin dir and selected repo are updated
Empty
Nouha Terzi (terzino), loic.lefort@st.com
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#7522
Manuel Vacelet (vaceletm)
2014-11-04 18:29
2014-10-13 11:27
7528

References

Follow-ups

User avatar
Nouha, Loïc,

As of Tuleap 7.6.99.27, tuleap server is able to generate a manifest by itself, can you test on your side ?

This manifest only contains the repositories selected for given mirror

  • CC list set to Nouha Terzi (terzino), loic.lefort@st.com
  • Category set to
User avatar

Hi Manuel,

We need more information about this story.

What happen if a repository is removed/added from/to a mirror? My guess is that the corresponding manifest file should be regenerated.

  • It seems that it is not done as of today. Do you confirm?
  • Should we handle this case in this story?

Best regards,
Nicolas