Trigger acceptance tests ai on new pushes to main#1971
Trigger acceptance tests ai on new pushes to main#1971jordimassaguerpla wants to merge 1 commit intoSUSE:masterfrom
Conversation
Signed-off-by: Jordi Massaguer Pla <jmassaguerpla@suse.com>
There was a problem hiding this comment.
Pull request overview
Adds an automated trigger to run the MLM AI acceptance-test Jenkins pipeline when SCM changes are detected (intended for new pushes to main).
Changes:
- Add an SCM polling trigger (
pollSCM) to the declarative pipeline to check for changes every 5 minutes.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| triggers { | ||
| // Poll the SCM every five minutes for changes. | ||
| // 'H' is used to spread out the load on Jenkins. | ||
| // This requires the Jenkins job to be configured to point to the mcp-server-uyuni git repository. | ||
| pollSCM('H/5 * * * *') | ||
| } |
There was a problem hiding this comment.
pollSCM only polls the Jenkins job’s configured SCM (or checkout scm in multibranch). This Jenkinsfile explicitly checks out https://github.com/uyuni-project/mcp-server-uyuni.git via the git step, which is not the SCM being polled, so this may not actually trigger on new pushes to mcp-server-uyuni/main and may instead poll whatever repo the job is configured with (often the repo containing this Jenkinsfile). If the intent is “run on pushes to mcp-server-uyuni main”, consider moving/configuring the job as “Pipeline script from SCM” pointing at that repo (so polling/webhooks track the right branch), or switch to a time-based cron(...) trigger and handle change detection explicitly inside the pipeline.
There was a problem hiding this comment.
@copilot apply changes based on this feedback
No description provided.