refactor: hudson.maven.MavenModuleSet is now treated as a scope#7599
Conversation
|
@sstojak1 Have you tested it ? And it works as expected? |
|
Looks good to me in terms of a fix. |
|
@sstojak1 BTW, are you interested in joining Apache as a Committer? I would like to invite you if you are up for it. Please reach me out on Slack if you do, my name is "Klesh Wong" on the channel. |
|
@klesh makes sense to have scope as a default since there should be more jobs that should be treated as |
|
@gustavobini Would you like to take a look at the code? Thanks in advance. |
We had talked over Slack about this. It's a good solution. Thanks @sstojak1 |
|
Thank you all. |
* hudson.maven.MavenModuleSet is now treated as a scope * refactor: scope is now the default --------- Co-authored-by: Josip Stojak <Josip.Stojak@infobip.com>
… (#7745) * hudson.maven.MavenModuleSet is now treated as a scope * refactor: scope is now the default --------- Co-authored-by: sstojak1 <18380216+sstojak1@users.noreply.github.com> Co-authored-by: Josip Stojak <Josip.Stojak@infobip.com>
pr-type/bug-fix,pr-type/feature-development, etc.Summary
What does this PR do?
hudson.maven.MavenModuleSetJenkins pipeline will now be treated as a scopeDoes this close any open issues?
Closes 7598
Screenshots
Include any relevant screenshots here.
Other Information
Any other information that is important to this PR.