X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail.marwe.net (mail.marwe.net [109.234.104.132]) by lists.alpinelinux.org (Postfix) with ESMTP id 1022E5C4C9B for ; Wed, 12 Jul 2017 09:35:30 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail.marwe.net (Postfix) with ESMTP id 3D3B41A722D for ; Wed, 12 Jul 2017 11:35:54 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.marwe.net X-Spam-Flag: NO X-Spam-Score: -2.899 X-Spam-Level: X-Spam-Status: No, score=-2.899 required=6.31 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.marwe.net ([127.0.0.1]) by localhost (mail.marwe.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6Y6XPgLnsN04 for ; Wed, 12 Jul 2017 11:35:52 +0200 (CEST) Received: from balosar.starwarsfan.de (141-10-138-91.dyn.cable.fcom.ch [91.138.10.141]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.marwe.net (Postfix) with ESMTPSA id 79B3B1A7225 for ; Wed, 12 Jul 2017 11:35:52 +0200 (CEST) Received: from [0.0.0.0] (eisler.nettworks.org [139.20.200.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by balosar.starwarsfan.de (Postfix) with ESMTPSA id 162AC801FA for ; Wed, 12 Jul 2017 09:35:03 +0000 (GMT) Subject: Re: [alpine-devel] Change Travis in Alpine Continuous Integration To: alpine-devel@lists.alpinelinux.org References: <0MI52u-1dWkGz1LeI-003sj6@mail.gmx.com> From: Yves Schumann Message-ID: <4d2655c8-5599-6f19-36e9-faa32256a0f3@eisfair.org> Date: Wed, 12 Jul 2017 11:35:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 In-Reply-To: <0MI52u-1dWkGz1LeI-003sj6@mail.gmx.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi 7heo Am 12.07.2017 um 03:23 schrieb 7heo: > Jenkins is a terrible, bloated software, that is a gigantic pain to install and maintain, let alone use. >... Sorry to say that but this kind of answer let me always think if I need to laugh or beeing angry. I'm hearing such statements always from people who came from a pure Unix a/o Linux world, who see Java as the Armageddon of the IT and not even have an idea of the power and possibilities which a tool like Jenkins offers. So it sounds like the common answer, unfortunately. :-( Build automation or CI/CD in general is my daily business and I know the different available tools. If you say it's a "gigantic pain to install and maintain", then I'd like to know which part is the real pain. Where is there something difficult a/o expensive? And even the "bloated" argument, for me inappropriate. Why/how do you came to such conclusions? To let Jenkins run for some testing and play around, you simply need to type _one_ line! Even to install it as a service is a common task. You can customize Jenkins exactly for your needs, that's the power of a plugin system. You can scale it exactly to your requirements. I'm maintaining different Jenkins installations with hundreds and even thousands of jobs and there are all kinds of jobs with of course a majority of build jobs. So you can automate nearly everything with it or even let setup build jobs fully automated by Jenkins itself. Not to just talk without some facts: Beside my daily business Jenkins administration I'm maintaining the Jenkins instance of the OSS projects fli4l [1] and eisfair [2]. The distro eisfair-ng is based on Alpine Linux and the CI of eisfair-ng [3] is fully automated and builds our packages. If a new package was added, the corresponding Jenkins job will be generated automatically and some minutes after a Git push the new package is available on the pkg repo. "In the end, and to go back on topic" to use your words, you really suggest to use minimalistic solutions because of Alpine's goal to be a minimalistic distro? Interesting! I think most of the users do _not_ use minimalistic tools around Alpine as their base system. Why would someone do this? Why should I resign to some comfort if it is just available? How do you write Emails or Documents? How do you develop software? Even if I'm very happy that there are base tools like vi available as an anchor in case of whatever can happen, I'm happy to use comfortable tools around the Alpine base system. But anybody as he wishes. If it's ok for you to build using some kind of cron jobs, why not. ;-) Unfortunately the day is always too short with only 24 hours, so I cannot bring in more time for such tasks on Alpine itself. I even got problems to find enough time for fli4l and eisfair-ng so we also spot the issue with not enough man power. So I hope the Alpine'ians find a proper solution for their CI/CD. Kind regards, Yves (A sidenote: At the moment we struggle with our EOL hardware. This is the reason why there are a lot of jobs on [3] currently disabled or not at the latest version. As soon as this is solved the whole system will be setup to build for the latest Alpine release.) [1] https://www.fli4l.de/ [2] https://www.eisfair.org/ [3] https://ssl.nettworks.org/ci/ --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---