Bug 2684 - Need additional information on configuring and using the PR server
Summary: Need additional information on configuring and using the PR server
Status: RESOLVED FIXED
Alias: None
Product: Reference
Classification: Documentation
Component: handbook (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4
Assignee: Scott Rifenbark
QA Contact:
URL: http://git.yoctoproject.org/cgit/cgit...
Whiteboard: 11 Feb 2013: Resolved
Depends on:
Blocks:
 
Reported: 2012-07-03 16:58 UTC by Mark Hatle
Modified: 2013-02-11 18:03 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hatle 2012-07-03 16:58:28 UTC
Additional information on setting up, managing and using the PR server is needed for both OE-Core and the Yocto Project.

The document should cover:

* Theory on why a PR service is better then the old way of doing things
* basic PR service configuration
* setting up a shared PR server
* migrating the PR server data from one build directory to another
  - Enable group development
  - Enable removing build and clean building while preserving PR values
Comment 1 Scott Rifenbark 2012-07-03 17:08:56 UTC
Mark, 

We probably need to schedule a meeting to discuss this bug.  I will need plenty of background information on this as right now the bucket is empty :)  I will schedule something for a phone meeting.

Scott
Comment 2 Paul Eggleton 2012-10-02 13:54:29 UTC
There's a little bit of background here:

https://wiki.yoctoproject.org/wiki/Network_based_PR_service
http://comments.gmane.org/gmane.linux.embedded.poky/5596

Obviously we'll need to give you more concise information for the documentation, but this is at least a start.
Comment 3 Richard Purdie 2012-12-05 14:20:03 UTC
We now have https://wiki.yoctoproject.org/wiki/PR_Service
Comment 4 Scott Rifenbark 2013-02-08 12:55:31 UTC
I have looked this over and can implement some fixes based on the wiki link that Richard provided in Comment 3.  Namely, an overview of the PR Service, how to run it for a single and muliple build systems, caveates such as sstate, and command specifics.  

However, Mark's initial bug as stated suggests we should provide several things.  I don't really have information telling me why the PR Service is better other than the obvious that it would eliminate error-prone manual bumping scheme.  I don't have information on how to set up a PR Server if it goes beyond what is shared in the wiki on how to configure the host and port.  And, I don't have information on migrating PR server data.

Another question.... We currently describe the PR bump system in http://www.yoctoproject.org/docs/1.4/dev-manual/dev-manual.html#usingpoky-changes-prbump.  Should we leave this as is and add the PR Service information?  Or, integrate the two methods but clearly suggest the PR Service as the superior method.

Thanks, 
Scott
Comment 5 Scott Rifenbark 2013-02-08 21:25:36 UTC
I have updated the4 section called "Incrementing a Package Revision Number" in the dev-manual.  You can see it at http://www.yoctoproject.org/docs/1.4/dev-manual/dev-manual.html#incrementing-a-package-revision-number.  

This is a first stab at trying to cover the PR Service stuff and the options for incrementing things in YP.  I have addressed only what I could get out of the wiki whose link is in Comment 3.  I do not have the information to address everything Mark said the documentation should cover.  Someone will need to provide me with that extra information.

Also, I left the section on how to manually "bump" the package revision as is. I don't have the information that would cover any new schemes the user needs to understand.  I also need that provided to me.

Please look over what I have. 

Thanks, 
Scott
Comment 6 Scott Rifenbark 2013-02-11 18:03:56 UTC
Applied final review comments from Richard Purdie.  The result can be seen at http://www.yoctoproject.org/docs/1.4/dev-manual/dev-manual.html#incrementing-a-package-revision-number.