Trigger acceptance tests ai on new pushes to main#2001
Trigger acceptance tests ai on new pushes to main#2001jordimassaguerpla 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
This PR aims to automatically trigger the MLM AI acceptance test Jenkins pipeline when new changes are pushed (per title: on new pushes to main), by adding an SCM polling trigger to the pipeline definition.
Changes:
- Add a Jenkins
triggers { pollSCM('H/5 * * * *') }block to the MLM 5.1 AI acceptance tests pipeline.
💡 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 (typically the repo that contains the Jenkinsfile), not the repository checked out later via the git ... branch: params.MCP_SERVER_BRANCH step. As written, this is unlikely to trigger builds on new pushes to mcp-server-uyuni main (and may instead trigger on commits to this susemanager-ci repo, or do nothing if the job has no SCM configured), so it doesn’t match the PR goal. Consider instead triggering from a job/multibranch pipeline that is actually attached to uyuni-project/mcp-server-uyuni (e.g., GitHub webhook / multibranch) and/or using an upstream trigger that passes the commit/branch to this job.
No description provided.