[JIRA] (JENKINS-41764) Perforce triggered build should not trigger polling on jobs unless there are changes related to that view
Title: Message Title Alena Volarevic commented on JENKINS-41764 Re: Perforce triggered build should not trigger polling on jobs unless there are changes related to that view Also the jobs that are being triggered by preforce should be build no matter if they are using Source Code Management or not. Like I have a job that is using the files from the perforce, but I am syncing the workspace files in the build process instead of source code managements portion. and I realized if I don't have source code management set to use perforce. the jobs wont be picked up when the P4 trigger is emitted... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178605.1486395343000.11586.1575414600187%40Atlassian.JIRA.
[JIRA] (JENKINS-41764) Perforce triggered build should not trigger polling on jobs unless there are changes related to that view
Title: Message Title Alena Volarevic commented on JENKINS-41764 Re: Perforce triggered build should not trigger polling on jobs unless there are changes related to that view Is there any progress on this? Also not sure if it's related or not.. but I have a pipeline script job, that is set to "Perforce triggered build" and it never gets picked up when I send manual P4 Trigger. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178605.1486395343000.11574.1575412920176%40Atlassian.JIRA.
[JIRA] (JENKINS-59132) Perforce Workspace spec file root skipped
Title: Message Title
Alena Volarevic created an issue
Jenkins / JENKINS-59132
Perforce Workspace spec file root skipped
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-08-28 20:31
Labels:
p4plugin p4 workspace workspace-root
Priority:
Minor
Reporter:
Alena Volarevic
I have a drive letter (lets say D) that is being used as a root for all the perforce workspaces that we have on our system. I am trying to use the p4 plugin in Jenkins to sync the code before running the unittest or running any script, and no matter what kind of workspace behavior I use (besides the Static one), It is always syncing the code to the {Jenkins workspace}/{JOB_NAME} and I would like to keep it on the D drive as all the perforce workspaces we have are set right now like that. I managed to get this with the Static workspace behavior, but in that case I have to remote to the slave machines to create the workspace by hand and then use it, which then defeats the purpose of Jenkins... I tried using the Spec workspace behavior, cause I though if I specify the root in that file, the perforce workspace should use that folder as a root, but whenever it starts the sync part, it again syncs to the jenkins workspace location and sets the workspace root to use that location for root... It woudl be really nice if we can control where do we want the root to be, if we want to copy the files to the new jenkins workspace or use the root folder that we already had setup before implementing Jenkins. If I'm missing something I apologize for creating this ticket. I am using Jenkins ver 2.190 P4 Plugin 1.10.3 Thanks.
