public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Clara Kowalsky <clara.kowalsky@siemens.com>,
	isar-users@googlegroups.com, Natalia Tasci <nt@ilbers.de>,
	Zhihang Wei <wzh@ilbers.de>
Subject: Re: Migrating from Jenkins to GitHub CI
Date: Fri, 11 Jul 2025 08:33:00 +0200	[thread overview]
Message-ID: <ffe1c6da-6cee-4bfc-82ac-80a588580ba6@siemens.com> (raw)
In-Reply-To: <f970099a-15e3-4909-a989-6f82dc95f2dc@siemens.com>

On 11.07.25 08:17, Clara Kowalsky wrote:
> 
> 
> On 10.07.25 12:52, Baurzhan Ismagulov wrote:
>> On 2025-07-03 13:38, 'Clara Kowalsky' via isar-users wrote:
>>> 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.
>>
>> Thanks Clara for the inquiry,
>>
>> we had evaluated the integration with GitHub actions some time ago and
>> had a
>> positive impression. We'll prioritize this topic. We might need to
>> discuss this
>> in more detail.
>>
>> For now, we have a publicly accessible GitLab instance at
>> https://gitlab.isar-build.org/ which runs nightly jobs.
>>
>> With kind regards,
>> Baurzhan
>>
> 
> Hi Baurzhan,
> 
> thank you for the update, sounds good.
> 
> Best regards,
> Clara

I think this link wasn't known publicly before. Drop it in the README?

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
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/ffe1c6da-6cee-4bfc-82ac-80a588580ba6%40siemens.com.

  reply	other threads:[~2025-07-11  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 11:38 'Clara Kowalsky' via isar-users
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 [this message]
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=ffe1c6da-6cee-4bfc-82ac-80a588580ba6@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=clara.kowalsky@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=nt@ilbers.de \
    --cc=wzh@ilbers.de \
    /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