[sprotty-dev] Unsuccessful PR status due to Jenkins build

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[sprotty-dev] Unsuccessful PR status due to Jenkins build

From: Kai Salmen <kai.salmen@xxxxxxxxxx>
Date: Fri, 19 Jan 2024 10:09:47 +0100
Delivered-to: sprotty-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/sprotty-dev/>
List-help: <mailto:sprotty-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/sprotty-dev>, <mailto:sprotty-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/sprotty-dev>, <mailto:sprotty-dev-request@eclipse.org?subject=unsubscribe>

Hi Sprotty devs,

with every commit to a PR branch a build is triggered on Jenkins server (https://ci.eclipse.org/sprotty/) and it is currently failing. As a result a required PR check is failing.

I have two questions:

- Is this integration still needed as we have the GitHub Action ensuring build, lint and test are successful and can we therefore remove it from the PR checks?

- Is the Jenkins and the build job still needed these days or could it be fully deactivated? I don't know the overall history and its current purpose, so this suggestion may seem bold or naive. :-)

Thank you and cheers,

Kai

Kai Salmen

Senior Software Engineer & Consultant

TypeFox GmbH

Am Germaniahafen 1, 24143 Kiel

https://typefox.io

Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385

Geschäftsführer: Daniel Dietrich, Dr. Miro Spönemann

Follow-Ups:
- Re: [sprotty-dev] Unsuccessful PR status due to Jenkins build
  - From: Miro Spönemann

Prev by Date: [sprotty-dev] Sprotty v1.1.0 is released
Next by Date: Re: [sprotty-dev] Unsuccessful PR status due to Jenkins build
Previous by thread: [sprotty-dev] Sprotty v1.1.0 is released
Next by thread: Re: [sprotty-dev] Unsuccessful PR status due to Jenkins build
Index(es):
- Date
- Thread

Breadcrumbs