{"action":"created","issue":{"url":"https://api.github.com/repos/NatronGitHub/Natron/issues/257","repository_url":"https://api.github.com/repos/NatronGitHub/Natron","labels_url":"https://api.github.com/repos/NatronGitHub/Natron/issues/257/labels{/name}","comments_url":"https://api.github.com/repos/NatronGitHub/Natron/issues/257/comments","events_url":"https://api.github.com/repos/NatronGitHub/Natron/issues/257/events","html_url":"https://github.com/NatronGitHub/Natron/issues/257","id":318246421,"number":257,"title":"GitLab mirror and CI integration","user":{"login":"mash-graz","id":13013641,"avatar_url":"https://avatars2.githubusercontent.com/u/13013641?v=4","gravatar_id":"","url":"https://api.github.com/users/mash-graz","html_url":"https://github.com/mash-graz","followers_url":"https://api.github.com/users/mash-graz/followers","following_url":"https://api.github.com/users/mash-graz/following{/other_user}","gists_url":"https://api.github.com/users/mash-graz/gists{/gist_id}","starred_url":"https://api.github.com/users/mash-graz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mash-graz/subscriptions","organizations_url":"https://api.github.com/users/mash-graz/orgs","repos_url":"https://api.github.com/users/mash-graz/repos","events_url":"https://api.github.com/users/mash-graz/events{/privacy}","received_events_url":"https://api.github.com/users/mash-graz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-04-27T01:15:09Z","updated_at":"2018-04-30T16:28:30Z","closed_at":null,"author_association":"NONE","body":"because of your call at the forum concerning the build system, i already started to mirror your actual NatronGitHub repository to GitLab.\r\n\r\nhttps://gitlab.com/natron\r\n\r\ni created this new Group resp. namespace to keep it isolated from my other activities and would really like to transfer the ownership or at least adminstrator rights with you to prevent any accusation of name piracy.\r\n\r\nbut i definitely prefere GitLabs CI capabilities and transparency over GitHub!\r\n\r\nin the meanwhile it's also possible to utillize only GitLabs CI system for projects hosted GitLab, but the repository mirroring feature and a more traditional use of GitLabs services looks more reasonable to me.\r\n\r\nnevertheless it's always a little bit tricky to work with mirrored repositories, because changes on the mirror have to be done solely in parallel branches or have to be merged at the upstream source. and this doesn't work very well together with automatic CI build process...\r\n\r\nbut as a starting point it's perhaps the most useful compromise.\r\n\r\ni also would really like hear your opinion about GitLab and its CI system in general -- the pro and cons of such an attempt from your point of view.\r\n\r\nuntil now i didn't use GitLab for any complex crossplatform builds, but i already utilized it for docker image creation (e.g. my recent [DaVinci Resolve container](https://gitlab.com/mash-graz/resolve)) and simple in-house debian package creation. but any other job, which can by realized in privileged  docker containers should be able within this infrastructure as well.\r\n\r\ndebian packages can be even hosted via [GitLab pages](https://about.gitlab.com/features/pages/) and a little bit of help from [aptly](https://www.aptly.info/) straight out of the CI system. (here is a little [example](https://gitlab.com/mash-graz/raspi3-firmware/blob/fixes_by_mash/.gitlab-ci.yml#L34), how this works and [looks](https://mash-graz.gitlab.io/raspi3-firmware/) like) \r\n\r\n[and btw. i would even suggest to use gitlab pages for natrons web page, although i already asked the mur.at preseidium in the meanwhile to support your project officially with virtual host etc. i'm quite sure, you'll get an letter about their final decision soon.]\r\n\r\nfor the debian/ubuntu/mint platform we can reuse the [already available package build adaptation written by christian mariallat]( https://cse.google.com/cse?cx=partner-pub-7392075759954682:3632489811&q=natron&oq=natron&gs_l=partner-generic.3...2364.3388.0.3716.0.0.0.0.0.0.0.0..0.0.gsnos%2Cn%3D13...0.1008j227968j6..1ac.1.25.partner-generic..0.0.0.#gsc.tab=0&gsc.q=natron&gsc.page=1). this makes it quite trival, to build packages of natron and its siblings for this platforms.\r\n\r\nbut i would really like to see an inclusion of the relevant debian subdirectory within the upstream repository. this would make it a lot easier to reproduce the build even by non CI experienced individuals.\r\n\r\nas you already know -- because i was very often asking always just the same question -- i could never find out, how the CI build process of the natron binaries was realized in the past? i always guessed, OBS could be involved, but i couldn't find a satisfaying answer until now.\r\n\r\nif you see any chance, to reuse the existing solution or at least parts of it, i would really appreciate it. it's quite frustrating to reinvent the wheel again.\r\n\r\nbut if we have to rewrite it from scratch, i think, i could manage at least the unix platforms.\r\ni just have to ask for a little bit of patience and unavoidable reminders, because i'm so busy with other jobs, that i can not spend to much spare time on this particular challenge.\r\n\r\ngood luck!\r\n\r\nbut i really like your project and will try my best.\r\n\r\n<bountysource-plugin>\r\n\r\n---\r\nWant to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/57645800-gitlab-mirror-and-ci-integration?utm_campaign=plugin&utm_content=tracker%2F83915136&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F83915136&utm_medium=issues&utm_source=github).\r\n</bountysource-plugin>"},"comment":{"url":"https://api.github.com/repos/NatronGitHub/Natron/issues/comments/385452436","html_url":"https://github.com/NatronGitHub/Natron/issues/257#issuecomment-385452436","issue_url":"https://api.github.com/repos/NatronGitHub/Natron/issues/257","id":385452436,"user":{"login":"devernay","id":3778071,"avatar_url":"https://avatars3.githubusercontent.com/u/3778071?v=4","gravatar_id":"","url":"https://api.github.com/users/devernay","html_url":"https://github.com/devernay","followers_url":"https://api.github.com/users/devernay/followers","following_url":"https://api.github.com/users/devernay/following{/other_user}","gists_url":"https://api.github.com/users/devernay/gists{/gist_id}","starred_url":"https://api.github.com/users/devernay/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/devernay/subscriptions","organizations_url":"https://api.github.com/users/devernay/orgs","repos_url":"https://api.github.com/users/devernay/repos","events_url":"https://api.github.com/users/devernay/events{/privacy}","received_events_url":"https://api.github.com/users/devernay/received_events","type":"User","site_admin":false},"created_at":"2018-04-30T16:28:30Z","updated_at":"2018-04-30T16:28:30Z","author_association":"OWNER","body":"@Cinerar thanks for the links. Now someone has to find time to set it up!\r\nThe main problem (that we also have with travis and appveyor) is that fully building Natron and plugins, followed by running the unit tests, takes a long time. Travis kills us at 49mn, so we can just compile Natron and the basic plugins. see https://travis-ci.org/NatronGitHub/Natron : the coverity_scan builds now almost always error.\r\nDo you know on any similar restriction on gitlab CI?"}}
{"actor":{"display_login":"devernay"}}