[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Paul Allen commented on JENKINS-61745 Re: Scan multibranch with date range or dop '@now' Latest build: https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/446/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205574.1585583601000.4081.1585737120235%40Atlassian.JIRA.
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Paul Allen commented on JENKINS-61745 Re: Scan multibranch with date range or dop '@now' Added fix: https://github.com/jenkinsci/p4-plugin/commit/62c83c4368a10a2538a04f1988ae59c9c00d11cc Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205574.1585583601000.4079.1585736400123%40Atlassian.JIRA.
[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'
Title: Message Title Paul Allen commented on JENKINS-61745 Re: Scan multibranch with date range or dop '@now' I doubt the p4d is scanning the wrong way (the -m1 flag should be minimal load). The Build user should not have MaxResults set; perhaps MaxLockTime would be more appropriate or run off a replica to minimise load. Notes: Possibly apply ConnectionHelper::getHeadLimit() to AbstractP4ScmSource::findLatestChange(...) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205574.1585583601000.3454.1585642200133%40Atlassian.JIRA.
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Paul Allen edited a comment on JENKINS-58249 Re: Perforce plugin: JCasC cannot export configuration Sorry for not looking at this sooner. As suggested I have added a getSsl() method into the Perforce Base Credentials. I have manually tested this against the configuration-as-code plugin with a Perforce SSL connection and it looks good to me.Please let me know if you are able to verify this fix and confirm there are no side effects when using SSL enabled Perforce Servers. [https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/434/] 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.200312.1561709954000.684.1581947160229%40Atlassian.JIRA.
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Paul Allen commented on JENKINS-58249 Re: Perforce plugin: JCasC cannot export configuration Sorry for not looking at this sooner. As suggested I have added a getSsl() method into the Perforce Base Credentials. I have manually tested this against the configuration-as-code plugin with a Perforce SSL connection and it looks good to me. Please let me know if you are able to verify this fix and confirm there are no side effects when using SSL enabled Perforce Servers. 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.200312.1561709954000.653.1581941580207%40Atlassian.JIRA.
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Paul Allen commented on JENKINS-58949 Re: If job fails in cleanup further triggering fails The P4 Trigger is a top level endpoint in Jenkins and wakes up all Subscribed Jenkins jobs, checks for changes then scheduled a build. If the previous run failed or was aborted then no changes are recorded so further polling or in this case triggers will fail. A 'Build Now' would correct the state and all would be back to normal. Ideally we could carry the previous built changes forward, or change the logic to search the previous builds. Perhaps recording the 'head' change would be enough for failed/aborted builds, but that might not be ideal in all circumstances. 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.201296.1565876577000.9731.1576584480575%40Atlassian.JIRA.
[JIRA] (JENKINS-39287) Ability to select from existing credentials list at runtime
Title: Message Title
Paul Allen commented on JENKINS-39287
Re: Ability to select from existing credentials list at runtime
There is no benefit for implicit checkout; however if you set `options { skipDefaultCheckout() }` then for subsequent checkout steps you could change the credential. You would need your own logic to look up the credential or specify them with the agent/label.
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.175718.1477521864000.1654.1575560640417%40Atlassian.JIRA.
[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project
Title: Message Title Paul Allen closed an issue as Fixed Closing. Plugin cannot read invalid pipeline script. Jenkins / JENKINS-55214 NullPointerException when starting a pipeline in a multibranch project Change By: Paul Allen Status: Open Closed Resolution: Fixed 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
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-55985 Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Change By: Paul Allen Priority: Blocker Minor 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.197398.1549406943000.1643.1575559500638%40Atlassian.JIRA.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-55985 Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Change By: Paul Allen Priority: Minor Major 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.197398.1549406943000.1645.1575559500673%40Atlassian.JIRA.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Paul Allen commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) TODO: retest this issue after updating plugin dependencies. 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.197815.1550844551000.1633.1575559080449%40Atlassian.JIRA.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Paul Allen Priority: Blocker Major 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.197815.1550844551000.1623.1575559020719%40Atlassian.JIRA.
[JIRA] (JENKINS-56286) Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-56286 Multibranch Pipeline + P4Plugin + Helix Library + Polling = Infinite Build Loop Change By: Paul Allen Priority: Blocker Major 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.197865.1551180689000.1617.1575558840489%40Atlassian.JIRA.
[JIRA] (JENKINS-56290) Impossible to Add Streams with Exact Names to Multibranch Pipeline
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-56290 Impossible to Add Streams with Exact Names to Multibranch Pipeline Change By: Paul Allen Priority: Blocker Major 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.197869.155119216.1609.1575558720554%40Atlassian.JIRA.
[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58119 Cant run P4Groovy sync on multiple executors Change By: Paul Allen Priority: Blocker Major 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.200164.1561045657000.1600.1575558300572%40Atlassian.JIRA.
[JIRA] (JENKINS-58196) UTF8 BOM override issue in 1.10.0
Title: Message Title Paul Allen assigned an issue to Karl Wirth Jenkins / JENKINS-58196 UTF8 BOM override issue in 1.10.0 Change By: Paul Allen Assignee: Karl Wirth 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.200252.1561501047000.1596.1575558180351%40Atlassian.JIRA.
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58949 If job fails in cleanup further triggering fails Change By: Paul Allen Priority: Blocker Minor 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.201296.1565876577000.1592.1575558060289%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Paul Allen commented on JENKINS-60321 Re: Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams Notes (to avoid exception and ignore Multibranch with defaults): - In AbstractP4ScmSource method getLastScan() check instance of branchProject.getProjectFactory() - In AbstractP4ScmSource method retrieve() null check revision and continue loop to next P4SCMHead 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.203319.157495971.9308.1575024721152%40Atlassian.JIRA.
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title Paul Allen commented on JENKINS-60220 Re: Multibranch pipeline with Helix Swarm source doesn't sync to latest Hi Guys, just back from vacation so may need a bit of time to get up speed on this issue... Using 'head' (the latest change on that branch) might be an alternative, but there could be side effects if the 'head' is newer than the shelf/review. The P4 plugin may need to perform a resolve step (forcing the accept of the shelve's content) - I seem to remember writing something like this, but can't remember if it was released or in a dev branch. I'll take a look and refresh myself on the Swarm review part of the code. 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.203193.1574213884000.6377.1574701020205%40Atlassian.JIRA.
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title Paul Allen commented on JENKINS-60074 Re: Empty array returned with p4sync after 1.10.6 Passes internal tests - pushed to master It may fail CI builds as Jenkins infra has been a bit sensitive lately. https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/409/ 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.202910.1573035013000.11225.1573223100170%40Atlassian.JIRA.
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title Paul Allen started work on JENKINS-60074 Change By: Paul Allen Status: Open In Progress 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.202910.1573035013000.11220.1573222980448%40Atlassian.JIRA.
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title Paul Allen updated JENKINS-60074 Jenkins / JENKINS-60074 Empty array returned with p4sync after 1.10.6 Change By: Paul Allen Status: In Progress Review 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.202910.1573035013000.11222.1573222980478%40Atlassian.JIRA.
[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Issue resolved. Jenkins / JENKINS-60041 P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Change By: Paul Allen Status: Open Closed Assignee: Paul Allen Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received
[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Title: Message Title Paul Allen commented on JENKINS-60041 Re: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US The error suggests that Identifier.properties is not in your class path; I can verity that we ship the properties file in the p4.hpi file. unzip p4.hpi cd WEB-INF/lib/ unzip p4.jar ls org/jenkinsci/plugins/p4/Identifier.properties From the log is seems that the issue occurs on a Windows slave 'buildvpc10' perhaps the slave.jar is old? or a localisation setting has changed the class path? Please can you verify this by running the job on the master or a different slave. Perhaps redeploying the Jenkins slave may solve the issue? 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.202869.1572884428000.9170.1572948900218%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title Paul Allen updated JENKINS-52806 Released in 1.10.6 Jenkins / JENKINS-52806 Pipeline: Parallel syncs don't set environment variables properly. Change By: Paul Allen Status: In Review Closed Resolution: Fixed 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
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.6 Jenkins / JENKINS-59213 P4 Plugin - Errors when syncing symlinks Change By: Paul Allen Status: In Progress Closed Resolution: Fixed 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
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.6 Jenkins / JENKINS-59611 Symlink target update fails when "noclobber" set Change By: Paul Allen Status: In Progress Closed Resolution: Fixed 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
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Paul Allen updated JENKINS-56037 Jenkins / JENKINS-56037 SCM Polling with p4-plugin triggers builds several times Change By: Paul Allen Status: In Review Closed Resolution: Fixed 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.197457.1549569383000.7861.1571143740845%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen started work on JENKINS-59213 Change By: Paul Allen Status: Open In Progress 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.201664.156755142.7746.1571135460672%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-59213 P4 Plugin - Errors when syncing symlinks Change By: Paul Allen Labels: P4_SUPPORT P4_VERIFY p4-plugin symlink 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.201664.156755142.7743.1571135460563%40Atlassian.JIRA.
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-59611 Symlink target update fails when "noclobber" set Change By: Paul Allen Assignee: Charusheela Bopardikar 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.202252.1569940696000.7735.1571135402111%40Atlassian.JIRA.
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-59213 P4 Plugin - Errors when syncing symlinks Change By: Paul Allen Assignee: Karl Wirth Charusheela Bopardikar 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.201664.156755142.7739.1571135403556%40Atlassian.JIRA.
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title Paul Allen started work on JENKINS-59611 Change By: Paul Allen Status: Open In Progress 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.202252.1569940696000.7732.1571135340687%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title Paul Allen updated JENKINS-52806 Jenkins / JENKINS-52806 Pipeline: Parallel syncs don't set environment variables properly. Change By: Paul Allen Status: In Progress Review 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.192727.153298856.7542.1571128020550%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title Paul Allen commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. Hi guys, I have merged the original pull request and added a test case to test parallel stages. 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.192727.153298856.7087.1571065380227%40Atlassian.JIRA.
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Paul Allen updated JENKINS-56037 Jenkins / JENKINS-56037 SCM Polling with p4-plugin triggers builds several times Change By: Paul Allen Status: In Progress Review 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.197457.1549569383000.4898.1570714501735%40Atlassian.JIRA.
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Paul Allen commented on JENKINS-56037 Re: SCM Polling with p4-plugin triggers builds several times Karl Wirth - I think this issue is now fixed in release 1.10.5 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.197457.1549569383000.4890.1570714442659%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.5 Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Status: In Progress Closed Resolution: Fixed 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
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Labels: P4_VERIFY P4_A 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.200807.156396953.571.1570110300279%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen started work on JENKINS-58639 Change By: Paul Allen Status: Open In Progress 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.200807.156396953.567.1570110240557%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Assignee: Charusheela Bopardikar 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.200807.156396953.564.1570110240469%40Atlassian.JIRA.
[JIRA] (JENKINS-56501) Filter on p4-publish when using streams
Title: Message Title Paul Allen updated JENKINS-56501 Released in 1.10.4 Jenkins / JENKINS-56501 Filter on p4-publish when using streams Change By: Paul Allen Status: Fixed but Unreleased Closed 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.198108.1552306897000.9751.1570028041861%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen updated JENKINS-58149 Released in 1.10.4 Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Paul Allen Status: Fixed but Unreleased Closed 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.200194.1561145922000.9757.1570028042900%40Atlassian.JIRA.
[JIRA] (JENKINS-58686) Syncing to revision 0 runs an invalid command
Title: Message Title Paul Allen updated JENKINS-58686 Released in 1.10.4 Jenkins / JENKINS-58686 Syncing to revision 0 runs an invalid command Change By: Paul Allen Status: Fixed but Unreleased Closed 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.200969.1564174442000.9749.1570028041409%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title Paul Allen updated JENKINS-58745 Released in 1.10.4 Jenkins / JENKINS-58745 P4Groovy p4.run() does not locate credentials in folder Change By: Paul Allen Status: Fixed but Unreleased Closed 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.201048.156461302.9753.1570028042300%40Atlassian.JIRA.
[JIRA] (JENKINS-59526) Clearly document automatic vs static label usage
Title: Message Title Paul Allen closed an issue as Fixed Static labels can be used, but with polling restrictions. Doc not required. Jenkins / JENKINS-59526 Clearly document automatic vs static label usage Change By: Paul Allen Status: Open Closed Resolution: Fixed 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
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Paul Allen closed an issue as Fixed Jenkins / JENKINS-57870 Request too large for server memory since 10.1.0 Change By: Paul Allen Status: Resolved Closed 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.199833.1559782353000.9615.1570015380346%40Atlassian.JIRA.
[JIRA] (JENKINS-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Paul Allen started work on JENKINS-39107 Change By: Paul Allen Status: Reopened In Progress 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.175527.1476879748000.9610.1570015140453%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Paul Allen Comment: Ready for release. 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.200194.1561145922000.9115.1569947040690%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen updated JENKINS-58149 Ready for release. Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Paul Allen Status: Reopened Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly Ready for release. 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.200194.1561145922000.9105.1569946920171%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly I'll look into the polling logic and see if it can manage static labels. Polling will need to poll against the old label name (e.g. static1), so changes will only get found if a new label (e.g. static2) is used and has newer revisions. Updating the original label (e.g. static1) would have no effect as the comparison is using the label's name and not its content. 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.200194.1561145922000.8819.1569931500195%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title
Paul Allen edited a comment on JENKINS-58149
Re: p4-plugin 1.10.0 does not sync to label correctly
Verified (master codeline) Static labels can be used to sync source:{code:java}P4 : Warning label is static and cannot be used with polling!... p4 counter static1 +P4: builds: static1 ###P4 Task: syncing files at client/label: static1p4 sync -q /var/ xxx ### /workspace/staticLabelSync/...@static1{code}
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.200194.1561145922000.8594.1569926640159%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen reopened an issue Verified Static labels can be used to sync source: P4 Task: syncing files at client/label: static1 p4 sync -q /var/xxx/workspace/staticLabelSync/...@static1 Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Paul Allen Resolution: Won't Fix Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title Paul Allen started work on JENKINS-58745 Change By: Paul Allen Status: Open In Progress 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.201048.156461302.7749.1569841500757%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title Paul Allen updated JENKINS-58745 Ready for release. Jenkins / JENKINS-58745 P4Groovy p4.run() does not locate credentials in folder Change By: Paul Allen Status: In Progress Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-56501) Filter on p4-publish when using streams
Title: Message Title Paul Allen updated JENKINS-56501 Ready for release. Jenkins / JENKINS-56501 Filter on p4-publish when using streams Change By: Paul Allen Status: In Progress Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen closed an issue as Won't Fix Jenkins / JENKINS-58149 p4-plugin 1.10.0 does not sync to label correctly Change By: Paul Allen Status: Open Closed Resolution: Won't Fix 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.200194.1561145922000.5946.1569501360486%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Paul Allen commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly `P4: Warning label is static and cannot be used with polling!` Static labels are not supported as they may represent more than one changelist number. Please use an automatic label. 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.200194.1561145922000.5944.1569501360465%40Atlassian.JIRA.
[JIRA] (JENKINS-58968) Publish improvements
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58968 Publish improvements Change By: Paul Allen Epic 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.201315.1565967714000.4173.1568631360262%40Atlassian.JIRA.
[JIRA] (JENKINS-56501) Filter on p4-publish when using streams
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-56501 Filter on p4-publish when using streams Change By: Paul Allen Assignee: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198108.1552306897000.6402.1567593420121%40Atlassian.JIRA.
[JIRA] (JENKINS-56501) Filter on p4-publish when using streams
Title: Message Title Paul Allen started work on JENKINS-56501 Change By: Paul Allen Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198108.1552306897000.6400.1567593360191%40Atlassian.JIRA.
[JIRA] (JENKINS-59221) Filter on Populate when using streams
Title: Message Title Paul Allen created an issue Jenkins / JENKINS-59221 Filter on Populate when using streams Issue Type: Task Assignee: Paul Allen Components: p4-plugin Created: 2019-09-04 10:34 Priority: Minor Reporter: Paul Allen Similar to JENKINS-56501. Provide a list of depot or local paths that are passed to the sync command, so the whole workspace is not synced. Auto Cleanup? whole workspace or just the paths HaveList? whole workspace or just the paths Add Comment
[JIRA] (JENKINS-59213) P4 Plugin - Errors when syncing symlinks
Title: Message Title Paul Allen commented on JENKINS-59213 Re: P4 Plugin - Errors when syncing symlinks It's possible that the older 1.10.0 release may have left a 'bad' symlink in your workspace with strange permissions. You may need to use 'administrator' permissions to clean up the file. Windows has a few types of symlinks; the plugin only supports 'symlinks' not 'junctions' JENKINS-57955. If it still causes a problem please let me know. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201664.156755142.6394.1567593060386%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen closed an issue as Won't Fix Closing - will not support 'junctions'. Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Status: Reopened Closed Resolution: Won't Fix 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.6329.1567585981923%40Atlassian.JIRA.
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title Paul Allen commented on JENKINS-40292 Re: More Control of p4 task logging The TaskListener does not have levels, I could extended it to use java.util.logging.Level (all levels are cumulative and include the level above): Would the following break down work? SEVERE Fatal errors that will cause the build to Abort WARNING Warnings INFO (default level) Intermediate steps (like file cleanup, populate) and just the p4 command CONFIG (not used) FINE p4 command details and output FINER (not used) FINEST (not used) Configuring this can be done Globally, per Job, or possibly per Credential. I'm thinking for large Jenkins deployments if one user is investigating a job he might upset other teams if the setting is global. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title Paul Allen commented on JENKINS-40292 Re: More Control of p4 task logging Hi Guys, there are at least two main types of logging in Jenkins the TaskListener the main discussion here and the System Log (java.util.logging). Over the years I have made improvements to both, but with change in the GUI (Blue Ocean) some of the collapsable html blocks in TaskListener are somewhat redundant. Logging with TaskListener occurs in many places; the most common are ConnectionHelper, ClientHelper, Tasks (AbstractTask) and the Perforce commands in P4Logging. A Global option to enable/disable logging details may be the simplest; is there a need to set this per job or per connection? I can see that per job might be preferable. The next question would be to determine how many levels and what would be visible for each: sub steps (e.g. updating client, removing file, reconcile files, syncing file) the actual p4 commands detailed output for commands (files being reconciled, full client workspace view mappings) execution time (for a sub step, or even a command) Lots to think about? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176946.1481141079000.7734.1566468180357%40Atlassian.JIRA.
[JIRA] (JENKINS-58968) Publish improvements
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58968 Publish improvements Change By: Paul Allen Epic Color: ghx-label- 1 6 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201315.1565967714000.4145.1565967780067%40Atlassian.JIRA.
[JIRA] (JENKINS-58968) Publish improvements
Title: Message Title Paul Allen created an issue Jenkins / JENKINS-58968 Publish improvements Issue Type: Epic Assignee: Unassigned Components: p4-plugin Created: 2019-08-16 15:01 Priority: Minor Reporter: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201315.1565967714000.4144.1565967720192%40Atlassian.JIRA.
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58249 Perforce plugin: JCasC cannot export configuration Change By: Paul Allen Labels: P4_A jcasc-compatibility 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200312.1561709954000.4143.1565967600198%40Atlassian.JIRA.
[JIRA] (JENKINS-58698) Perforce sync fails for symlinks
Title: Message Title Paul Allen closed an issue as Fixed Resolved in 1.10.2 Jenkins / JENKINS-58698 Perforce sync fails for symlinks Change By: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200987.156437800.4138.1565967480390%40Atlassian.JIRA.
[JIRA] (JENKINS-45465) Performance work on Sync/Populate options
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-45465 Performance work on Sync/Populate options Change By: Paul Allen Epic Status: To Do Done 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183635.1499850918000.4135.1565967360235%40Atlassian.JIRA.
[JIRA] (JENKINS-47191) Custom review and global parameters
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-47191 Custom review and global parameters Change By: Paul Allen Epic Status: To Do Done 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185598.1506592349000.4136.1565967360250%40Atlassian.JIRA.
[JIRA] (JENKINS-45464) MultiBranch support for Graph depots
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-45464 MultiBranch support for Graph depots Change By: Paul Allen Epic Status: To Do Done 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183634.1499850708000.4134.1565967360221%40Atlassian.JIRA.
[JIRA] (JENKINS-49731) p4-plugin viewFilter unusable
Title: Message Title Paul Allen closed an issue as Fixed Jenkins / JENKINS-49731 p4-plugin viewFilter unusable Change By: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188673.1519574557000.4126.1565967060391%40Atlassian.JIRA.
[JIRA] (JENKINS-49731) p4-plugin viewFilter unusable
Title: Message Title
Paul Allen commented on JENKINS-49731
Re: p4-plugin viewFilter unusable
Sorry for the delay (over a year). It's not possible for two implementations to have the same symbol. I can't remember why, but one of them got renamed. The DataBoundConstructor for viewFilter only takes one argument and it's possible that the older implementation got changed. FilterViewMaskImpl uses @Symbol("viewFilter") FilterPatternListImpl uses @Symbol("viewPattern")
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188673.1519574557000.4124.1565967000186%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen commented on JENKINS-57955 Re: Clean and sync incorrectly follows junction/directory symlinks on Windows P4Java's reconcile supports 'symlinks' not 'junctions'. Please use: mklink /D "%WORKSPACE%\3rdparty" "C:\Jenkins\3rdparty" 'D' for a Directory Symlink. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4639.1564589880279%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen reopened an issue Possible issue when cleaning up symbolic links on Windows. Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Resolution: Fixed Status: Closed Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4627.1564587300383%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen assigned an issue to Matthew Smeeth Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Assignee: Paul Allen Matthew Smeeth 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4623.1564587120324%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Assignee: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4620.1564587120259%40Atlassian.JIRA.
[JIRA] (JENKINS-58116) "Request too large" in p4-plugin 1.10 (works with 1.9.7)
Title: Message Title Paul Allen commented on JENKINS-58116 Re: "Request too large" in p4-plugin 1.10 (works with 1.9.7) Released in 1.10.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200161.1561031961000.18985.1563892081357%40Atlassian.JIRA.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Paul Allen commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 Released in 1.10.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.18979.1563892020293%40Atlassian.JIRA.
[JIRA] (JENKINS-58504) P4 Plugin tries to make depot location of Jenkinsfile available regardless of SCM type
Title: Message Title Paul Allen updated JENKINS-58504 Released in 1.10.3 Jenkins / JENKINS-58504 P4 Plugin tries to make depot location of Jenkinsfile available regardless of SCM type Change By: Paul Allen Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200647.1563234801000.18976.1563891960323%40Atlassian.JIRA.
[JIRA] (JENKINS-57945) p4 sync corrupts symlinks
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.2 Jenkins / JENKINS-57945 p4 sync corrupts symlinks Change By: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199921.1560203497000.10642.1563186362013%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.2 Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.10645.1563186362102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58048) P4 error - No open file stream in ClientSystemFileCommands.writeFile()
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.2 Jenkins / JENKINS-58048 P4 error - No open file stream in ClientSystemFileCommands.writeFile() Change By: Paul Allen Status: Resolved Closed Assignee: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200069.1560779623000.10631.1563186301540%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58109) Perforce ditto mappings from clientspec do not work
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.1 Jenkins / JENKINS-58109 Perforce ditto mappings from clientspec do not work Change By: Paul Allen Status: Open Closed Assignee: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200152.1561000701000.10613.1563186240922%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Paul Allen commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 For reference: The code to query the change was added to deal with issue JENKINS-57534 https://github.com/jenkinsci/p4-plugin/commit/c1ed873be0d988d12619b1072bb41a0580aa3bd2 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.11717.1561734420178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-58249 Perforce plugin: JCasC cannot export configuration Change By: Paul Allen Assignee: Paul Allen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200312.1561709954000.11714.1561733820101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58116) "Request too large" in p4-plugin 1.10 (works with 1.9.7)
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58116 "Request too large" in p4-plugin 1.10 (works with 1.9.7) Change By: Paul Allen Labels: P4_SUPPORT 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200161.1561031961000.4613.1561038420493%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58109) Perforce ditto mappings from clientspec do not work
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-58109 Perforce ditto mappings from clientspec do not work Change By: Paul Allen Labels: P4_B 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200152.1561000701000.4598.1561038300443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57901) Concurrent Pipeline builds report all changes since last completed build
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-57901 Concurrent Pipeline builds report all changes since last completed build Change By: Paul Allen Labels: P4_B 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199866.1559866894000.4571.1561037760403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Labels: P4_B P4_A 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.25960.1560348780217%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) populate: previewOnly(quiet: true) fail
Title: Message Title Paul Allen commented on JENKINS-57870 Re: populate: previewOnly(quiet: true) fail Please can you also include the client view mappings when reporting to support. (Exclusionary mappings could be very expensive.) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.22573.1559815200540%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57870) populate: previewOnly(quiet: true) fail
Title: Message Title
Paul Allen commented on JENKINS-57870
Re: populate: previewOnly(quiet: true) fail
If you are using PreviewOnly with the quiet option set then the sync operation is skipped and you should see "P4 Task: skipping sync." in the log. (since version 1.9.5)
// Skip `p4 sync -q -n` to save compute time.
if (populate.isQuiet()) {
log("P4 Task: skipping sync.");
return;
}
Jenkins still needs to know what changes are associated with the build; this is for reporting, but also for polling calculations.
p4 changes -m1 -ssubmitted //CLIENT_SPEC/...@
Should not cause the server to report 'Request too large for server memory (try later?)'. Please work with our support team to get a copy of the Server log.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.22563.1559814660175%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen assigned an issue to Kevin Williamson Jenkins / JENKINS-52679 p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs Change By: Paul Allen Assignee: Paul Allen Kevin Williamson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21980.1559745060196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen updated JENKINS-52679 Ready for release. Jenkins / JENKINS-52679 p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs Change By: Paul Allen Status: In Progress Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21975.1559745000415%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen started work on JENKINS-52679 Change By: Paul Allen Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21906.1559741640228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen commented on JENKINS-52679 Re: p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs Requires: DOC example and raise warning messages from 'execmap: client -i' to the user. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21189.1559664301468%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title
Paul Allen commented on JENKINS-52679
Re: p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Ok this seems to work with a change view:
Client: ${P4_CLIENT}
Update: 2019/01/24 14:24:06
Access: 2019/06/04 16:25:24
Owner: pallen
Description:
Created by pallen.
Root: /Users/pallen/Perforce/1666/ws
Options: noallwrite noclobber nocompress unlocked nomodtime normdir
SubmitOptions: submitunchanged
LineEnd: local
View:
//depot/projA/... //${P4_CLIENT}/...
ChangeView:
//depot/projA/...@2239
log...
P4 Task: syncing files at change: 2239
... p4 sync -q /Users/pallen/Workspaces/main.p4-jenkins/public/work/workspace/ChangeViewFree/...@2239
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21186.1559664240124%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
