We want to have our own TDF-provided Bibisect repositories.
The scope of this ticket is to regularly produce Bibisect repositories for
- Mac OS X
with all the flavors and branches we need. These should be produced by TDF staff, on officially TDF-hosted machines. The platform should be maintained by infra, while the Bibisect repositories should be managed by assignee.
How to setup a new repository ( using lode )
- ./setup --help
- ./setup --new bibisect/coreXX
- mv /dev/bibisect/coreXX to bibisect/
- copy autogen.input from previous builds to the current one
- copy old .bibisect/loXX to .bibisect/loYY
- edit the new loYY
- go to jenkins - new item - copy existing item ( lo_bibisect_XX_Y_Y )
How to setup a new repository in gerrit
- Write project name ( use these as reference --> https://gerrit.libreoffice.org/#/admin/projects/?filter=bibisect )
- Change rights to 'Inherit from Dev-ACL-Template'
- ssh firstname.lastname@example.org
p 22 cd /srv/repositories/<new repository name>
- copy config file from another existing repository
- Edit the config file
- touch git-daemon-export-ok
- git remote update ( While the origin repo is not being built )
Use this script < https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/bibisect/buildReleasesRepository.sh > for building bibisect-linux-64-releases
Updated by Florian Effenberger over 5 years ago
- Assignee changed from Robinson Tryon to Christian Lohmaier
- Target version deleted (
Moving to Cloph's pile, but un-milestoned yet - let's revisit next year if we still need this and who carries it out; so no action required from your side for the moment, Cloph
Updated by Florian Effenberger about 5 years ago
- Assignee deleted (
Removing that from Cloph's pile, as its part of this tender: https://blog.documentfoundation.org/blog/2016/01/30/tender-for-a-quality-assurance-engineer-201601-01/
Updated by Xisco Fauli Tarazona almost 4 years ago
- Assignee set to Xisco Fauli Tarazona
I'm already taking care of creating the bibisect repositories. it's done using jenkins. Assigning it to myself
Updated by Xisco Fauli Tarazona over 3 years ago
- File downloadRelease.sh added
On the other hand, the 'releases' repository  is created using the script attached.
Usage: bash downloadRelease.sh <folder's name from https://downloadarchive.documentfoundation.org/libreoffice/old/>
Updated by Guilhem Moulin over 1 year ago
With the upcoming gerrit upgrade/refactoring I'd like to take the opportunity to consolidate that too. Details were agreed upon with Xisco Fauli Tarazona on IRC:
- Bibisect repos are no longer advertised at https://gerrit.libreoffice.org/#/admin/projects (nor served by the gerrit service). Using gerrit for the
bibisect-*projects are overkill because 1/ no change set are ever submitted; 2/ they clutter the project list; 3/ the ACLs are trivial (read access is enabled for everyone, push are forbidden for everyone).
- Having all bibisect repos in a self-contained drive makes it easier to move elsewhere (for instance on the box currently hosting https://dev-downloads.libreoffice.org).
- Furthermore I'm not at all comfortable about opening remote shell access to service users like
The bibisect repos are now available for anonymous `git fetch` from https://bibisect.libreoffice.org/$PLATFORM-$VERSION.git . For backward compatibility one can still fetch the active bibisect repositories (6.3 to 6.5) from the old insecure URLs git://gerrit.libreoffice.org/bibisect-$PLATFORM-$VERSION.git , however git:// support will not be added to >6.5 repositories, and will be entirely deprecated once 6.5 bibisect repositories are no longer active. Xisco updated the Wiki page to reflect these changes.
The new workflow involves a dedicated user and hostname:
$ git init --bare --quiet ~bibisect/repositories/linux-64-6.5.git $ git -C ~bibisect/repositories/linux-64-6.5.git remote add -f \ --mirror=fetch origin ssh://username@hostname/path/to/repo.git Updating origin […]
(No need to create the magic file
git-daemon-export-ok anymore. Repositories under
~bibisect/repositories are all public, and all exposed to git-http-backend(1), which runs as an unprivileged dynamic user. Don't put any private world-readable repositories in there!)
- Update (while the remote is not being built)
$ git -C ~bibisect/repositories/linux-64-6.5.git remote update Fetching origin […]
(This is for a fetch-based workflow, like was done up to now. For a push-based workflow one would instead need to push to ssh://email@example.com/~/repositories/linux-64-6.5.git from the original repository.)
Updated by Guilhem Moulin over 1 year ago
Or better, creation + fetch in a single command:
$ git clone --bare --mirror --template ~bibisect/templates \ ssh://username@hostname/path/to/repo.git \ ~bibisect/repositories/linux-64-6.5.git Cloning into bare repository… […]
Either way, please use
--template= as above (I forgot it in msg#17) in your creation recipe. There is not much in the template right now, but should the need to tune configuration options arise, the use
--template= will allow us to do it in a future-proof fashion.
Is there a wiki page where I could write these commands Xisco Fauli Tarazona? Or should I edit this Redmine ticket instead?
Updated by Beluga Beluga over 1 year ago
Guilhem: I suggest replacing the contents of this wiki page with what is the current reality: https://wiki.documentfoundation.org/QA/Bibisect/Implementation
(For some reason that page was translated to Danish, but I don't think we should be translating these sorts of docs)
Updated by Guilhem Moulin 9 months ago
Beluga Beluga wrote:
I suggest replacing the contents of this wiki page with what is the current reality: https://wiki.documentfoundation.org/QA/Bibisect/Implementation
Thanks, done. It subsumes part of the workflow in this ticket (repository creation and update).