[JIRA] (JENKINS-46090) Cannot run two parallel builds with SCM Jenkinsfile script
Title: Message Title Randy Simat commented on JENKINS-46090 Re: Cannot run two parallel builds with SCM Jenkinsfile script I can reproduce this with lightweight checkout enabled as well. 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-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat commented on JENKINS-42076 Re: Manual workspace root reset on every sync I've attached a screenshot depicting the history of the Jenkinsfile client. I have made no changes to the setup of the client itself - these were all done automatically. 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-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset.Pipeline job client: jenkins-master-1.0.0-AppName1. Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName2. Client root is finally set to just $JENKINS_HOMEThe same behavior is exhibited in:Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-JenkinsfileGlobal library client: jenkins-master-1.0.0-LibraryThis has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat Attachment: JenkinsfileExample.PNG 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-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset. Pipeline job client: jenkins-master-1.0.0-AppName 1. Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName2. Client root is finally set to just $JENKINS_HOMEThe same behavior is exhibited in:Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-JenkinsfileGlobal library client: jenkins-master-1.0.0-LibraryThis has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat updated an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Change By: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset.Pipeline job client: jenkins-master-1.0.0-AppName - 1. Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName - 2. Client root is finally set to just $JENKINS_HOME The same behavior is exhibited in:Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-JenkinsfileGlobal library client: jenkins-master-1.0.0-LibraryThis has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received
[JIRA] (JENKINS-42076) Manual workspace root reset on every sync
Title: Message Title Randy Simat created an issue Jenkins / JENKINS-42076 Manual workspace root reset on every sync Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2017/Feb/15 8:10 PM Environment: Jenkins 2.46 with P4 Plugin 1.4.14 Priority: Critical Reporter: Randy Simat It appears that all manual workspaces have their root directories reset with each sync. I have a Pipeline job read from a source controlled Jenkinsfile that references a global library resulting in 3 different clients. In each of them I am seeing the client root continually reset. Pipeline job client: jenkins-master-1.0.0-AppName Client root is set first to the proper directory = $JENKINS_HOME/workspace/JobName Client root is finally set to just $JENKINS_HOME The same behavior is exhibited in: Pipeline Jenkinsfile client: jenkins-master-1.0.0-AppName-Jenkinsfile Global library client: jenkins-master-1.0.0-Library This has resulted in hundreds or thousands of unneeded specs in the spec depot and also restricts the ability to run manual p4 commands using the “sh” build step
[JIRA] (JENKINS-36966) Add LineEnd to Pipeline p4sync
Title: Message Title Randy Simat created an issue Jenkins / JENKINS-36966 Add LineEnd to Pipeline p4sync Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 2016/Jul/26 7:24 PM Priority: Minor Reporter: Randy Simat You can currently set the LineEnd client option from a Freestyle Project or a Pipeline script from SCM but when you use the p4sync snippet there is no LineEnd option and it does not inherit this option from the job configuration. Add Comment This message was
