From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 8830166D9A for ; Mon, 11 Jan 2021 08:53:37 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7F61D154B6 for ; Mon, 11 Jan 2021 08:53:07 +0100 (CET) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 1F52B15499 for ; Mon, 11 Jan 2021 08:53:05 +0100 (CET) Received: by mail-ed1-x535.google.com with SMTP id b2so17796014edm.3 for ; Sun, 10 Jan 2021 23:53:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=odiso-com.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=kXuz2dmVMyd6hYQECX2aH1XbLGFccL/ZnYqLirZ5di4=; b=CO2SoY/QF2gZYPoQ49QZxlaVTJEjhYOaLGBPgj+vE24YTzNpK1+gLwwTgvEB0vmPkq GrJ5H0m3T0Zqi446UzHNgdX43ADeO61PMVTT+t/No3jkclBaqWSBpY63Pn9xlS+yGjcx ZkTimgFiU+el6UZAyY0grNOeL7gX5cYzdbQEOJPJtNzoQGNd5AOBqeYV+VW0Y0kcCwJ1 R7jGru54Bq0UfRWAx/6Wh+gTF9JZPYpPk0XS0vUAiGVbPqhYanOJQ6eDcf62/g2J0wpZ FY++t7ZiZi63gYg5ViMXQnGed+4vsKuJaceIiMT9UdF0vWc+goFTM7Cq41EaBCjA10ZT ZXpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=kXuz2dmVMyd6hYQECX2aH1XbLGFccL/ZnYqLirZ5di4=; b=MpT+sBoz/revn9rTNuEDU3a5Jgul2vUI+CX/XaBaZgJ5c+NLGlaLg2R86kdZZwx3Xy JWDoWyruRzwPrvtBCzJl4mSK/vAxzahwQTGyl76GYefmOamdplv3WW7Q8eAwrQkPjkTQ u51VGF5gZP13SSdXvusOsFb7Z0p+bORS8ycQXfwsoR3CRooKs0Q//UsF0BSajiQOzH5Y UrOls7QYegMTuyua6Fq/Gac1y7UUyamER9ebOwjir0KddW9yIvPO9bdOOgstEz5+TFC2 5Dqe8Ni7jqn8LeOzCzHoMcZ5cutd3l0DiTQMGuxkQF7Tm61nJLtKDsCT4M+IXkLrAmVR 61Ow== X-Gm-Message-State: AOAM533Fv/bHMNPV9KOaJZOp3yhAkNZUZt5N5fokjiMQ6TYYgdcpoGFc +oE1MzMuKL3fqUYnh7E+qWFwKvsEEWQVapldanc= X-Google-Smtp-Source: ABdhPJzgllHgZK0Q/tZ3yKRxSj13Tc6Zc0DxfVTdTIBqshGqaM7M6y86xwPADMTX9qBrgjt51HuDCQ== X-Received: by 2002:a50:ec18:: with SMTP id g24mr13059075edr.6.1610351578641; Sun, 10 Jan 2021 23:52:58 -0800 (PST) Received: from [192.168.178.50] ([79.132.253.97]) by smtp.gmail.com with ESMTPSA id q25sm7255063eds.85.2021.01.10.23.52.57 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 10 Jan 2021 23:52:58 -0800 (PST) Message-ID: <67545ec92401aa20f7842bbdfaefa80513b97b46.camel@odiso.com> From: aderumier@odiso.com To: Proxmox VE development discussion Date: Mon, 11 Jan 2021 08:52:57 +0100 In-Reply-To: <1ceff1ea-4a30-1412-695f-0ae908908aa0@gilouweb.com> References: <1ceff1ea-4a30-1412-695f-0ae908908aa0@gilouweb.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.227 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] PVE development environment X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2021 07:53:37 -0000 Hi! (Great to see a new French contributor ^_^ ) Personnaly, I'm coding directly on a remote proxmox dev server with vim through ssh I'm pulling packages from pvetest repository to try to get the almost last version without need to build them. I'm pulling the master branch of the package I want to edit, make the deb and if some dependencies need to be updated (because they are too old in pvetest), I'm rebuilding them. I just need time to time rebuild the depend or update them through pvetest repo, but not so much. Alexandre Le jeudi 07 janvier 2021 à 16:17 +0100, Gilles Pietri a écrit : > Hi, > > Sorry if this doesn't belong here, point me in the right direction if > there is one ;) > > I read extensively what's there, and that is very helpful: > https://pve.proxmox.com/wiki/Developer_Documentation > I also read the thread here: I read also > https://lists.proxmox.com/pipermail/pve-devel/2018-August/033448.html > but that deals more with the repos than the actual dev env. > > Now I wonder, this all assumes you work directly on the test setup, > patch and code from there, and I'm not a big fan of this, for many > reasons… > > I usually do write code on my own station, that can access various > test > setups that I can spawn, be it in virtualbox, test installs of > proxmox > or nested ones for actual qemu tests. My question is, how do you guys > do > it, if there are any consensual setups? > > I wondered about different possibilities, tested some: > - coding, versionning on a test environment: I don't like that: I > need > to maintain a test environment that includes the coding tools, and it > will break, again and again, and not be in a reliable state, should I > need to debug something. > - compiling locally, having the debian and proxmox tooling, but that > is > not a happy solution, as I don't run Debian 10 or proxmox on my > machine > - using a set of hooks in git, mirroring stuff to a test instance, > and > compiling the packages there, rebooting as needed, that is easy > enough, > but I need to factor the dev environment > - using a CI system to handle that on my branches/remotes, namely > gitlab-ci with a runner on a pvetest instance, assetting the .debs, > deploying them… that feels a bit overkill, but… well, I might like > that > more, but maybe we could have a lighter way there. > > So, if I'm dumb and there's an obvious choice, just tell me ;) > If not, I'd love to hear about how you guys do it, and if we could > make > suggestions for that! > > Cheers, > > Gilou > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel