1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.JAVA

  • No CI/CD settings in packages of Debian Java team?

    From Andreas Tille@21:1/5 to All on Fri Apr 16 10:40:01 2021
    Hi,

    in Debian Med we are activating Salsa-CI by adding debian/salsa-ci.yml
    to all packages and set this in

    -> Settings -> CI/CD

    This entry can be found in the menu between Repository and Operations.
    I intended to do this setting for packages (for instance cronometer and
    cdk). However, the whole menu entry is missing. I have no idea why but
    it seems Salsa-CI needs a team wide configuration and it would be great
    if some team admin would enable this setting for individual packages.

    Kind regards

    Andreas.

    --
    http://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sudip Mukherjee@21:1/5 to andreas@an3as.eu on Fri Apr 16 11:50:02 2021
    Hi Andreas,

    On Fri, Apr 16, 2021 at 9:34 AM Andreas Tille <andreas@an3as.eu> wrote:

    Hi,

    in Debian Med we are activating Salsa-CI by adding debian/salsa-ci.yml
    to all packages and set this in

    -> Settings -> CI/CD

    This entry can be found in the menu between Repository and Operations.
    I intended to do this setting for packages (for instance cronometer and
    cdk). However, the whole menu entry is missing. I have no idea why but
    it seems Salsa-CI needs a team wide configuration and it would be great
    if some team admin would enable this setting for individual packages.

    repos in java-team have pipelines disabled by default, You can enable it from: Settings -> General -> Visibility, project features, permissions and
    enable 'Pipelines' from there.

    I have done cronometer for you.


    --
    Regards
    Sudip

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Morrell@21:1/5 to Sudip Mukherjee on Fri Apr 16 12:50:01 2021
    On Fri, Apr 16, 2021 at 10:48:51AM +0100, Sudip Mukherjee wrote:
    On Fri, Apr 16, 2021 at 9:34 AM Andreas Tille <andreas@an3as.eu> wrote:
    in Debian Med we are activating Salsa-CI by adding debian/salsa-ci.yml
    to all packages and set this in

    -> Settings -> CI/CD

    repos in java-team have pipelines disabled by default, You can enable it from:
    Settings -> General -> Visibility, project features, permissions and
    enable 'Pipelines' from there.

    Additionally, just because it appears to be less well known: You only
    need a d/salsa-ci.yml file if you're customising the CI *per-branch*.
    You can even set the Variables like RELEASE=experimental from that
    config page.

    the recommended way is to use "recipes/debian.yml@salsa-ci-team/pipeline" as config path

    https://salsa.debian.org/salsa-ci-team/pipeline#basic-use

    -----BEGIN PGP SIGNATURE-----

    iHUEABYKAB0WIQSBP39/Unco6Ai78+TbymUJHySObAUCYHlqMgAKCRDbymUJHySO bEEKAP9/eKORknqikShxyXYgfJxokDt+5ctfF/Nc9hxvvK+cbwEAw/6zZn3U4Aj0 IK0l9EUl5vYdbn9/xcmm+ND8ZHop7gQ=
    =8xuH
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to Sudip Mukherjee on Fri Apr 16 15:20:01 2021
    Hi Sudip,

    On Fri, Apr 16, 2021 at 10:48:51AM +0100, Sudip Mukherjee wrote:
    This entry can be found in the menu between Repository and Operations.
    I intended to do this setting for packages (for instance cronometer and cdk). However, the whole menu entry is missing. I have no idea why but
    it seems Salsa-CI needs a team wide configuration and it would be great
    if some team admin would enable this setting for individual packages.

    repos in java-team have pipelines disabled by default.

    Is there any good reason for this setting?

    You can enable it from:
    Settings -> General -> Visibility, project features, permissions and
    enable 'Pipelines' from there.

    I have done cronometer for you.

    Thanks a lot for the hint and taking over the change.

    Kind regards

    Andreas.

    --
    http://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Emmanuel Bourg@21:1/5 to All on Fri Apr 16 21:50:02 2021
    Le 16/04/2021 à 15:13, Andreas Tille a écrit :

    repos in java-team have pipelines disabled by default.

    Is there any good reason for this setting?

    When Salsa was set up we were instructed no to overuse the CI system, I
    don't know how this has evolved now.

    Personally I think this isn't very useful, it's more a waste of
    resources since I've already built the packages locally before pushing
    the changes to Salsa. In an era of digital sobriety I prefer to keep it
    turned off. And it's also a source of spam on the IRC channel.

    Emmanuel Bourg

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to Emmanuel Bourg on Sat Apr 17 07:30:02 2021
    Hi Emmanuel,

    On Fri, Apr 16, 2021 at 09:41:11PM +0200, Emmanuel Bourg wrote:
    Is there any good reason for this setting?

    When Salsa was set up we were instructed no to overuse the CI system, I
    don't know how this has evolved now.

    As far as I know this has settled now.

    Personally I think this isn't very useful, it's more a waste of
    resources since I've already built the packages locally before pushing
    the changes to Salsa. In an era of digital sobriety I prefer to keep it turned off.

    Fair enough. I admit I do not run all tests done by Salsa-CI (for
    instance I do not run piuparts and reproducibility test) and I also
    learned that when running autopkgtest in my pbuilder chroot the results
    can be different from debci and salsa-ci (since the pbuilder hook I'm
    using is running as root which is wrong but does its job in the waste
    majority of cases). So I learned that salsa-ci is helpful for my
    workflow.

    Kind regards
    Andreas.

    --
    http://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)