[JIRA] (JENKINS-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Paul Allen commented on JENKINS-49628 Re: Perforce "Workspace Name Format" reset to literal Issue resolved in release 1.9.5 https://swarm.workshop.perforce.com/changes/24942 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Karl Wirth closed an issue as Fixed Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Karl Wirth Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title
Karl Wirth edited a comment on JENKINS-49628
Re: Perforce "Workspace Name Format" reset to literal
Have moved After discussion with developers, closing this issue.Note: If using the implicit sync that comes with P4-Jenkins the workspace name format used on the master to being an improvement request because it's working as designed extract the Jenkins file now includes the source path:{code:java}Obtained Jenkinsfile from p4-JenkinsMaster-//depot/project1/main/ . Changing label ..{code}but the workspace used to P4_VERIFY implicitly sync the files does inherit the workspace naming format from the configuration page . For example:{code:java}jenkins-dockeragent-0kgxgj1jh-Pipeline_Docker_Test-0{code}Note: You may need to run one manual build to enforce the new naming for ech job impacted.If it is still a problem for you please provide us example using P4-Plugin 2.9.4 or later and a demonstration of where the name is incorrect.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Karl Wirth Labels: P4_SUPPORT P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Karl Wirth commented on JENKINS-49628 Re: Perforce "Workspace Name Format" reset to literal Have moved this to being an improvement request because it's working as designed. Changing label to P4_VERIFY. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Karl Wirth Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Karl Wirth Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Paul Allen assigned an issue to Karl Wirth Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Paul Allen Assignee: Karl Wirth Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title
Paul Allen edited a comment on JENKINS-49628
Re: Perforce "Workspace Name Format" reset to literal
Lightweight checkout creates a temporary workspace to fetch the Jenkinsfile and uses a 'p4 print' on that file instead of a sync.If Lightweight checkout is used then the workspace name format is changed to {{jenkinsTemp-}}.This should only be used with Pipeline scripts e.g. {{pipeline\{...\}}} and not {{node()\{...\}}} if you want to make use of the implicit checkout , or . To disable using implicit checkout use the options:{code:java}options { skipDefaultCheckout() }{code}Recent changes in 1.8.12 should resolve parallel and concurrent builds problems with Lightweight checkout, especially when using Global Libraries.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title
Paul Allen commented on JENKINS-49628
Re: Perforce "Workspace Name Format" reset to literal
Lightweight checkout creates a temporary workspace to fetch the Jenkinsfile and uses a 'p4 print' on that file instead of a sync. If Lightweight checkout is used then the workspace name format is changed to jenkinsTemp-. This should only be used with Pipeline scripts e.g. pipeline{...} and not node(){...} if you want to make use of the implicit checkout, or disable using the options:
options { skipDefaultCheckout() }
Recent changes in 1.8.12 should resolve parallel and concurrent builds problems with Lightweight checkout, especially when using Global Libraries.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Brian Jackson commented on JENKINS-49628 Re: Perforce "Workspace Name Format" reset to literal Am running into this same issue. Disabling lightweight checkout means I have to sync 100GB+ of project content to my master node just to get the Jenkinsfile from Perforce. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Karl Wirth Labels: P4_SUPPORT 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Karl Wirth commented on JENKINS-49628 Re: Perforce "Workspace Name Format" reset to literal Am working with Simon on this. Currently its working as designed: https://swarm.workshop.perforce.com/changes/23373 However there is a bug that causes the whole client to be synced after the Jenkinsfile has been retrieved. JENKINS-49678 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Simon Watts commented on JENKINS-49628 Re: Perforce "Workspace Name Format" reset to literal Confirmed that enabling "lightweight checkout" is the cause: Project has correct template for "Workspace Name Format" and "lightweight checkout" is enabled. Build the Project. Project now has the corrupted literal in the "Workspace Name Format" field. Correct "Workspace Name Format" field and disabled "lightweight checkout" of the Jenkins file. Build the Project. Project still has the correct template value in its "Workspace Name Format" field. 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title
Simon Watts updated an issue
Jenkins / JENKINS-49628
Perforce "Workspace Name Format" reset to literal
Change By:
Simon Watts
When configuring a Pipeline project with source from Perforce, it is required to set a _*"Workspace Name Format"*_ as a template which can be used to generate per-node, per-executor workspace names required by Perforce.The default value for this field is adequate and we have not felt the need to change it:{noformat}jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}{noformat}Furthermore the field requires that the value contains at least one substitution variable to be accepted.I recently noticed that our project's workspace name formats had changed to literal values such as:{noformat}jenkinsTemp-87602970-2871-43c1-9759-0b16964ffa42{noformat}Which does not match any expansion of the original name format.This change also corresponds to issues recently observed whereby developers have stopped getting emails on failed builds (which was previously working). In fact, even though builds are triggered by SCM changes, the associated change list is empty.We presume that this is a consequence of the Jenkins build now using the same workspace name for different build nodes and executors – I believe that Perforce frowns on such things.Having changed all projects back to the default template on Friday evening, looking again today and every project which has been rebuilt since then once again has a literal value in place of the template.*Light weight checkout?*_Since this wasn't happening before, we look for something that has changed..._The most likely candidate is that all projects were recently switched to using _"Lightweight Checkout"_ to obtain the Jenkinsfile – this capability became supported by P4 Plugin with release 1.8.4. This mechanism saves a lot (in our case) of disk space by avoiding the need for an additional workspace sync just to get the Jenkinsfile.This would also be in line with the literal workspace name appearing in project configurations not being related to the original template format.*Hypothesis*P4 Plugin light weight checkout of the Jenkins file is overwriting the workspace name template for projects with the literal workspace name used during the lightweight checkout, and rendering the project incompatible with Perforce.*Scenario*Our builds are principle C/C++ code built using a makefile, driven by a script which sets the variables as appropriate to the build host and target.Each project interacts with Perforce as follows: # A template workspace defined in Perforce. # A Jenkinsfile from Perforce in the project's home directory – using lightweight checkout. # A Jenkins extension library also held in Perforce is loaded by default. # The project sources from Perforce as defined by the template workspace.This has been the same for a while now, and the recent change of enabling lightweight checkout on the Jenkinsfile (2) seems the most likely candidate for triggering the bug. *Attached:* * Pipeline configuration with corrupted
[JIRA] (JENKINS-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Simon Watts updated an issue Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Simon Watts Attachment: JENKINS-49628-1.png 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title
Simon Watts created an issue
Jenkins / JENKINS-49628
Perforce "Workspace Name Format" reset to literal
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-02-19 14:46
Environment:
Jenkins 2.89.2 P4 Plugin 1.8.5 Java: 1.8.0_51-b31 (Oracle, 64-bit) Master on RedHat Enterprise Linux 6.6 x86_64. Perforce Server version: P4D/LINUX26X86_64/2017.1/1545029 (2017/08/16)
Priority:
Major
Reporter:
Simon Watts
When configuring a Pipeline project with source from Perforce, it is required to set a "Workspace Name Format" as a template which can be used to generate per-node, per-executor workspace names required by Perforce. The default value for this field is adequate and we have not felt the need to change it:
jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}
Furthermore the field requires that the value contains at least one substitution variable to be accepted. I recently noticed that our project's workspace name formats had changed to literal values such as:
jenkinsTemp-87602970-2871-43c1-9759-0b16964ffa42
Which does not match any expansion of the original name format. This change also corresponds to issues recently observed whereby
