Task #1028
closedBibisecting documentation
0%
Description
- Clean the docs (https://wiki.documentfoundation.org/Bibisect and https://wiki.documentfoundation.org/QA/HowToBibisect/Linux) dramatically --> Simplify, simplify, simplify.
- Separate Windows, Linux, OSX in different pages
- Consistency - provide consistent clean instructions for each platform
- Identify who controls what
- compile a list of repositories for bibisect packages
- name responsible parties
- state if the process is automated or manually triggered
=> That sould also answer whether we still need Bibisect 5.0 Linux bibisect builds from the Sun Ultra 24
Related issues
Updated by Florian Effenberger over 9 years ago
What's the status here? I recall this has been dealt with, but you should adjust the due date accordingly then
Updated by Florian Effenberger over 9 years ago
Florian poked Joel and Björn for details
Updated by Florian Effenberger over 9 years ago
For reference, Cloph's IRC posting:
<@cloph> we have "static" bibisect repos http://dev-downloads.libreoffice.org/bibisect/linux/ - those are highly detailed - and we have continuously updated repos in /srv/git/* on dev-downloads... [17:08:38] <@cloph> debugutil (linux), windows and mac are updated by tinderboxes - so there are updated builds, although not necessarily matching the build environment of the "static" ones.
Updated by Florian Effenberger over 9 years ago
- Subject changed from RECURRING: Create next set of bibisect commits and add to repo to get status quo on bibisecting status
Let's talk again about this during the next team call
We have the machine hosted, but it can be used for other tasks as well, if bibisecting is not needed.
What's required is:
- comple a list of repositories for bibisect packages
- Linux - Björn?
- Windows - hard to find? -> make more prominent
- OS X- Norbert before?
- name responsible parties (ideally not just one)
- identify which machines this is built and hosted on
- state if the process is automated or manually triggered [IMHO manually]
Goal is to have
- Windows, Linux, OSX all updated on a regular basis (at least once every other month) and the package uploaded somewhere useful and the wiki to reflect the range of every package, packages should be limited to ~10 gigs or less
- ideally - git working so we can pull daily and have a 3.5 - current
In a nutshell: Each platform has a different range, largely undocumented, and largely (outside of Linux) unused. Getting consistency, transparency, and automation would largely help all of these.
Updated by Florian Effenberger over 9 years ago
- Subject changed from get status quo on bibisecting status to get status quo on bibisecting
Sample structure to fill in is available at https://wiki.documentfoundation.org/QA/HowToBibisect/Linux
Updated by Florian Effenberger over 9 years ago
- Related to Support #1280: Bibisect 5.0, bibisect docs updates, Sun Ultra 24 tasks added
Updated by Florian Effenberger about 9 years ago
Let me add what was in #1280 originally:
Please clarify:- Do we still need Bibisect 5.0 Linux bibisect builds from the Sun Ultra 24? (given that there is a "Linux dbgutil" bibisect repo at git://dev-downloads.libreoffice.org/lo-linux-dbgutil-daily.git -- or is that too big/otherwise cumbersome?)
- please check the docs at https://wiki.documentfoundation.org/Bibisect for possibly needed updates to documentation
- Is the Sun Ultra currently in use? If not, I might be interested in running some stats with them.
Updated by Florian Effenberger about 9 years ago
- Priority changed from Normal to Immediate
Updated by Robinson Tryon about 9 years ago
Florian Effenberger wrote:
Let me add what was in #1280 originally:
Please clarify:
- Do we still need Bibisect 5.0 Linux bibisect builds from the Sun Ultra 24? (given that there is a "Linux dbgutil" bibisect repo at git://dev-downloads.libreoffice.org/lo-linux-dbgutil-daily.git -- or is that too big/otherwise cumbersome?)
I've asked people about the bibisect repos this week, and the overall impression I get is that having a regular (i.e. non-dbguil) daily bibisect for Linux is indeed useful. While we do have very fine coverage of commits with the XX-max family of repositories, those aren't available as daily-updated resources. Norbert mentioned the possibility of having the Jenkins machines produce builds for bibisect repo, so I'm going to follow-up w/him on that and see what plans he has (and timetable) for making those available.
- please check the docs at https://wiki.documentfoundation.org/Bibisect for possibly needed updates to documentation
Current docs have been updated with the latest repositories. Norbert is currently working on a backlog of commits for Windows bibisect, but will provide a link to the correct repo and update the notes on the wiki page when the building is caught up.
- Is the Sun Ultra currently in use? If not, I might be interested in running some stats with them.
If we're happy with the existing set of bibisect repos (XXmax + dbgutil), and we can use the builds generated by Jenkins to feed into a vanilla daily repo for Linux, then I think that the Ultra machine can definitely be repurposed for stats, etc.
Updated by Florian Effenberger about 9 years ago
- Tracker changed from Bug to Task
Updated by Robinson Tryon about 9 years ago
Robinson Tryon wrote:
Florian Effenberger wrote:
I've asked people about the bibisect repos this week, and the overall impression I get is that having a regular (i.e. non-dbguil) daily bibisect for Linux is indeed useful.
...possibility of having the Jenkins machines produce builds for bibisect repo, so I'm going to follow-up w/[Norbert] on that...
Further conversation with QA Team, Norbert, etc.. clarified some points:
- QA members would like to have up-to-date bibisect repositories available for testing
- While the Jenkins buildbots can produce builds several times a day, Norbert's preference is to only make updates available every 2 weeks or so (which would simplify the git-gc step, etc..)
If we're happy with the existing set of bibisect repos (XXmax + dbgutil), and we can use the builds generated by Jenkins to feed into a vanilla daily repo for Linux, then I think that the Ultra machine can definitely be repurposed for stats, etc.
IMHO the remaining question is whether or not it's acceptable to wait (up to) 2 weeks to get the latest stack of builds from the bibisect repository. I think it's a fair interval, but I'll confirm with the rest of the team
Updated by Florian Effenberger about 9 years ago
- Subject changed from get status quo on bibisecting to document bibisecting
- Description updated (diff)
Updated by Florian Effenberger about 9 years ago
- Project changed from Infrastructure to Release Engineering
- Subject changed from document bibisecting to Bibisecting documentation
- Status changed from New to Feedback
- Target version set to Q3/2015
- Start date deleted (
2015-01-26) - Parent task deleted (
#917)
Robinson sent updated docs to Florian who will cross-check it and give feedback
Updated by Florian Effenberger about 9 years ago
- Status changed from Feedback to Closed