Help Desk issueshttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues2024-03-28T19:46:21Zhttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4481Add External Collaborators to Eclipse 4diac Github organisation2024-03-28T19:46:21ZAlois ZoitlAdd External Collaborators to Eclipse 4diac Github organisationGithub only allows members of the organization to be assigned for reviewing pull requests. We have a larger contributor base that are currently not committers. However these are not only supporting with PRs but also with code reviews and...Github only allows members of the organization to be assigned for reviewing pull requests. We have a larger contributor base that are currently not committers. However these are not only supporting with PRs but also with code reviews and tests. For that it would be great to beeing able to assing them as reviewers for PRs.
According to the Github documentation this is only possible if these people are added as External Collaborators with read access to the organization: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization
My question would be is something like this possible and if yes how can we do that so that you have no effort in it?https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4479Questions about moving a repo from Openj9 to Adoptium AQAvit2024-03-28T08:31:54ZLan XiaQuestions about moving a repo from Openj9 to Adoptium AQAvit## Summary
We are thinking of moving https://github.com/eclipse-openj9/openj9-systemtest repo from OpenJ9 to Adoptium AQAvit. Please see https://github.com/adoptium/aqa-tests/issues/5163 for details.
Is there an Eclipse process that we...## Summary
We are thinking of moving https://github.com/eclipse-openj9/openj9-systemtest repo from OpenJ9 to Adoptium AQAvit. Please see https://github.com/adoptium/aqa-tests/issues/5163 for details.
Is there an Eclipse process that we need to follow? Also, we are wondering what will the resulting license be. Currently, openj9-systemtest repo has EPL2 or AP2 (dual licensed). Adoptium repo has Apache 2.0. Is it correct to assume that openj9-systemtest repo material will be changed to Apache 2.0 once it is moved to Adoptium? Thanks
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Lowhttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4477Add dprod-bot as a member of the GitHub "eclipse-che" organization with read-...2024-03-28T20:25:04ZIlya BuziukAdd dprod-bot as a member of the GitHub "eclipse-che" organization with read-only access.## Summary
Hello, please add https://github.com/dprod-bot to the `eclipse-che` GitHub organization with read-only access
## Steps to reproduce
(How one can reproduce the issue - this is very important)
## What is the current bug beha...## Summary
Hello, please add https://github.com/dprod-bot to the `eclipse-che` GitHub organization with read-only access
## Steps to reproduce
(How one can reproduce the issue - this is very important)
## What is the current bug behavior?
(What actually happens)
## What is the expected correct behavior?
(What you should see instead)
## Relevant logs and/or screenshots
(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Low
## Impact
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example:
"We have a release tomorrow")https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4474[temurin-compliance] Add new users to the project2024-03-27T14:32:59ZStewart Addison[temurin-compliance] Add new users to the projectWe have a few users that have been onboarded by the Adoptium PMC for addition to the temurin-compliance project. PMC approval was done as part of [1] and they are now added and listed on the Temurin Compliance project page [2]. Please cr...We have a few users that have been onboarded by the Adoptium PMC for addition to the temurin-compliance project. PMC approval was done as part of [1] and they are now added and listed on the Temurin Compliance project page [2]. Please create their IDs on the temurin compliance system and on the machines in order to allow them to perform work in the project. They are all employed by Red Hat so are covered by the three-way agreement. Tony from the original list has already been onboarded [3] so is not in this list:
Name | github ID | Eclipse ID
---|---|---
Jiri Vanek | [judovana](https://github.com/judovana) | [judovana](https://accounts.eclipse.org/users/judovana)
Zdenek Zambersky | [zzambers](https://github.com/zzambers) | [zzambers](https://accounts.eclipse.org/users/zzambers)
Radek Čáp | [RadekCap](https://github.com/RadekCap) | [radek](https://accounts.eclipse.org/users/radek)
Petra Mikova | [pmikova](https://github.com/pmikova) | [pmikova](https://accounts.eclipse.org/users/pmikova)
Jiri Andrlik | [andrlos](https://github.com/andrlos) | [jandrlik](https://accounts.eclipse.org/users/jandrlik)
- [1] - https://www.eclipse.org/lists/adoptium-pmc/msg00274.html
- [2] - https://projects.eclipse.org/projects/adoptium.temurin-compliance/who
- [3] - https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4228
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Low
## Impact
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example:
"We have a release tomorrow")
Our next release will be in the second half of April so if we could get them onboarded before then we can get them up to speed to help with the release.Pawel StankiewiczPawel Stankiewiczhttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4471PR checks are not processed anymore2024-03-26T20:58:14ZDirk FauthPR checks are not processed anymore## Summary
When creating a PR for the NatTable project, only the eca check is performed. The PR build is triggered and can be seen in Jenkins, but the PR in GitHub does not reflect the build result.
This worked some weeks ago but sudden...## Summary
When creating a PR for the NatTable project, only the eca check is performed. The PR build is triggered and can be seen in Jenkins, but the PR in GitHub does not reflect the build result.
This worked some weeks ago but suddenly stopped.
## Steps to reproduce
Create a PR for NatTable or check https://github.com/eclipse-nattable/nattable/pull/72
## What is the current bug behavior?
No check for the build result.
## What is the expected correct behavior?
Additionally to the eca check, the build check should be performed and inspected.
## Relevant logs and/or screenshots
https://github.com/eclipse-nattable/nattable/pull/72
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Low
## Impact
Need to double check in Jenkins if the PR doesn't break anything.Frederic Gurrfrederic.gurr@eclipse-foundation.orgFrederic Gurrfrederic.gurr@eclipse-foundation.orghttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4469Change aidge's group icon2024-03-26T08:37:35ZOlivier BICHLERChange aidge's group icon## Summary
I would like to change aidge's group icon with the same as the one used for its aidge inner project!
## Priority
- [ ] Urgent
- [ ] High
- [ ] Medium
- [x] Low
## Severity
- [ ] Blocker
- [ ] Major
- [ ] Normal
- [x] Low## Summary
I would like to change aidge's group icon with the same as the one used for its aidge inner project!
## Priority
- [ ] Urgent
- [ ] High
- [ ] Medium
- [x] Low
## Severity
- [ ] Blocker
- [ ] Major
- [ ] Normal
- [x] Lowhttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4463Request archival of kuksa.val.feeders repository2024-03-28T03:52:06ZSebastian SchildtRequest archival of kuksa.val.feeders repositoryRelated #2221
We'd like to request the repository https://github.com/eclipse/kuksa.val.feeders to be archived.
We already added a note to the Readme explaining this, and this has been discussed on several KUKSA community calls. Apart f...Related #2221
We'd like to request the repository https://github.com/eclipse/kuksa.val.feeders to be archived.
We already added a note to the Readme explaining this, and this has been discussed on several KUKSA community calls. Apart form the calls there is also a public discussion here: https://github.com/eclipse/kuksa.val.feeders/pull/175Christopher HillsChristopher Hillshttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4461Eclipse Foundation should apply for Matrix Foundation membership2024-03-28T16:51:37ZMarkus KargEclipse Foundation should apply for Matrix Foundation membership## Summary
The Eclipse Foundation should become a member of the Matrix Foundation.
## Priority
- [ ] Urgent
- [x] High *Because the future of the Matrix protocol is at urgent risk due to running out of funds!*
- [ ] Medium
- [ ] Low
...## Summary
The Eclipse Foundation should become a member of the Matrix Foundation.
## Priority
- [ ] Urgent
- [x] High *Because the future of the Matrix protocol is at urgent risk due to running out of funds!*
- [ ] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [ ] Normal
- [x] Low
## Impact
A membership in the Matrix Foundation allows the Eclipse Foundation to...
* ...help funding, so the Matrix Protocol will have the power to become the future standard chat protocol on this planet.
* ...express its strong support by mutal linking and logo appearance.
* ...influence the future of the Matrix Protocol in a way that is beneficial for the EF members wrt that EF is running its own Matrix node.https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4457NVD API Key for eclipse-tractusx projects improving dependency check possibil...2024-03-22T19:24:10ZMaximilian WesenerNVD API Key for eclipse-tractusx projects improving dependency check possibilities## Summary
OWASP Dependency Check takes very long without api key.
Can we request an api key for the organziation or the project? https://nvd.nist.gov/general/news/API-Key-Announcement
## Steps to reproduce
Open eclipse-tractusx/trace...## Summary
OWASP Dependency Check takes very long without api key.
Can we request an api key for the organziation or the project? https://nvd.nist.gov/general/news/API-Key-Announcement
## Steps to reproduce
Open eclipse-tractusx/traceability-foss project and execute the action: https://github.com/eclipse-tractusx/traceability-foss/actions/runs/8353452321/job/22865193054
## What is the current bug behavior?
The action runs sometimes longer than 2 hours.
## What is the expected correct behavior?
The action runs within a normal time frame. Provide an api key to be able to have normal runs.
## Relevant logs and/or screenshots
Please see logs of action: https://github.com/eclipse-tractusx/traceability-foss/actions/runs/8353452321/job/22865193054
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Low
## Impact
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example:
"We have a release tomorrow")
Cost of github actionshttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4454Enable forced confirmation for GH actions for external committers2024-03-21T09:56:33ZOliver KlapperEnable forced confirmation for GH actions for external committers## Summary
Currently, if an project-external opens a PR a project lead must confirm one times that GH actions can be executed inside the PR.
However, after this one time approval the committer can execute the GH actions with every commi...## Summary
Currently, if an project-external opens a PR a project lead must confirm one times that GH actions can be executed inside the PR.
However, after this one time approval the committer can execute the GH actions with every commit.
A committer might inject the pipeline or do something unwanted with the CI / CD pipeline.
We wanted to change the setting that every commit on a PR that was not opened by an official contributor must be approved by an project lead allowing GH actions to be executed.
The setting is not available via the self-service.
Repository: https://github.com/eclipse-ankaios/ankaios
## Steps to reproduce
Described above in the summary.
## What is the current bug behavior?
Only one time approvals for GH actions for external committers not being elected as official contributors.
## What is the expected correct behavior?
GH actions shall require always a confirmation by a project lead.
## Relevant logs and/or screenshots
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Low
## Impact
Impact on security.https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4453Mailing list From address broken2024-03-21T19:15:17ZGunnar WagenknechtMailing list From address brokenThe FROM address of some mailing lists seems to be broken.
For some my mail client shows:
> Denis Roy via eclipse.org-committers <eclipse.org-committers@eclipse.org>
![image](/uploads/befa50606aa5c2163b18e0720a3f3e26/image.png)
But fo...The FROM address of some mailing lists seems to be broken.
For some my mail client shows:
> Denis Roy via eclipse.org-committers <eclipse.org-committers@eclipse.org>
![image](/uploads/befa50606aa5c2163b18e0720a3f3e26/image.png)
But for quite a lot mailing lists it now shows:
> Technology PMC <technology-pmc@eclipse.org>
> Eclipse JDT general development list. <jdt-dev@eclipse.org>
![image](/uploads/3e954e3e4735460f2e7d400759fa8cbd/image.png)
That makes mailing lists unusable. Please include the sender name in the From address display.Matt WardMatt Wardhttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4452Use of docker image in openPASS2024-03-22T10:17:04ZRaghunandan Netrapalli MadhusudhanUse of docker image in openPASSAs part of the issue #3831, `eclipseopenpass` repository on dockerhub is created (https://hub.docker.com/u/eclipseopenpass).
As per the example (https://github.com/eclipse-cbi/dockerfiles/pull/33) referenced in the issue #3831, we are u...As part of the issue #3831, `eclipseopenpass` repository on dockerhub is created (https://hub.docker.com/u/eclipseopenpass).
As per the example (https://github.com/eclipse-cbi/dockerfiles/pull/33) referenced in the issue #3831, we are unsure of `CREDENTIALS_ID`. Is it specific to eclipsecbi or is it something we could use as well? If not, could you please help us with the CREDENTIALS_ID for eclipseopenpass.
Also to integrate jenkins-pipeline-library, would you suggest `main` as the version or any latest tag as in `@Library('releng-pipeline@main')` or `@Library('releng-pipeline@v0.11.0')`
We would appreciate if you could provide us detailed process on how to integrate into our CI and also the possible way to delete the docker image from the dockerhub in case if necessity arises.Sébastien Heurtemattesebastien.heurtematte@eclipse-foundation.orgSébastien Heurtemattesebastien.heurtematte@eclipse-foundation.orghttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4447remove branch protection for repos governed by ee4j.jaxb and ee4j.jaxws2024-03-20T19:37:57ZLukas Jungmannremove branch protection for repos governed by ee4j.jaxb and ee4j.jaxwsevery PR in https://github.com/jakartaee/jax-ws-api, https://github.com/jakartaee/saaj-api/ and https://github.com/jakartaee/jaxb-api/ repos currently requires at least 1 approving review. Given number of active committers in these proje...every PR in https://github.com/jakartaee/jax-ws-api, https://github.com/jakartaee/saaj-api/ and https://github.com/jakartaee/jaxb-api/ repos currently requires at least 1 approving review. Given number of active committers in these projects is low, this became an obstacle. I'd like to ask for removing this requirement on PRs there.https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4444Update to MSVC 2022 and latest Windows 10 SDK on rs68g-win10 in RelEng JIPP2024-03-20T16:55:04ZHannes WellmannUpdate to MSVC 2022 and latest Windows 10 SDK on rs68g-win10 in RelEng JIPP## Summary
Now that the [new win32-aarch64 node in the RelEng JIPP uses MSVC 2022](https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4276#note_1982668), it would be good to be consistent and to use Visual Studio 2022 also to compi...## Summary
Now that the [new win32-aarch64 node in the RelEng JIPP uses MSVC 2022](https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4276#note_1982668), it would be good to be consistent and to use Visual Studio 2022 also to compile the x86_64 windows binaries SWT native binaries.
Therefore can you please update Visual Studio/MSVC in https://ci.eclipse.org/releng/computer/rs68g%2Dwin10/ to
* Visual Studio with C++ Community 2022
* Latest Windows 10 SDK (since it is a Win10 machine we should probably not go to the Win11 SDK, although in practice it would probably not be a big difference, would it?)
On my local computer I also build the SWT windows natives using MSVC 2022 and didn't notice any issue.
@akurtakov, @aloskutov are you fine with this?
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Lowhttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4443[Tractus-X] Increase public APIs limit at SwaggerHub2024-03-19T14:19:25ZTomasz Barwicki[Tractus-X] Increase public APIs limit at SwaggerHub## Summary
Teams are reporting unability to publish public APIs at SwaggerHub due to reached 3 APIs limit (according to current plan).
Please follow https://github.com/eclipse-tractusx/sig-infra/issues/455 for more details.
## What is ...## Summary
Teams are reporting unability to publish public APIs at SwaggerHub due to reached 3 APIs limit (according to current plan).
Please follow https://github.com/eclipse-tractusx/sig-infra/issues/455 for more details.
## What is the expected correct behavior?
Ability to publish API.
## Relevant logs and/or screenshots
Logs from workflow run: https://github.com/eclipse-tractusx/traceability-foss/actions/runs/8327540374/job/22785455605
## Priority
- [ ] Urgent
- [ ] High
- [ ] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [ ] Normal
- [ ] Low
CC: @fgurr, @sigihttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4431Use of binder_rs in Apache 2.0 codebase2024-03-27T14:40:47ZSteven HartleyUse of binder_rs in Apache 2.0 codebaseNeed some Eclipse legal advice w.r.t licensing.
We would like to consume in [Eclipse-uProtocol](https://github.com/eclipse-uprotocol/) the project https://github.com/Kernel-SU/binder_rs in one of the sub projects. All of the uProtocol i...Need some Eclipse legal advice w.r.t licensing.
We would like to consume in [Eclipse-uProtocol](https://github.com/eclipse-uprotocol/) the project https://github.com/Kernel-SU/binder_rs in one of the sub projects. All of the uProtocol is Apache 2.0 on purpose so there are no issues with using it in EOM production code. The binder_rs code is mainly (99%) fork of code from AOSP that has Apache 2.0 license however the project itself is missing a LICENSE file. Given there is no LICENSE, would it be OK to include this code or will it cause issues with Eclipse legal review (as well as issues with IP)?
If we couldn't directly include it, could we fork the project, add the LICENSE and then include the project?
## Priority
- [ ] Urgent
- [X] High
- [ ] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [X] Major
- [ ] Normal
- [ ] Low
## Impact
We need this library for implementing functionality of the project.Wayne BeatonWayne Beaton2024-03-21https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4428Resolve MDT GIT publishing / redirects2024-03-14T16:17:56ZEd WillinkResolve MDT GIT publishing / redirectsThe long discussion in #3484 (Missing mdt ocl redirects) started as an mdt ocl problem that was 'fixed' but revealed mdt modisco problems caused by stomping.
The long discussion addressed long term de-containerisation and medium term GIT...The long discussion in #3484 (Missing mdt ocl redirects) started as an mdt ocl problem that was 'fixed' but revealed mdt modisco problems caused by stomping.
The long discussion addressed long term de-containerisation and medium term GIT merging.
This issue is focussed solely on identifying what is wrong today and fixing it easily. Please avoid the red herrings.
The final two paragraphs provide the solution if you feel confident in skipping the description of the historic mess.
Historically, prior to 2012, the following accesses
- www.eclipse.org/modeling/x was serviced from /cvsroot/modeling/x
- www.eclipse.org/modeling/mdt/y was serviced from /cvsroot/modeling/mdt/y
- www.eclipse.org/modeling/mdt/ocl/z was serviced fromn /cvsroot/modeling/mdt/ocl/z
- www.eclipse.org/modeling/mdt/uml2/z was serviced fromn /cvsroot/modeling/mdt/uml2/z
/cvsroot was a flat monolith with file protections isolating unauthorised committers.
I understand that some publishing rule, such as a poll CVS for changes every 15 minutes refreshed a monolithic www tree from cvsroot.
The first GITification in 2012 changed the mapping so that ideally
- www.eclipse.org/modeling/x was serviced from modeling/x in www.eclipse.org/modeling.git
- www.eclipse.org/modeling/mdt/y was serviced from mdt/y in www.eclipse.org/modeling/mdt.git
- www.eclipse.org/modeling/mdt/ocl/z was serviced from ocl/z in www.eclipse.org/modeling/mdt/ocl.git
- www.eclipse.org/modeling/mdt/uml2/z was serviced from uml2/z in www.eclipse.org/modeling/mdt/uml2.git
I suspect that once again some polling rule refreshed a monolithic www tree from a GIT change.
Unfortunately the content for www.eclipse.org/modeling/mdt/y is also available from modeling/mdt/y in www.eclipse.org/modeling.git.
There is therefore an ambiguity as to where www.eclipse.org/modeling/mdt/y should be edited and an opportunity for divergence.
Unfortunately the creators of the ambiguity, presumably the webmasters, neglected to ensure that the modeling.git committers deleted
the material 'moved' to mdt.git. (This could still be done now, but may conflict with longer term tidy ups.)
Fortunately the very low edit rate and restrictive committer authorisations mean that no edits have occurred to from modeling/mdt/y
since gitification. Only 10 files have evolved and 10 files been created in mdt.git (10 files have also been deleted and moved to ocl-website.git).
ocl.git and uml2.git were never used.
Introduction of eclipse.dev behind www.eclipse.org introduced a complexity that I do not understand.
I presume there are some redirect rules, which I am unable to review. Since these were apparently tweaked to 'fix'
#3484 I suspect that they are non-trivial and wrong.
The current reGITification changes the mapping to
- www.eclipse.org/modeling/x is serviced from modeling/x in www.eclipse.org/modeling.git
- www.eclipse.org/modeling/mdt/y is serviced from mdt/y in github.com:eclipse-mdt/mdt-website.git
- www.eclipse.org/modeling/mdt/ocl/z is serviced fromn ocl/z in github.com:eclipse-ocl/ocl-website.git
- www.eclipse.org/modeling/mdt/uml2/z is serviced fromn uml2/z in www.eclipse.org/modeling/mdt/uml2.git
The mix of new and old style GITs presumably requires complexity in the publishing / redirect rules that
can explain why the 2012 version of modeling/mdt/downloads/index.php is being published from www.eclipse.org/modeling.git
rather than my MoDisco-supporting 2019 edit of mdt/downloads/index.php from github.com:eclipse-mdt/mdt-website.git
Since I cannot see what is happening internally I offer two simple solutions depenbent on what I cannot see.
If the problem is in polled GIT publishing rules
- republish all from GIT bottom-up. i.e. modeling then mdt then ocl so that most contained wins.
- or touch all changed files in mdt.git so that re-polling stomps on modeling.git
If the problem is in the redirect rules
- ensure that the rules are prioritised so that ocl redirects before mdt before modeling.https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4422Eclipse Kura Jenkins builds fail on Sonar stage2024-03-26T12:00:46ZPierantonio MerlinoEclipse Kura Jenkins builds fail on Sonar stage## Summary
The Eclipse Kura jenkins builds fail after the Sonar stage with this exception:
```plaintext
Exception in thread "main" java.lang.NoSuchMethodError: 'java.lang.String org.eclipse.equinox.p2.core.IProvisioningAgent.getPropert...## Summary
The Eclipse Kura jenkins builds fail after the Sonar stage with this exception:
```plaintext
Exception in thread "main" java.lang.NoSuchMethodError: 'java.lang.String org.eclipse.equinox.p2.core.IProvisioningAgent.getProperty(java.lang.String)'
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getAgentPropertyWithFallback(SimpleArtifactRepository.java:813)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getMaximumThreads(SimpleArtifactRepository.java:1012)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifacts(SimpleArtifactRepository.java:900)
at org.eclipse.tycho.repository.p2base.artifact.repository.LazyArtifactRepository.getArtifacts(LazyArtifactRepository.java:102)
at org.eclipse.tycho.repository.p2base.artifact.repository.RepositoryArtifactProvider.getArtifactFromAnyChildRepository(RepositoryArtifactProvider.java:213)
at org.eclipse.tycho.repository.p2base.artifact.repository.RepositoryArtifactProvider.getArtifactFromAnyFormatAvailableInRepository(RepositoryArtifactProvider.java:180)
at org.eclipse.tycho.repository.p2base.artifact.repository.RepositoryArtifactProvider.getArtifactFromAnySource(RepositoryArtifactProvider.java:166)
at org.eclipse.tycho.repository.p2base.artifact.provider.CompositeArtifactProviderBaseImpl.getArtifact(CompositeArtifactProviderBaseImpl.java:54)
at org.eclipse.tycho.repository.local.MirroringArtifactProvider.downloadCanonicalArtifact(MirroringArtifactProvider.java:326)
at org.eclipse.tycho.repository.local.MirroringArtifactProvider.downloadMostSpecificNeededFormatOfArtifact(MirroringArtifactProvider.java:319)
at org.eclipse.tycho.repository.local.MirroringArtifactProvider.downloadArtifact(MirroringArtifactProvider.java:304)
at org.eclipse.tycho.repository.local.MirroringArtifactProvider.makeOneFormatLocallyAvailable(MirroringArtifactProvider.java:243)
at org.eclipse.tycho.repository.local.MirroringArtifactProvider.makeLocallyAvailable(MirroringArtifactProvider.java:193)
at org.eclipse.tycho.repository.local.MirroringArtifactProvider.getArtifactFile(MirroringArtifactProvider.java:132)
at org.eclipse.tycho.repository.p2base.artifact.provider.CompositeArtifactProvider.getArtifactFile(CompositeArtifactProvider.java:87)
at org.eclipse.tycho.p2.target.TargetPlatformBaseImpl.getLocalArtifactFile(TargetPlatformBaseImpl.java:163)
at org.eclipse.tycho.p2.resolver.DefaultP2ResolutionResult.lambda$2(DefaultP2ResolutionResult.java:89)
at org.eclipse.tycho.p2.resolver.DefaultP2ResolutionResultEntry.getLocation(DefaultP2ResolutionResultEntry.java:74)
at org.eclipse.tycho.p2.resolver.P2DependencyResolver.lambda$newDefaultTargetPlatform$5(P2DependencyResolver.java:482)
at org.eclipse.tycho.core.osgitools.targetplatform.ArtifactCollection.lambda$addArtifactFile$2(ArtifactCollection.java:69)
at org.eclipse.tycho.core.osgitools.DefaultArtifactDescriptor.getLocation(DefaultArtifactDescriptor.java:71)
at org.eclipse.tycho.core.osgitools.targetplatform.ArtifactCollection.lambda$addArtifact$3(ArtifactCollection.java:124)
at org.eclipse.tycho.core.osgitools.DefaultArtifactDescriptor.getLocation(DefaultArtifactDescriptor.java:71)
at org.eclipse.tycho.core.osgitools.targetplatform.ArtifactCollection.lambda$addArtifact$3(ArtifactCollection.java:124)
at org.eclipse.tycho.core.osgitools.DefaultArtifactDescriptor.getLocation(DefaultArtifactDescriptor.java:71)
at org.eclipse.tycho.core.maven.MavenDependencyInjector.collectExternalDependencies(MavenDependencyInjector.java:175)
at org.eclipse.tycho.core.maven.MavenDependencyInjector.addDependency(MavenDependencyInjector.java:146)
at org.eclipse.tycho.core.maven.MavenDependencyInjector.injectMavenDependencies(MavenDependencyInjector.java:74)
at org.eclipse.tycho.p2.resolver.P2DependencyResolver.injectDependenciesIntoMavenModel(P2DependencyResolver.java:506)
at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:183)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.lambda$resolveProjects$3(TychoMavenLifecycleParticipant.java:254)
at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at java.base/java.util.stream.WhileOps$1$1.accept(WhileOps.java:99)
at java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1602)
at java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:129)
at java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:527)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:513)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.resolveProjects(TychoMavenLifecycleParticipant.java:292)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:264)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
```
The failing build is [here](https://ci.eclipse.org/kura/job/multibranch/job/develop/983/). The last succeded build is [here](https://ci.eclipse.org/kura/job/multibranch/job/develop/981/). We rebuild also some PRs that succeded days ago with the same result. So, it seems that this is not related to our code.
## Steps to reproduce
Run a build on Eclipse Kura Jenkins with the develop branch.
## What is the current bug behavior?
The build fails.
## What is the expected correct behavior?
The build succeed.
## Relevant logs and/or screenshots
[Here](https://ci.eclipse.org/kura/job/multibranch/job/develop/983/) is a failing build.
## Priority
- [ ] Urgent
- [x] High
- [ ] Medium
- [ ] Low
## Severity
- [x] Blocker
- [ ] Major
- [ ] Normal
- [ ] Low
## Impact
Unfortunately we cannot build the project anymore.Frederic Gurrfrederic.gurr@eclipse-foundation.orgFrederic Gurrfrederic.gurr@eclipse-foundation.orghttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4415cppcheck Jenkins plugin on 4diac JIPP is deprecated and should be removed.2024-03-11T22:41:33ZFrederic Gurrfrederic.gurr@eclipse-foundation.orgcppcheck Jenkins plugin on 4diac JIPP is deprecated and should be removed.## Summary
The cppcheck Jenkins plugin is deprecated and has an unresolved security vulnerability (see https://plugins.jenkins.io/cppcheck/). It should be removed rather soon.
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
...## Summary
The cppcheck Jenkins plugin is deprecated and has an unresolved security vulnerability (see https://plugins.jenkins.io/cppcheck/). It should be removed rather soon.
## Priority
- [ ] Urgent
- [ ] High
- [x] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Low
/cc @azoitlAlois ZoitlAlois Zoitlhttps://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4409Compilation of fat jar including frontend components2024-03-12T11:37:48ZMarcos Didonet Del FabroCompilation of fat jar including frontend components## Summary
The build of the PapyrusWeb project cannot be done, because there are missing components in the Eclipse CI runner image, and we cannot set up a GitHub Access token.
The PapyrusWeb project (https://gitlab.eclipse.org/eclipse/...## Summary
The build of the PapyrusWeb project cannot be done, because there are missing components in the Eclipse CI runner image, and we cannot set up a GitHub Access token.
The PapyrusWeb project (https://gitlab.eclipse.org/eclipse/papyrus/org.eclipse.papyrus-web) build produces both frontend application and backend server. It relies on node and npm for frontend build and mvn for backend build, and it needs to access the GitHub repository of Sirius components to fetch required packages.
## Steps to reproduce
The building steps are described in the project README file (https://gitlab.eclipse.org/eclipse/papyrus/org.eclipse.papyrus-web/-/blob/master/README.adoc?ref_type=heads#build).
However, we cannot set up the building process for the PapyrusWeb project in the Eclipse CI. The latest build execution log is available here: https://ci.eclipse.org/papyrus/view/PapyrusWeb/job/Papyrus-Web-Master/lastBuild/console.
Problems:
The execution flow from the build is incomplete, for two reasons:
* It is necessary to have a GitHub access token to configure the settings.xml (for mvn) and .npmrc (for npm) files. The token is used to fetch packages when compiling the frontend using npm and to access the Sirius Components GitHub package repository, when compiling the backend. How is it possible to obtain a GitHub access token ? We don't want to use a personal access token.
* npm and node are not available in the runner.
The two commands below cannot be executed.
```
npm ci
npm run build
```
Is it possible to install the required components ?
## What is the current bug behavior?
The build cannot be done, because npm is not available and there is not a GitHub access token.
## What is the expected correct behavior?
Execute the complete build and produce a jar of the PapyrusWeb application.
## Relevant logs and/or screenshots
Example of failed build:
https://ci.eclipse.org/papyrus/view/PapyrusWeb/job/Papyrus-Web-Master/lastBuild/console
Note that this build do not call the npm ci command yet.
## Priority
- [ ] Urgent
- [x] High
- [ ] Medium
- [ ] Low
## Severity
- [ ] Blocker
- [ ] Major
- [x] Normal
- [ ] Low
## Impact
We cannot compile PapyrusWeb application. It is important to have daily build in the development process.Frederic Gurrfrederic.gurr@eclipse-foundation.orgFrederic Gurrfrederic.gurr@eclipse-foundation.org