public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Clara Kowalsky' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan (T CED)" <jan.kiszka@siemens.com>
Subject: Migrating from Jenkins to GitHub CI
Date: Thu, 3 Jul 2025 13:38:48 +0200	[thread overview]
Message-ID: <4e68dc66-8adf-4d3b-b904-4623ef2c9a5b@siemens.com> (raw)

Hi,

would it be possible to migrate the CI pipeline from Jenkins to GitHub 
Actions?

I see multiple advantages in using GitHub directly:
- Pipeline results publicly visible
- No separate login / access approval required to access results
- Native integration with the GitHub repo

The existing Avocado tests could be seamlessly integrated into GitHub 
Actions.
I understand that the migration takes time, but I think it would be very 
beneficial for the project if the CI results could be visible from the 
outside. If possible, we could help with the migration.

Best regards,
Clara Kowalsky

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/4e68dc66-8adf-4d3b-b904-4623ef2c9a5b%40siemens.com.

             reply	other threads:[~2025-07-03 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 11:38 'Clara Kowalsky' via isar-users [this message]
2025-07-10 10:52 ` Baurzhan Ismagulov
2025-07-11  6:17   ` 'Clara Kowalsky' via isar-users
2025-07-11  6:33     ` 'Jan Kiszka' via isar-users
2025-07-14 10:59       ` 'MOESSBAUER, Felix' via isar-users

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4e68dc66-8adf-4d3b-b904-4623ef2c9a5b@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=clara.kowalsky@siemens.com \
    --cc=jan.kiszka@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox