Skip to content

Trigger acceptance tests ai on new pushes to main #1971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jordimassaguerpla wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Trigger acceptance tests ai on new pushes to main #1971

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions jenkins_pipelines/mlm_ai/Jenkinsfile_mlm_51_ai_acceptance_tests
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,13 @@ pipeline {
)
}

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 * * * *')
}
Comment on lines +21 to +26
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Member Author

@jordimassaguerpla jordimassaguerpla Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot apply changes based on this feedback


environment {
// Sanitize JOB_NAME for Docker compatibility (lowercase, no illegal chars)
DOCKER_TAG = "${env.JOB_NAME.toLowerCase().replaceAll(/[^a-z0-9]/, '-')}"
Expand Down
Loading