[wildfly-dev] Re: Enabling dependabot on https://github.com/wildfly/wildfly-archetypes and other changes
Hi,
it seems dependabot updates e.g. maven plugins only in one archetype,
but not in all?
E.g. https://github.com/wildfly/wildfly-archetypes/pull/34:
maven-war-plugin is updated to 3.4.0 in the webapp archetype, but not in
the ear archetype.
Or did this not happen, because dependabot checks each archetype
project, and after five pull requests it does not continue?
Up to now, I did the plugin updates when updating the WildFly version ;-).
I consider this automatic update a bit dangerous, as there seems to be
no further validation. Is there a mechanism to create a project from
each archetype and deploy it to WildFly? I created testing scripts and
run those tests after each WildFly update. If this is not happening in
the future, a broken archetype might be released.
Best regards
Wolfgang
Am 09.08.23 um 14:34 schrieb Jeff Mesnil:
> Hi,
>
>> On 9 Aug 2023, at 12:04, Jeff Mesnil <jmesnil(a)redhat.com> wrote:
>>
>> 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:
>
> Done. Dependabot has started to open PRs to updates the archetypes pom.xml as well as
the generated projects’s pom.xml:
>
> https://github.com/wildfly/wildfly-archetypes/pulls?q=is%3Apr+label%3Adep...
>
>> 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.
> The default branch is now `main`. The usual instructions to change that in your local
forks apply:
>
> —8<—
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
> —8<—
>
> I’ve enabled a GitHub action to « mvn verify » the archetypes. This means that their
tests (which generates projects) are also testing component updates to the generated
projects’s pom.xml:
>
> https://github.com/wildfly/wildfly-archetypes/actions/workflows/maven.yml
>
> Best regards,
> Jeff
>
> --
> Jeff Mesnil
> Engineer @ Red Hat JBoss EAP
> http://jmesnil.net/
> _______________________________________________
> 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...