PR testing with SE 25
by Brian Stansberry
We're continuing to progress with qualifying SE 25 as our recommended
SE version for WildFly. That's getting close enough that we should
look at what we're doing for PR testing. Currently full WF and WF Core
are not testing PRs on SE 25. We're relying on nightly jobs to detect
problems.
A difficulty is CI is a limited resource and we also want to limit our
carbon impact, so just adding more jobs for each PR doesn't seem good.
Perhaps....
On full WF...
Replace the "Linux MicroProfile - JDK 17" job with a 'Linux - JDK 25".
The "Linux MicroProfile" job runs a subset of tests but with server
installation the run the standalone-microprofile.xml config instead of
standalone.xml. It basically validates that the presence of the MP
stuff in the config doesn't break things. I can't remember the last
time that test detected a problem. Probably not the decade. It brings
little value.
Replacing it with a full -DallTests job will mean more resource
consumed per PR though.
On Core....
Reconfigure "WildFly Core -> Preview Integration Linux- JDK 21" to use
SE 25 instead.
That leaves nothing running the core TS on 25 though. Perhaps we could
remove the -DskipTests setting in the step in "WildFly Core -> Preview
Integration Linux- JDK 21" that builds core.
WDYT?
- Brian
1 month
Re: Fabio Burzigotti as a WildFly AS maintainer
by Richard Opalka
Congratulations Fabio!
Rio
On Fri, Feb 13, 2026 at 1:31 PM Tom Jenkinson via wildfly-dev <
wildfly-dev(a)lists.jboss.org> wrote:
> Congratulations, Fabio!
> ------------------------------
> *From:* Brian Stansberry <bstansberry(a)gmail.com>
> *Sent:* 11 February 2026 23:25
> *To:* wildfly-dev(a)lists.jboss.org <wildfly-dev(a)lists.jboss.org>
> *Subject:* [EXTERNAL] [wildfly-dev] Re: Fabio Burzigotti as a WildFly AS
> maintainer
>
> No one's objected to this (no surprise there!) so I went ahead and
> updated the Team.md doc.
>
> Congrats, Fabio!
>
> On Thu, Feb 5, 2026 at 4:41 PM Brian Stansberry <bstansberry(a)gmail.com>
> wrote:
> >
> > I'd like to add Fabio Burzigotti as a Maintainer for the WildFly AS
> project.
> >
> > Fabio's been doing great stuff on WildFly AS for many years now and
> > recently took over leadership of the JBoss WS project. Traditionally
> > the lead of JBoss WS has write permissions to the main WildFly repo so
> > they can handle integration issues. To have write permissions he needs
> > to be a Maintainer.
> >
> > Reference:
> >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wildfly_w...
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wildfly_w...
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> Privacy Statement:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_en_ab...
> List Archives:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.jboss.org_arch...
> Unless otherwise stated above:
>
> IBM United Kingdom Limited
> Registered in England and Wales with number 741598
> Registered office: Building C, IBM Hursley Office, Hursley Park Road,
> Winchester, Hampshire SO21 2JN
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> List Archives:
> https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
>
1 month, 3 weeks
Use of the 'org.wildfly' groupId
by Brian Stansberry
Currently we have a number of different repos publishing artifacts using
the 'org.wildfly' groupId with no further namespacing.
Going forward I don't think we should allow any other new repos to do that.
It leads to administrative hassles, e.g. with setting things up in Nexus.
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
1 month, 4 weeks
