Re: Request to join the team
And by the way, my salsa login is: smarquis Thanks --- Original Message --- Le lundi 19 septembre 2022 à 21:09, Stanislas Marquis a écrit : > Hello, > > I hereby request to join the Python Team. > > I will maintain the python3-swisseph package. See my ITP > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958755 . Also will take > care of some other packages I care about. > > I have read the group policy > (https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst) > and I accept it. > > Thanks! > -- > Stanislas Marquis astrori...@protonmail.com > > 2E86 C286 B932 AB40 5DFB C09A 1C28 E6C2 6007 C39C
Request to join the team
Hello, I hereby request to join the Python Team. I will maintain the python3-swisseph package. See my ITP https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958755 . Also will take care of some other packages I care about. I have read the group policy (https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst) and I accept it. Thanks! -- Stanislas Marquis 2E86 C286 B932 AB40 5DFB C09A 1C28 E6C2 6007 C39C
Re: Enabling salsa-ci on all Debian Python Team repos
> I was wondering if it would make sense to enable CI/CD on Salsa for all > projects owned by the Debian Python Team, or if there's any concern > about scaling issues in terms of pipeline workers (or anything else > really). what would the team get out of doing this? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: Enabling salsa-ci on all Debian Python Team repos
On 2022-09-19 06 h 51, Emanuele Rocca wrote: Hello debian-salsa-ci and debian-python! I was wondering if it would make sense to enable CI/CD on Salsa for all projects owned by the Debian Python Team, or if there's any concern about scaling issues in terms of pipeline workers (or anything else really). For the past few days I've been enabling CI/CD on Salsa for various packages owned by the DPT. I've been doing this on a case-by-case basis: if the package I wanted to work on (for reasons unrelated to CI) did not have CI/CD yet, I'd add [1] as the pipeline configuration file and carry on with my work. Perhaps there's an opportunity to automate and getting wider CI usage. Thanks, Emanuele [1] recipes/debian.yml@salsa-ci-team/pipeline Hi, I was told "please don't" 3 years ago and although I've pushed a number of times (in private and in public), I have had no replies: https://salsa.debian.org/salsa/support/-/issues/170 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: [Debian-salsa-ci] Enabling salsa-ci on all Debian Python Team repos
On Mon, Sep 19, 2022 at 01:52:09PM +0200, Iñaki Malerba wrote: > [...] > > Perhaps there's an opportunity to automate and getting wider CI usage. > > One of the biggest issues we had when a team adopted the pipeline was > DDOSing of the instance because of the multiple pipelines generated when > pusing the .gitlab-ci.yml file to all the projects. > > If you're planning to do this, please: > > - Use the API and configure the 'CI/CD configuration file' project > field, as you mentioned in the email. This won't generate a pipeline > when configured but only on the next push. Indeed; setting the configuration file to recipes/debian.yml@salsa-ci-team/pipeline will avoid any need to touch the actual repository. > - If you need create the .gitlab-ci.yml file, please use the > `ci.skip`[1] push option. And that should only be needed if the configuration is non-standard. > Thanks, and good luck :) Best wishes, Julian
Enabling salsa-ci on all Debian Python Team repos
Hello debian-salsa-ci and debian-python! I was wondering if it would make sense to enable CI/CD on Salsa for all projects owned by the Debian Python Team, or if there's any concern about scaling issues in terms of pipeline workers (or anything else really). For the past few days I've been enabling CI/CD on Salsa for various packages owned by the DPT. I've been doing this on a case-by-case basis: if the package I wanted to work on (for reasons unrelated to CI) did not have CI/CD yet, I'd add [1] as the pipeline configuration file and carry on with my work. Perhaps there's an opportunity to automate and getting wider CI usage. Thanks, Emanuele [1] recipes/debian.yml@salsa-ci-team/pipeline