[JIRA] (JENKINS-38886) Polling broken on Matrix configuration
Title: Message Title Paul Allen closed an issue as Won't Fix No plans to fix this. Jenkins has many limitations with environment variable especially around polling; custom Matrix variables only compounds this problem. Jenkins / JENKINS-38886 Polling broken on Matrix configuration Change By: Paul Allen Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-38886) Polling broken on Matrix configuration
Title: Message Title Adil Akhund-Zade commented on JENKINS-38886 Re: Polling broken on Matrix configuration It is mentioned in wiki limitations : Jenkins job and multi configuration parameters should be expand, but custom or parameterised build variables are unlikely to be available Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38886) Polling broken on Matrix configuration
Title: Message Title Stephen Tunney commented on JENKINS-38886 Re: Polling broken on Matrix configuration My configuration is a standard freestyle project, so I don't think this is isolated to matrix-projects. Here is my P4 polling log: Perforce Software Polling Log Started on Nov 7, 2016 2:54:00 PM No workspace is available, so can’t check for updates. Scheduling a new build to get a workspace. (nonexisting_workspace) Done. Took 1.6 sec Changes found 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-38886) Polling broken on Matrix configuration
Title: Message Title Stephen Tunney commented on JENKINS-38886 Re: Polling broken on Matrix configuration Running Jenkins 2.7.2 with P4 plugin v1.4.8 and I am also hitting this issue. Doesn't matter if it is a stream spec or manual spec configuration. The polling is completely broken and I'm getting continuous builds and a filling build queue. Did anyone actually test this? 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-38886) Polling broken on Matrix configuration
Title: Message Title
Michal Ejdys updated an issue
Jenkins / JENKINS-38886
Polling broken on Matrix configuration
Change By:
Michal Ejdys
After upgrading p4-plugin from 1.0.14 to 1.4.8, all our matrix build configurations started triggering continuously. It turns out, the plugin changed the way it resolves variables in the workspace name for the matrix configuration. The way the SCM polling does it and the actual build is different, which leads to the polling trying to use a non-existent workspace name, and always detecting new changes.Build name: test-build-configWorkspace name in configuration: jenkins-$\{NODE_NAME\}-$\{JOB_NAME\}Polling log, observe the workspace name has been calculated using the JOB_NAME of the job of the first matrix axis combination. In previous versions of the plugin, this would be the build name, so the workspace would be 'jenkins-master-test-build-config'.{code}Perforce Software Polling LogStarted on Oct 11, 2016 12:15:00 AMPolling SCM changes on masterP4: Polling on: master with:jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Value_2-AXIS_3-Value_3... p4 client -o jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Va___ +... p4 info +P4 Task: establishing connection server: perforce-ci.tomtomgroup.com:1666... node: michi-jenkins-00P4: Polling with cstat: //jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Value_2-AXIS_3-Value_3/.. p4 cstat //jenkins-master-test-build-config-AXIS_1-value_1- AXIS_3 AXIS_2 -Valu___ +... p4 change -o 2418201 +... found change: 2418201... p4 change -o 2364282 +... found change: 2364282... p4 change -o 2357042 +... found change: 2357042Done. Took 1.7 secChanges found{code}Build log (the kick off of the master build, before spawning the builds for each matrix axis combination), however, checks out 'jenkins-master-test-build-config'. So the polling workspace and the build workspace are different. And since the former does not exist, each poll triggers a build.
Add Comment
[JIRA] (JENKINS-38886) Polling broken on Matrix configuration
Title: Message Title
Michal Ejdys updated an issue
Jenkins / JENKINS-38886
Polling broken on Matrix configuration
Change By:
Michal Ejdys
After upgrading p4-plugin from 1.0.14 to 1.4.8, all our matrix build configurations started triggering continuously. It turns out, the plugin changed the way it resolves variables in the workspace name for the matrix configuration. The way the SCM polling does it and the actual build is different, which leads to the polling trying to use a non-existent workspace name, and always detecting new changes.Build name: test-build-configWorkspace name in configuration: jenkins-$ \ {NODE_NAME \ }-$ \ {JOB_NAME \ }Polling log, observe the workspace name has been calculated using the JOB_NAME of the job of the first matrix axis combination. In previous versions of the plugin, this would be the build name, so the workspace would be 'jenkins-master-test-build-config'.{code}Perforce Software Polling LogStarted on Oct 11, 2016 12:15:00 AMPolling SCM changes on masterP4: Polling on: master with:jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Value_2-AXIS_3-Value_3... p4 client -o jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Va___ +... p4 info +P4 Task: establishing connection server: perforce-ci.tomtomgroup.com:1666... node: michi-jenkins-00P4: Polling with cstat: //jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Value_2-AXIS_3-Value_3/.. p4 cstat //jenkins-master-test-build-config-AXIS_1-value_1-AXIS_3-Valu___ +... p4 change -o 2418201 +... found change: 2418201... p4 change -o 2364282 +... found change: 2364282... p4 change -o 2357042 +... found change: 2357042Done. Took 1.7 secChanges found{code}Build log (the kick off of the master build, before spawning the builds for each matrix axis combination), however, checks out 'jenkins-master-test-build-config'. So the polling workspace and the build workspace are different. And since the former does not exist, each poll triggers a build.
Add Comment
[JIRA] (JENKINS-38886) Polling broken on Matrix configuration
Title: Message Title
Michal Ejdys created an issue
Jenkins / JENKINS-38886
Polling broken on Matrix configuration
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2016/Oct/11 8:12 AM
Environment:
Jenkins ver. 2.19.1 p4-plugin version 1.4.8 matrix-project 1.6
Priority:
Critical
Reporter:
Michal Ejdys
After upgrading p4-plugin from 1.0.14 to 1.4.8, all our matrix build configurations started triggering continuously. It turns out, the plugin changed the way it resolves variables in the workspace name for the matrix configuration. The way the SCM polling does it and the actual build is different, which leads to the polling trying to use a non-existent workspace name, and always detecting new changes. Build name: test-build-config Workspace name in configuration: jenkins-$ {NODE_NAME} -$ {JOB_NAME} Polling log, observe the workspace name has been calculated using the JOB_NAME of the job of the first matrix axis combination. In previous versions of the plugin, this would be the build name, so the workspace would be 'jenkins-master-test-build-config'.
Perforce Software Polling Log
Started on Oct 11, 2016 12:15:00 AM
Polling SCM changes on master
P4: Polling on: master with:jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Value_2-AXIS_3-Value_3
... p4 client -o jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Va___ +
... p4 info +
P4 Task: establishing connection.
... server: perforce-ci.tomtomgroup.com:1666
... node: michi-jenkins-00
P4: Polling with cstat: //jenkins-master-test-build-config-AXIS_1-value_1-AXIS_2-Value_2-AXIS_3-Value_3/...
... p4 cstat
