Looks like I need to explain a bit more about the workflow. First thing you need to know is that workflow has been changed in February-March in a way that every submission is now built in isolated OBS project. All those projects are on home:prerelease: namespace in OBS. Each of them represent one submission. Images are also built for those projects, so release engineer (and developer too, btw) can see if submission builds OK. For IVI we also have automatic testing of every submission. For example, this is how submission queue looks like for IVI RE now: $ repa list submit/tizen/20140801.113059 ready tlm submit/tizen/20140801.123902 ready tlm submit/tizen/20140801.134500 ready cynara submit/tizen/20140801.185919 ready smack submit/tizen/20140804.084221 ready weston submit/tizen/20140804.084452 ready ivi-sanity-suite submit/tizen/20140804.095639 ready efl submit/tizen/20140804.134115 ready tlm submit/tizen/20140804.160000 ready gstreamer-vaapi,qt-tizen,libva-intel-driver,libva submit/tizen/20140804.171804 ready nspr submit/tizen/20140804.174021 ready nss submit/tizen/20140805.025917 ready e2fsprogs submit/tizen/20140805.063507 ready e2fsprogs submit/tizen/20140805.152104 ready u-boot submit/tizen/20140806.111926 ready icecream submit/tizen/20140806.115507 ready mic submit/tizen/20140806.121720 ready kickstarter submit/tizen/20140806.125426 ready gumd submit/tizen/20140807.020216 ready u-boot submit/tizen/20140807.060945 ready connman submit/tizen/20140807.091345 ready cynara submit/tizen/20140807.133029 ready kickstarter,icecream,rpm,build,mic,zypper,python-pygments submit/tizen/20140808.084959 ready efl submit/tizen/20140808.122026 ready gumd submit/tizen/20140808.212249 ready csf-framework submit/tizen/20140808.212639 ready csf-framework submit/tizen/20140811.130226 unresolvable packages weston-common submit/tizen/20140811.130757 ready u-boot submit/tizen/20140811.133500 ready testkit-lite submit/tizen/20140811.133542 ready common-suite-launcher submit/tizen_ivi/20140811.130836 ready common-api-runtime
As you can see most of submission are in a good shape. ‘ready’ status means that submission doesn’t have regressions in package and image building. However, this is not enough to accept submission to IVI or another profile. Another criteria is that submission must be accepted and released in Tizen Common project first. So, as IVI RE I can accept only tizen_ivi submissions if they don’t introduce regressions. tizen submissions have to be tested and released by Tizen Common before I can accept them. BTW, I’ve accepted gmock submission submit/tizen_ivi/20140811.050019 today. Submitter should get an email about that. Here is the SR, btw: https://build.tizen.org/request/show/27536. However, SR is created only when submission is rejected or accepted by RE. You can see your package in the latest ivi snapshot here: https://download.tizen.org/snapshots/tizen/ivi/latest/ Regards, Ed From: Jacek Bukarewicz [mailto:[email protected]] Sent: Monday, August 11, 2014 4:43 PM To: Bartosh, Eduard Cc: [email protected] Subject: Re: [Dev] git tag -> OBS submit requests mapping Thanks for the answer and yes - I'd rather not get into details of the release process more than required :). I had a specific reason to ask this question actually. We noticed that platform/upstream/gmock package is not built for the IVI project despite gbs submit was run on 2014-07-16 (there was no gmock in the IVI build manifest [1] ). I couldn't find any information regarding this submit request for IVI in the tizen-submit list. I _believe_ that after running gbs submit we couldn't see gmock in the pending requests here either: https://build.tizen.org/package/requests?package=gmock&project=Tizen%3AIVI). Now I see that there is one revoked request for gmock which I must have missed before and this lead me to believe that IVI submit requests might require target option. From my point of view OBS submission workflow is very convenient. What confused me was lack of (or my unability to find) feedback regarding state of submit request on the tizen-submit list and/or on build.tizen.org website (is it submitted at all, accepted or declined). By the way - today there was another IVI submit request (now accepted) for gmock package and I'm pretty sure that this request wasn't visible when the "new or review" option was chosen on the build.tizen.org - such behaviour is definitely confusing to the submitter. [1] http://download.tizen.org/snapshots/tizen/ivi/tizen-ivi_20140808.1/builddata/manifest/tizen-ivi_20140808.1_atom.xml Best regards, Jacek On 08/11/2014 01:39 PM, Bartosh, Eduard wrote: Hi Jacek, You’re absolutely right. Git tags are mapped to target obs projects with git-obs-mapping. However, you as a developer should not care about that as far as I know. In most cases it should be enough to follow this guide: https://source.tizen.org/documentation/developer-guide/getting-started-guide/contributing-code-tizen#package-submission-and-review-on-the-build-system git-obs-mapping is configured by architects and release engineers to make developer’s life easy. You just need to use gbs submit. In most cases it should work. There is much more complexity in release process you might not want to know about, but I’d be happy to give you more details if you want to know them. Feel free to ask questions. Regards, Ed From: Dev [mailto:[email protected]] On Behalf Of Jacek Bukarewicz Sent: Monday, August 11, 2014 1:53 PM To: [email protected]<mailto:[email protected]> Subject: [Dev] git tag -> OBS submit requests mapping Hi, I'm a bit confused about how git tags like submit/tizen/<date> are mapped to OBS submissions. In the scm/git-obs-mapping.git package there is a file that seems to contain such mapping: https://review.tizen.org/git/?p=scm/git-obs-mapping.git;a=blob;f=git-obs-mapping.xml;h=2ed41f871766cbea659ab50e8929e6e19826e817;hb=HEAD This XML suggests that submit/tizen/<date> tags should trigger submissions to these projects: - Tizen:Mobile - Tizen:IVI - Tizen:Generic - Tizen:IVI:Panda - Tizen:Common Since I cannot find any official documentation regarding this mapping I'd like to ask for clarification if that's correct. We are mostly interested in Tizen:IVI and Tizen:Common projects. Is it enough to run gbs submit -m '<message>' to trigger OBS submit request to these or should target projects be explicitly specified (options -t tizen_ivi or -t tizen_common should be added to gbs submit)? Best regards, -- Jacek Bukarewicz Samsung R&D Institute Poland Samsung Electronics [email protected]<mailto:[email protected]> --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- Jacek Bukarewicz Samsung R&D Institute Poland Samsung Electronics [email protected]<mailto:[email protected]> --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
