coveooss/lure

Dependency update automation tool.

lure's Issues

Add a proper way to filter unwanted updates

Have a way to ignore updates that contains certain words like rc, beta, alpha, idealy configuration based.

Close branch when a PR was declined -> bitbucket doesn't do this

Invalid / unauthorized reviewer fails PR creation in bitbucket

{"type": "error", "error": {"fields": {"reviewers": ["x does not have access to view this pull request"]}, "message": "reviewers: x does not have access to view this pull request"}}

Add some kind of report to push a notification slack in jenkins with links to opened PRs

Previously declined PR are ignored by Lure

Ignoring PR for junit-5.7-RC will prevent PR for junit-5.7 (not RC) from being opened

Throttling when creating PR is not handled

We should probably wrap all calls to bitbucket to handle throttling

Branch ending with / should be properly reformatted.

Add a limit of PR to open un a single Lure execution

The first time you use Lure, it is possible that it open 100+ it would be great if there was a config to specify the mas number of PR to open per execution.

Warning should be displayed to the users

Duplicated dependencies yield this error message during the versions:display-dependency-updates execution

[WARNING] Some problems were encountered while building the effective model for com.blahblah:some-artifact:jar:1-SNAPSHOT                                                                    
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.zaxxer:HikariCP:jar -> duplicate declaration of version (?) @ line 318, column 21                           
[WARNING]                                                                                                                                                                                                
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.                                                                                              
[WARNING]                                                                                                                                                                                                
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.                                                                                               
[WARNING]                                                                                                   

Those warning should be visible to the users

Failure related to duplicated dependencies should provide a better error message

Duplicated dependencies yield this error message during the versions:display-dependency-updates execution

[WARNING] Some problems were encountered while building the effective model for com.blahblah:some-artifact:jar:1-SNAPSHOT                                                                    
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.zaxxer:HikariCP:jar -> duplicate declaration of version (?) @ line 318, column 21                           
[WARNING]                                                                                                                                                                                                
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.                                                                                              
[WARNING]                                                                                                                                                                                                
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.                                                                                               
[WARNING]                                                                                                    

It probably get caught in the parsing because of the presence of the full artifact name.