[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.4.11 Jenkins / JENKINS-39652 Add support for polling multiple checkouts with pipeline scripts Change By: Paul Allen Status: Resolved Closed 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.
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title Paul Allen updated JENKINS-39652 Ready for release Jenkins / JENKINS-39652 Add support for polling multiple checkouts with pipeline scripts Change By: Paul Allen Status: In Review Resolved Resolution: Fixed 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.
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title Paul Allen started work on JENKINS-39652 Change By: Paul Allen Status: Open In Progress 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.
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title Paul Allen updated JENKINS-39652 Jenkins / JENKINS-39652 Add support for polling multiple checkouts with pipeline scripts Change By: Paul Allen Status: In Progress Review 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.
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39652 Re: Add support for polling multiple checkouts with pipeline scripts Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java src/main/java/org/jenkinsci/plugins/p4/tasks/AbstractTask.java src/test/java/org/jenkinsci/plugins/p4/client/JenkinsfileTest.java http://jenkins-ci.org/commit/p4-plugin/fb5235393d8b2a1e44271429876b4910defe2463 Log: Polling fix for Multi client support in Pipeline. Jenkins polls for each SCM checkout, so must poll each workplace and therefore need to lookup last build information for each sync. Polling now uses same lookup as Change Summary. Added extra test cases multi sync poll and poll again. JENKINS-38401 JENKINS-37462 JENKINS-39652 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.
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39652 Re: Add support for polling multiple checkouts with pipeline scripts Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/build/P4EnvironmentContributor.java src/main/java/org/jenkinsci/plugins/p4/credentials/P4BaseCredentials.java src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java src/main/java/org/jenkinsci/plugins/p4/tasks/AbstractTask.java src/test/java/org/jenkinsci/plugins/p4/client/JenkinsfileTest.java http://jenkins-ci.org/commit/p4-plugin/ad88e9695891a28332f5e1282698aff18a18f9b7 Log: Multi client support in Pipeline. If two or more `p4sync` operations are called in one Pipeline script, they MUST have different client names. During a build, multiple entries are added to the build history; on subsequent builds they are used in the three following situations: Polling: largest change number across all the checkouts is used. Change Summary: last change with the same client name is used. Environment: last change recorded (regardless of client). Added two test cases to cover basic multi sync build/poll situations. JENKINS-38401 JENKINS-37462 JENKINS-39652 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subs
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title
Pete McNab created an issue
Jenkins / JENKINS-39652
Add support for polling multiple checkouts with pipeline scripts
Issue Type:
New Feature
Assignee:
Paul Allen
Components:
p4-plugin
Created:
2016/Nov/10 5:52 PM
Environment:
Jenkins 2.19.2, all pipeline-related plugins at latest version, p4-plugin at version 1.4.8
Labels:
pipeline
Priority:
Critical
Reporter:
Pete McNab
We're attempting to run some large pipeline jobs. Each job goes and runs a series of parallel jobs on multiple platforms for multiple targets. When adding the options to include in changelog/polling that are now available:
checkout([
changelog: true,
poll: true,
scm: [
$class: 'PerforceScm',
credential: credential,
...
The job will try to poll for changes. It correctly polls the actual Jenkinsfile, but when it goes to poll for each separate checkout in the pipeline script, it loses track of the previous change it built at and continually triggers a new build. The name of our generated clients is: 'jenkins-$ {NODE_NAME} -$ {JOB_NAME} -$ {BUILD_NUMBER} -' + platform The p4 plugins normally adds a "Description:" field into the client tracking the last change. During my testi
