[JIRA] (JENKINS-62115) Review: support swarm's update url
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-62115 Review: support swarm's update url Change By: Joel Brown Labels: P4_VERIFY. 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.206026.1588203323000.19742.1588203420078%40Atlassian.JIRA.
[JIRA] (JENKINS-62115) Review: support swarm's update url
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-62115 Review: support swarm's update url Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-04-29 23:35 Priority: Minor Reporter: Joel Brown Latest Swarm suggests use of the update parameter in the review/build to show running and some (hopefully) meaningful message(s). The "update" (instead of pass and fail) also as formatted in JSON in the body of the POST request. Test status: valid test status values are running, pass, and fail. Messages: you can pass a maximum 10 messages, if you provide more than 10 messages only the first 10 are saved. See https://www.perforce.com/manuals/swarm/Content/Swarm/admin.integrate_test_suite.html?Highlight=update Add Comment
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Joel Brown edited a comment on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi [~fulingstar], do you have a stack trace in your *jenkins* log file ? Also, what's you your p4d/helix server exact version? 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.205886.1587487073000.15029.1587495120105%40Atlassian.JIRA.
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Joel Brown commented on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi ling fu, do you have a stack trace in your jenkins log file ? Also, what's you p4d/helix server exact version? 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.205886.1587487073000.15027.1587494760295%40Atlassian.JIRA.
[JIRA] (JENKINS-60832) Polling on matrix build always gives "P4: Polling error; no previous change.
Title: Message Title
Joel Brown commented on JENKINS-60832
Re: Polling on matrix build always gives "P4: Polling error; no previous change.
My Workspace name is jenkins-${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER} Axis is VARIANT with valueA, valueB Polling is for syncID of jenkins-master-MultiConfigProject-VARIANT-valueA-0 The last build.xml has syncID jenkins-NODE_NAME-MultiConfigProject-EXECUTOR_NUMBER
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.204183.1579654315000.3849.1579704840126%40Atlassian.JIRA.
[JIRA] (JENKINS-60832) Polling on matrix build always gives "P4: Polling error; no previous change.
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-60832 Polling on matrix build always gives "P4: Polling error; no previous change. Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2020-01-22 00:51 Labels: P4_VERIFY Priority: Major Reporter: Joel Brown Polling on a matrix build never builds: P4: Polling: No changes in previous build. P4: Polling error; no previous change. The syncID we search for is different that the syncID in previous runs' build.xml. p4-plugin 1.10.9 jenkins 2.150.3 Add Comment
[JIRA] (JENKINS-45794) Option to use "-I" (ignore p4ignore) on auto cleanup and sync
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-45794 Option to use "-I" (ignore p4ignore) on auto cleanup and sync Change By: Joel Brown Labels: P4_VERIFY 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.184003.1501025177000.757.1579220100330%40Atlassian.JIRA.
[JIRA] (JENKINS-60752) Print friendly message when View entered incorrectly
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-60752 Print friendly message when View entered incorrectly Change By: Joel Brown Labels: P4_VERIFY 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.204010.1578962417000.7761.1578964140083%40Atlassian.JIRA.
[JIRA] (JENKINS-60752) Print friendly message when View entered incorrectly
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-60752 Print friendly message when View entered incorrectly Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-01-14 00:40 Priority: Trivial Reporter: Joel Brown When a view is created, look for common mistakes and print something to the console log that there may be a problem. Still keeping running – just print an info message. When the (incorrect) client gets used, the failure message logged doesn't offer any guidance as to what might be wrong. Things to look for: spaces in path that aren'ts. For example, there are three spaces in one view mapping line but not any quotes. left side ends with "..." but right side doesn't. And vice versa. Add Comment
[JIRA] (JENKINS-60512) ssl connection error on el8 during p4sync
Title: Message Title Joel Brown edited a comment on JENKINS-60512 Re: ssl connection error on el8 during p4sync You can force the p4 plugin (i.e., P4Java) connection to use a higher TLS version by starting your JVM (master and slaves) with-DsecureSocketEnabledProtocols=TLSv1.2 Edit: for that to work to need later versions of p4d server. I know the latest 18.2, 19.1, and 19.2 patch releases work. A bit more info here: [https://community.perforce.com/s/article/2620] 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.203604.157654269.9505.1576556460161%40Atlassian.JIRA.
[JIRA] (JENKINS-60512) ssl connection error on el8 during p4sync
Title: Message Title Joel Brown commented on JENKINS-60512 Re: ssl connection error on el8 during p4sync You can force the p4 plugin (i.e., P4Java) connection to use a higher TLS version by starting your JVM (master and slaves) with -DsecureSocketEnabledProtocols=TLSv1.2 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.203604.157654269.9503.1576555920312%40Atlassian.JIRA.
[JIRA] (JENKINS-60370) Pin build at timestamp
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-60370 Pin build at timestamp Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-12-04 18:29 Labels: P4_VERIFY Priority: Minor Reporter: Joel Brown Request the ability to pin a build to a timestamp or date. Current capability is to build at a change or label. Workaround: changes are sequentially ordered by submit datetime, so you could figure out the change that represents the desired datetime. Add Comment
[JIRA] (JENKINS-59977) P4 Plugin creates invalid AppleDouble files
Title: Message Title Joel Brown commented on JENKINS-59977 Re: P4 Plugin creates invalid AppleDouble files This is a P4Java bug and has been reproduced. Perforce internal job number is job100626. 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.202781.1572367041000.2790.1574101800171%40Atlassian.JIRA.
[JIRA] (JENKINS-59977) P4 Plugin creates invalid AppleDouble files
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-59977 P4 Plugin creates invalid AppleDouble files Change By: Joel Brown Labels: P4_VERIFY 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.202781.1572367041000.2786.1574101680264%40Atlassian.JIRA.
[JIRA] (JENKINS-51432) Add multibranch support for task streams
Title: Message Title Joel Brown commented on JENKINS-51432 Re: Add multibranch support for task streams I don't see the workaround mentioned here, so: submit a new revision of the jenkinsfile to the task stream (no changes needed). This will "promote" the revision to public storage from the task's stream private storage. Your task stream should then be detected. 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.190786.1526675772000.9525.1572977520664%40Atlassian.JIRA.
[JIRA] (JENKINS-59795) Option to skip any builds after indexing multibranch pipeline.
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-59795 Option to skip any builds after indexing multibranch pipeline. Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-10-15 21:08 Priority: Major Reporter: Joel Brown Using a multibranch pipeline, we want the scan to pick up new branches BUT to skip the check for changes and the possible build. The jobs are user initiated only. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-59207) READONLY autoclean sync fails on reconcile
Title: Message Title Joel Brown commented on JENKINS-59207 Re: READONLY autoclean sync fails on reconcile The fact the reconcile failure was ignored in an earlier release is a bug - the error should have been surfaced. IMO, we fixed it the change you noted. auto cleanup and sync should run "reconcile -w -f" to make the workspace consistent with the last sync. 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.201657.1567534561000.5761.1568767980283%40Atlassian.JIRA.
[JIRA] (JENKINS-59132) Perforce Workspace spec file root skipped
Title: Message Title
Joel Brown commented on JENKINS-59132
Re: Perforce Workspace spec file root skipped
Check out jenkins.model.Jenkins.workspacesDir - e.g., start your jenkins (including slaves) with -Djenkins.model.Jenkins.workspacesDir=d:\${ITEM_FULL_NAME} Note the comments for this property: https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties If you do a plain "d:\" then make sure all the workspace View field, right-hand sides, don't overlap. Otherwise you can use a Perforce form-in client trigger to alter the root. Just make sure you only change the root for jenkins clients.
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.201564.1567024301000.2377.1567037640161%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-58745 P4Groovy p4.run() does not locate credentials in folder Change By: Joel Brown Issue Type: Improvement Bug 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.201048.156461302.5154.1566181080292%40Atlassian.JIRA.
[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch
Title: Message Title Joel Brown commented on JENKINS-58820 Re: scan Multibranch pipeline does not detect new streams when file is branch Eric Daigneault if your "p4 -ztag info" shows support you can email supp...@perforce.com (please provide the p4 info). Please mention me. 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.201132.1565041263000.1476.1565653140190%40Atlassian.JIRA.
[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch
Title: Message Title Joel Brown closed an issue as Duplicate Jenkins / JENKINS-58820 scan Multibranch pipeline does not detect new streams when file is branch Change By: Joel Brown Status: Open Closed Resolution: Duplicate 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.201132.1565041263000.188.1565393460371%40Atlassian.JIRA.
[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch
Title: Message Title Joel Brown edited a comment on JENKINS-58820 Re: scan Multibranch pipeline does not detect new streams when file is branch [~newtopian] What type of Stream is this undetected stream? Development? Release? Task? I can reproduce this with a Task stream. Please confirm you have the problem with Task Streams - or other. 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.201132.1565041263000.179.1565390520160%40Atlassian.JIRA.
[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch
Title: Message Title Joel Brown commented on JENKINS-58820 Re: scan Multibranch pipeline does not detect new streams when file is branch Eric Daigneault What type of Stream is this undetected stream? Development? Release? Task? 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.201132.1565041263000.177.1565389620111%40Atlassian.JIRA.
[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch
Title: Message Title Joel Brown assigned an issue to Joel Brown Jenkins / JENKINS-58820 scan Multibranch pipeline does not detect new streams when file is branch Change By: Joel Brown Assignee: Joel Brown 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.201132.1565041263000.129.1565385780140%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title Joel Brown assigned an issue to Joel Brown Jenkins / JENKINS-58745 P4Groovy p4.run() does not locate credentials in folder Change By: Joel Brown Assignee: Joel Brown 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.201048.156461302.11037.1565302560413%40Atlassian.JIRA.
[JIRA] (JENKINS-58820) scan Multibranch pipeline does not detect new streams when file is branch
Title: Message Title Joel Brown commented on JENKINS-58820 Re: scan Multibranch pipeline does not detect new streams when file is branch Hi Eric Daigneault - does your company have a Perforce License? If so, I'd prefer to work with you through our Salesforce on the issue. And then update this with any conclusion. 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.201132.1565041263000.10908.1565289720322%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title
Joel Brown updated an issue
Jenkins / JENKINS-58745
P4Groovy p4.run() does not locate credentials in folder
Change By:
Joel Brown
When credentials to use are in a folder, using them in a script with p4.run() will not find the credential.Repro:create a folder.within the folder, create a credential and a pipleline job.The job's script references the credential in the folder.{ \ { script{}} \ {{ def ws = [$class: 'ManualWorkspaceImpl', name: "jenkins-${NODE_NAME}-${JOB_NAME}", }}{{ spec: [view: "//depot/main/utilities/AppUtilities/src/... //jenkins-${NODE_NAME}-${JOB_NAME}/..."]]}} \ {{ def p4 = p4(credential: 'build-u18-20182', workspace: ws)}} \ {{ def output = p4.run('sync')}} \ {{ }}} A p4sync step using the same credential succeeds. console log:[Pipeline] Start of Pipeline[Pipeline] nodeRunning on [Jenkins|http://jbrown-swarmu18.das.perforce.com:8080/computer/(master)/] in /var/lib/jenkins/jobs/pipelines/jobs/simple sync/workspace[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] p4[Pipeline] } [Pipeline] // script[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4: Task Exception: Invalid credentialsFinished: FAILURE
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
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title
Joel Brown created an issue
Jenkins / JENKINS-58745
P4Groovy p4.run() does not locate credentials in folder
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-07-31 22:43
Labels:
P4_VERIFY
Priority:
Major
Reporter:
Joel Brown
When credentials to use are in a folder, using them in a script with p4.run() will not find the credential. Repro: create a folder. within the folder, create a credential and a pipleline job. The job's script references the credential in the folder. {{ script{}} {{ def ws = [$class: 'ManualWorkspaceImpl', name: "jenkins-${NODE_NAME}-${JOB_NAME}", }} {{ spec: [view: "//depot/main/utilities/AppUtilities/src/... //jenkins-${NODE_NAME}-${JOB_NAME}/..."]]}} {{ def p4 = p4(credential: 'build-u18-20182', workspace: ws)}} {{ def output = p4.run('sync')}} {{ }}} console log: [Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/jobs/pipelines/jobs/simple sync/workspace[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] p4[Pipeline] } [Pipeline] // script[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4: Task Exception: Invalid credentials Finished: FAILURE
[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors
Title: Message Title
Joel Brown edited a comment on JENKINS-58119
Re: Cant run P4Groovy sync on multiple executors
Workaround should be to start all nodes running concurrent builds to not use "@": start jvm with {{"-Dhudson.slaves.WorkspaceList=_"}}
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.200164.1561045657000.7567.1561395120087%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58119) Cant run P4Groovy sync on multiple executors
Title: Message Title Joel Brown commented on JENKINS-58119 Re: Cant run P4Groovy sync on multiple executors Workaround should be to start all nodes running concurrent builds to not use "@": "-Dhudson.slaves.WorkspaceList=_" 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.200164.1561045657000.7565.1561395000117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Joel Brown commented on JENKINS-57156 Re: p4 plugin : Invalid credentials The default location for the tickets file is $user.home/.p4tickets. Check the Manage Jenkins -> System Information for "user.dir". Is it /home/jenkins? To change, ask your IT to change OS user jenkins home dir to be /var/lib/jenkins. Or you can alter your jenkins startup to change it, set jvm option -Duser.home=/var/lib/jenkins and make sure the jenkins process OS user (typically 'jenkins') can r/w file in that dir. Or you also can point to a file, start jvm with -DticketPath=/some/path/to/p4tickets.txt (same r/w requirement) Where you set these java system props depends on your jenkins seutp. For example, add the -D to /etc/default/jenkins within JAVA_ARGS. Restart jenkins to pick it up. 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-56471) Construct view using full path even when only one depot path is given
Title: Message Title
Joel Brown updated an issue
Jenkins / JENKINS-56471
Construct view using full path even when only one depot path is given
Change By:
Joel Brown
When your pipeline has a single filespec in the depotSource like this p4sync charset: 'none', source: depotSource('// Depot depot / Branch branch /...') Then the generated client view is //depot/branch/... // P4CLIENT P4_CLIENT /... This is request for that client view to be like it would be if you had two or more filespecs://depot/branch/... // P4CLIENT P4_CLIENT /depot/branch/... Use case: all existing "make" files assume a branch name in the path.Workaround:add a second depotPath to the list - e.g., source: depotSource('//depot/branch/...' '//depot/not/there') Code:In org.jenkinsci.plugins.p4.client.ViewMapHelper.java, allow an option to make multi = true regardless of views.size().
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-56471) Construct view using full path even when only one depot path is given
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-56471 Construct view using full path even when only one depot path is given Change By: Joel Brown Labels: 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-56471) Construct view using full path even when only one depot path is given
Title: Message Title
Joel Brown created an issue
Jenkins / JENKINS-56471
Construct view using full path even when only one depot path is given
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-03-08 01:08
Priority:
Minor
Reporter:
Joel Brown
When your pipeline has a single filespec in the depotSource like this p4sync charset: 'none', source: depotSource('//Depot/Branch/...') Then the generated client view is //depot/branch/... //P4CLIENT/... This is request for that client view to be like it would be if you had two or more filespecs: //depot/branch/... //P4CLIENT/depot/branch/... Code: In org.jenkinsci.plugins.p4.client.ViewMapHelper.java, allow an option to make multi = true regardless of views.size().
Add Comment
