WildFly Calendary Proposal
by Jason Lee
I have a PR open that is a first step in creating a calendar of
WildFly-related events: https://github.com/wildfly/wildfly.org/pull/439
Brian does a great job of emailing the WF dev schedule to this list, but,
for me, it tends to get buried and lost. What I'd love to be able to do is
subscribe to a .ics and have events show up on my calendar. This is a step
toward that. What would be nice is to take that one step further and make
it available in a human-friendly form on wildfly.org as well.
All that said, I would love feedback on the idea itself, the contents of
the calendar, etc. to see if this would be useful to more than just myself.
Additionally, I know we have various community efforts going on at the
moment, so if this overlaps with any of that, I'm happy to roll this into
those efforts.
Jason Lee
Principal Software Engineer
Red Hat JBoss EAP
3 months, 2 weeks
Enabling dependabot on https://github.com/wildfly/wildfly-archetypes and other changes
by Jeff Mesnil
Hi,
I’ve been looking at our archetypes at https://github.com/wildfly/wildfly-archetypes as we could leverage them to improve the user experience of getting started with WildFly (see my previous mail).
The project could benefit from enabling dependabot updates:
* The archetypes would be automatically updated with new WildFly releases. Brian is always making sure that he creates a PR whenever a new version of WildFly is released but this can be automated by dependabot and we would only need to merge a PR instead of having to create the commit manually.
* More importantly, we can also automatically update the generated projects so they use the latest version of any plugins that we configure in their pom.xml
I’ll also take the opportunity to move its default branch to `main` instead of `master` before applying these changes and create a GitHub action to get minimal CI for this project.
Best regards,
jeff
--
Jeff Mesnil
Engineer @ Red Hat JBoss EAP
http://jmesnil.net/
1 year, 8 months
Create a "get started" page on WildFly.org
by Jeff Mesnil
Hi,
We are evaluating how we could improve the user experience for using WildFly and one of the idea is to create a « Get Started » page on wildfly.org <http://wildfly.org/> that would be an entry point for users that wants to try WildFly.
This would be useful not only for new users (that have no previous knowledge of WildFly) but also existing users to let them understand the more recent ways to use WildFly.
The expectation for this page would be simple:
* no knowledge of WildFly required
* Few prerequisites:
* Java & Maven installed
* Few steps:
* Step 1: create a Maven project (using WildFly archetypes, more on that below)
* Step 2: run mvn package
* Step 3: run ./targer/server/bin/standalone.sh
* Step 4: verify the application is up and running
* Next steps
* the page should link to next logical steps after getting started with WildFly (eg deploy on Kubernetes, secure WildFly, etc.)
This page would provide a good user experience and rely on the WildFly archetype to bootstrap all the « plumbing » that needs to be done to setup WildFly so that the users can focus on "their » code.
We already have WildFly archetypes[1] but there are opportunities for a simpler one which focus on that user experience.
Darran is already working on such one[2] that takes advantage of the wildfly-maven-plugin to provision WildFly so that everything is controlled from the project pom.xml
Having a good archetype would also make sure that this "getting started" page is always up to date with the latest release of WildFly (as we update the archetype for every new release of WildFly).
For a quick review of Darran’s PR[3], we are not far from being able to release it and build on top of it for this « get started » page.
We can already start working on this page and create its shell while polishing up the archetype.
What do you think?
Best regards,
jeff
[1] https://mvnrepository.com/artifact/org.wildfly.archetype
[2] https://issues.redhat.com/browse/WFLY-17651
[3] https://github.com/wildfly/wildfly-archetypes/pull/26 <https://github.com/wildfly/wildfly-archetypes/pull/26/commits/16a596b6d26...>
--
Jeff Mesnil
Engineer @ Red Hat JBoss EAP
http://jmesnil.net/
1 year, 8 months
WildFly GitHub Bot
by Martin Stefanko
Hi,
we created a custom wildfly-github-bot that is ready to be deployed to
wildfly/wildfly repository when we get the green light -
https://github.com/xstefank/wildfly-github-bot.
It is a Java application that listens for GitHub events and interacts with
GitHub's public API.
For now, it contains two main features:
1/ PR format verification
Verifies the PR is in the expected format (WFLY-XYZ Test). A simple video
showing this in action https://www.youtube.com/watch?v=RgD7RhEegdc.
2/ Automatic /cc comment based on the changed files in the PR:
For instance, in https://github.com/xstefank/wildfly/pull/65 or
https://github.com/xstefank/wildfly/pull/64 you can see that I'm mentioned
because the commit changed a file under microprofile/lra subdirectory.
The configuration lives in the project that is utilizing the bot -
https://github.com/xstefank/wildfly/blob/main/.github/wildfly-bot.yml. As
you can see, mostly everything is configurable.
The bot is currently deployed in the custom OSD (OpenShift Dedicated)
cluster that we got provisioned just for this purpose. I would be the main
maintainer plus a few guys from SET backing me.
The deployed bot is configured for the https://github.com/xstefank/wildfly
repository. Feel free to open as many PRs as you'd like to experiment with
the bot. Check the configuration file to see what you can do -
https://github.com/xstefank/wildfly/blob/main/.github/wildfly-bot.yml.
Of course, this is just a start. We can add automatic labels, CI triggers,
review requests (if wanted), or milestones, etc. We are only limited by
what can be done on GitHub.
Thanks,
Martin Stefanko
Principal Software Engineer
Middleware Runtimes Sustaining Engineering Team
Red Hat
1 year, 8 months
