[JIRA] (JENKINS-41146) SCM Trigger configuration being overwritten by SYSTEM user in Pipeline

[dyer.d.jonat...@gmail.com (JIRA)]

Title: Message Title

Jonathan Dyer commented on JENKINS-41146   Re: SCM Trigger configuration being overwritten by SYSTEM user in Pipeline James Dumay, // Setup Job properties properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '30', numToKeepStr: '')), disableConcurrentBuilds(), pipelineTriggers([])]) The offending bit is "pipelineTriggers([])". It's now my understanding that any properties defined within the pipeline script will supersede and overwrite on disk the properties manually set on the Job itself. I have tested this theory and created a job with a single build parameter, then used the exact same properties I noted above which has no mention of build parameters. The initial run allowed me to select a build parameter, but after that the config changed and it was no longer an option. So it appears that pipeline properties will override all configurations it is able to, regardless if specified within the pipeline script or not. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.