[
https://issues.apache.org/jira/browse/CAMEL-25269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124925#comment-18124925
]
Guillaume Nodet commented on CAMEL-25269:
-----------------------------------------
PR opened: https://github.com/apache/camel/pull/27559
The fix adds a new dedicated GitHub Actions workflow ({{pr-license-check.yml}})
that runs {{mvn license:check -N}} on every PR targeting main, with no
{{paths-ignore}} entries.
This ensures that PRs adding new file types (such as Jenkinsfile.jdkNN) are
always checked against the Mycilla license plugin configuration, even when the
full pr-build-main.yml build is skipped due to its {{paths-ignore}} entries for
Jenkinsfile and Jenkinsfile.*.
_Note: This comment was generated by an AI coding agent on behalf of gnodet._
> Ensure PR GitHub check for Mycilla license check when a new file is created
> ---------------------------------------------------------------------------
>
> Key: CAMEL-25269
> URL: https://issues.apache.org/jira/browse/CAMEL-25269
> Project: Camel
> Issue Type: Task
> Components: build system
> Affects Versions: 4.23.0
> Reporter: Aurélien Pupier
> Assignee: Guillaume Nodet
> Priority: Major
>
> for isntance when adding a jenkinsfile.jdk28 , I would like the GitHub PR
> check to detect if the Mycilla License plugin is well configured (was caught
> by the problem both tfor JenkinsFile.jdk26 and JenkinsFile.jdk27
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
