[JIRA] (JENKINS-39278) new pipeline build not started by p4 trigger if existing pipeline already running

[jenk...@richardlee.name (JIRA)]

Title: Message Title

Richard Lee created an issue   Jenkins / JENKINS-39278 new pipeline build not started by p4 trigger if existing pipeline already running Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 2016/Oct/26 7:20 PM Priority: Minor Reporter: Richard Lee It appears that the build trigger provided by the p4 plugin does not launch a new pipeline build if a new change is submitted. It seems to not be obeying the 'Do not allow concurrent builds' setting of pipelines. If that setting is disabled, multiple pipeline builds should be allowed simultaneously, and the pipeline script itself should take care to mediate locking of shared resources. This effectively makes the p4 trigger useless on pipelines that have any sort of long running parallelized test processes, and requires falling back to polling (or using github.com). 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.