[
https://issues.apache.org/jira/browse/ARTEMIS-4764?focusedWorklogId=920267&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-920267
]
ASF GitHub Bot logged work on ARTEMIS-4764:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/May/24 16:23
Start Date: 21/May/24 16:23
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #4925:
URL:
https://github.com/apache/activemq-artemis/pull/4925#issuecomment-2122995622
Seems reasonable, but is presumably going to cause it to spam a bunch of PRs
(10 at a time) initially for various stuff we arent on the latest for, e.g
especially test deps, so I was thinking we should wait until after the
already-delayed release.
Issue Time Tracking
-------------------
Worklog Id: (was: 920267)
Time Spent: 20m (was: 10m)
> Increase automation for dependecy updates
> -----------------------------------------
>
> Key: ARTEMIS-4764
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4764
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> GitHub provides
> [dependabot|https://docs.github.com/en/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates]
> which, among other things, can automatically send PRs for Maven dependency
> updates. This will eliminate much of the manual work.
> However, the following manual steps will still be required to ensure proper
> tracking:
> * Create an associated Jira (the PR's title can be copy & pasted to the Jira)
> * Update the PR branch so the dependabot commit references the Jira
> That said, this is still a pretty big win in terms of overall automation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
