[opensuse-buildservice] access to log information from a linked project
Hello, when working on a slave OBS connecting on a master OBS via the public API (in my case Meego.com), the default model is to create an empty project which is a simple links to the public API. When you do so all log information for the packages which are accessed via the link project to the public API are lost. Carsten (see mail bellow sent on a MeeGo tool mailing list) shows that the issue does not come from the API but rather from the way the link is managed in OBS. Is there a way to go around that problem the log info for a package via a link project to a public API or should I file a bug ? Thanks. -- Dominig ar Foll MeeGo TV Open Source Technology Centre Intel SSG Hi, Just noted a small misconception (that I had myself too): "Public API do NOT provide log info and in that case revision info will be empty" Actually, it does, it's just that OBS can't figure out how to do it over the link itself,a try this: curl http://api.meego.com/public/source/Trunk/acl/_history BR Carsten Munk -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 18. August 2011, 15:24:56 schrieb Dominig ar Foll:
Hello,
when working on a slave OBS connecting on a master OBS via the public API (in my case Meego.com), the default model is to create an empty project which is a simple links to the public API.
When you do so all log information for the packages which are accessed via the link project to the public API are lost.
Carsten (see mail bellow sent on a MeeGo tool mailing list) shows that the issue does not come from the API but rather from the way the link is managed in OBS.
Is there a way to go around that problem the log info for a package via a link project to a public API or should I file a bug ?
What is the "log info" for you exactly ? It is true that only some data is exposed via the public api, but it should be enough to run valid builds. The revision numbers come via source server (CI_CNT or vrev in the _history api call) and the build count should not matter here, because you do anyway a build in another project/repo. So, I don't get the point what exactly you miss here. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
What is the "log info" for you exactly ? the information that you obtain when you type the command : osc log PRJ PKG It is true that only some data is exposed via the public api, but it should be enough to run valid builds. The information is actually exposed via the API as found by Carlsen. Running the small command bellow demonstrate it :
curl http://api.meego.com/public/source/Trunk/acl/_history
The revision numbers come via source server (CI_CNT or vrev in the _history api call) and the build count should not matter here, because you do anyway a build in another project/repo.
So, I don't get the point what exactly you miss here. I am not interested by the revision number but by the MD5. The MD5 remains the same from one OBS instance to an other one what allows to create Tag (e.g. via obstag) which can be used to copy (e.g. via obs2obscopy) the exact version of the desired packages from one OBS instance to an other one. it become also easy to only copy the packages which have changed when replicating project from one OBS to an other.
Unfortunately as the log info is not presented from linked OBS, the concept of Tag cannot be used if the user does not have a login on the source OBS. As the information is available on the public API, it's a shame not to be able to use it simply via a link. -- Dominig -- Dominig ar Foll MeeGo TV Open Source Technology Centre Intel SSG -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 18. August 2011, 16:51:17 schrieb Dominig ar Foll:
What is the "log info" for you exactly ?
the information that you obtain when you type the command : osc log PRJ PKG
It is true that only some data is exposed via the public api, but it should be enough to run valid builds.
The information is actually exposed via the API as found by Carlsen. Running the small command bellow demonstrate it :
curl http://api.meego.com/public/source/Trunk/acl/_history
The revision numbers come via source server (CI_CNT or vrev in the _history api call) and the build count should not matter here, because you do anyway a build in another project/repo.
So, I don't get the point what exactly you miss here.
I am not interested by the revision number but by the MD5. The MD5 remains the same from one OBS instance to an other one what allows to create Tag (e.g. via obstag) which can be used to copy (e.g. via obs2obscopy) the exact version of the desired packages from one OBS instance to an other one.
I don't know obs2obscopy, but I can assure that linking via specified MD5 or revision numbers is working cross build service wide. (just branched a package via specified MD5 as revision from a remote OBS 2.3 to a local OBS 2.3).
it become also easy to only copy the packages which have changed when replicating project from one OBS to an other.
Why not using project or package links ?
Unfortunately as the log info is not presented from linked OBS, the concept of Tag cannot be used if the user does not have a login on the source OBS.
ah, you manually check via an external tool .... okay, when you just want to current MD5, you can use /source/$REMOTE_PROJECT/$package When you add ?rev=$REVISION you get also the various MD5 sums for it.
As the information is available on the public API, it's a shame not to be able to use it simply via a link.
I can assure, links are just working at least with current code base. We have also at least one test casefor that in our current test suite. bye adrian
-- Dominig -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag, 19. August 2011, 08:55:49 schrieb Adrian Schröter:
Am Donnerstag, 18. August 2011, 16:51:17 schrieb Dominig ar Foll:
What is the "log info" for you exactly ?
the information that you obtain when you type the command : osc log PRJ PKG
It is true that only some data is exposed via the public api, but it should be enough to run valid builds.
The information is actually exposed via the API as found by Carlsen. Running the small command bellow demonstrate it :
Btw /public is declared as not official part of the API. It is just and exclusively for inter-OBS link. It should not be used by any tool. We will most likely map /public to / at some point of time and make it configurable whan can be accessed without login to some degree. ...
okay, when you just want to current MD5, you can use
/source/$REMOTE_PROJECT/$package
When you add ?rev=$REVISION you get also the various MD5 sums for it.
works currently also with /public atm.
As the information is available on the public API, it's a shame not to be able to use it simply via a link.
I can assure, links are just working at least with current code base. We have also at least one test casefor that in our current test suite.
bye adrian
-- Dominig
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian, I have joined your two previous mails for clarity.
I don't know obs2obscopy obstag and obscopy are two small utilities that I have create to mirror project between OBS instances. For more see : http://wiki.meego.com/Obstag Why not using project or package links ? My use case of private OBS instance is aiming at people who need to provide very long term support of their software (typical >10 to 25 years). As you would easily guess, assuming that longevity with a link on a public OBS instance is not acceptable. Btw /public is declared as not official part of the API. It is just and exclusively for inter-OBS link. It should not be used by any tool. I do not use /public directly in any tool but I have link created on my private OBS instance pointing on the public API of MeeGo.com (called meego.com) as you can create from the web UI with the button "setup OBS"
When I do on my private OBS : osc log myhome:myMeeGoCopy zypper I get the log info for mypackage (with the much needed MD5). ---------------------------------------------------------------------------- r18 | peter | 2011-04-20 11:57:49 | 8c74e45c667be611098b61f7c8403d2e | 1.5.3 | sr16587 Review ok ---------------------------------------------------------------------------- r17 | rolla | 2011-01-05 03:51:02 | 1169c733e75159352a42e4ac0f28f45b | 1.5.2 | sr11462 ...... (log cut here) If indirectly try to get the log info of a package via the link by doing : osc log meego.com:MeeGo:1.2:oss zypper I will get no log info at all. Just the package name. I do not understand why.
I can assure, links are just working at least with current code base. We have also at least one test casefor that in our current test suite. Can then explain me why osc log command reports differently when accessed via a linked project than directly? and hoz I can overturn the limitation ?
Thanks -- Dominig ar Foll MeeGo TV Open Source Technology Centre Intel SSG -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter -
Dominig ar Foll