Create CI Jenkins instance for Jakarta.config
Summary
Jakarta Config (https://github.com/jakartaee/config) is a new Spec Project within Jakarta EE umbrella. After a long time of discussion, the first version is to be released, but there is no CI assigned to create the release.
What is the expected correct behavior?
We would expect the committers to have access there.
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
While it is blocking the release, the release can wait a few days before the CI is created.