[
https://issues.apache.org/jira/browse/CAMEL-25269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124916#comment-18124916
]
Guillaume Nodet commented on CAMEL-25269:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
The gap has been confirmed: Jenkinsfile and Jenkinsfile.* paths are excluded
from the PR build trigger in pr-build-main.yml, meaning PRs adding new
Jenkinsfiles bypass the Mycilla license check entirely. Both Jenkinsfile.jdk26
and Jenkinsfile.jdk27 required separate follow-up commits to add license header
mappings.
A fix will be implemented: adding a dedicated lightweight GitHub Actions
workflow to run mvn license:check on all PRs without the paths-ignore exclusion
for Jenkinsfiles.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> 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)
