[JIRA] [p4] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Paul Allen commented on JENKINS-24070 Error: Wipe Out Workspace blocked by SCM Hi Grant, When you refer to the plugin "blocking requests to wipe out workspace" is this the 'Wipe Out Current Workspace' option under 'Workspace'? Have you tried the 'Forced clean and sync' option under the Populate options? I'll take a look into this and see what is going on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23974) Private maven repo got wipe out every build
Paul Allen updated JENKINS-23974 Private maven repo got wipe out every build Change By: Paul Allen (01/Aug/14 11:18 AM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync I setup a slave on Ubuntu and was not able to reproduce this issue. The string "3605760456" might refer to a serialisation issue, but I can't find anything odd in the code. Thanks for checking the logs; please can you check the Perforce Credential for the Server connection. Did you use an IP or FQDN? Can the slave resolve the Perforce Server? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync Before you try rolling back the plugin; have you tried a clean Jenkins Job. I'm thinking that the previous builds might not have full TagAction info and could cause a Null Pointer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Paul Allen commented on JENKINS-24070 Error: Wipe Out Workspace blocked by SCM Hi Grant, I pushed 1.0.9 out late friday; please check, but I think this should be fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Paul Allen resolved JENKINS-24070 as Fixed Error: Wipe Out Workspace blocked by SCM Change By: Paul Allen (04/Aug/14 9:34 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24003) Unable to wipe out workspace
Paul Allen closed JENKINS-24003 as Fixed Unable to wipe out workspace Fixed in 1.0.9 Duplicate JENKINS-24070 Change By: Paul Allen (04/Aug/14 9:33 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen commented on JENKINS-24101 Poll Watching Label Continually Triggering Think I have fixed this in change 9834. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23882) Long build startup
Paul Allen commented on JENKINS-23882 Long build startup I have reduced the number of connections to Perforce when starting up (Unicode checks and extra login checks). This should speed up build start time. There are additional limits on changes and files when populating the build history. Target release 1.0.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion
Paul Allen commented on JENKINS-24005 Pin build at Perforce Label does not support variable expansion Added support for label expansion in target 1.0.10 release. Tested OK with parameterized builds (NOTE: SCM Polling will not necessarily have access to these parameters). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion
Paul Allen closed JENKINS-24005 as Fixed Pin build at Perforce Label does not support variable expansion 1.0.10 Change By: Paul Allen (11/Aug/14 3:21 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23882) Long build startup
Paul Allen closed JENKINS-23882 as Fixed Long build startup 1.0.10 Change By: Paul Allen (11/Aug/14 3:22 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen closed JENKINS-24101 as Fixed Poll Watching Label Continually Triggering Fixed in 1.0.10 Please reopen if you find any issues. Change By: Paul Allen (11/Aug/14 3:24 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24105) Test failures on windows
Paul Allen commented on JENKINS-24105 Test failures on windows This is a know p4 admin stop issue on Windows. I might need to add a delay as the process can hang around and lock files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24203) SCM Polling Throwing an exception
Paul Allen commented on JENKINS-24203 SCM Polling Throwing an exception Please can you confirm if this is 1.0.10 or the development (SNAPSHOT) version. There is a situation when polling could fail if there are no previous builds. If you try the Build Now button, does the polling log report a fail on subsequent polling? Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24206) Support for workflow plugins
Paul Allen commented on JENKINS-24206 Support for workflow plugins Added support for Run/Job in my dev branch: https://github.com/p4paul/p4-jenkins However, I have a few questions: What will be the LTS version to support Run/Job (from 1.568)? When will this LTS version be available? Is there a prefered way to support both Run/Job and AbstractProject/AbstractBuild for compatibility with older version of Jenkins? (just leave the old methods for checkout etc... or check object with instanceof) E.g. to avoid errors like: hudson.scm.SCM.checkout(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/FilePath;Lhudson/model/BuildListener;Ljava/io/File;)Z java.lang.AbstractMethodError: hudson.scm.SCM.checkout(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/FilePath;Lhudson/model/BuildListener;Ljava/io/File;)Z at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1684) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen
commented on JENKINS-24101
Poll Watching Label Continually Triggering
I have looked at both of these issues and can't reproduce them in a simple environment. Freestyle + label.
I guess you have a more complex environment that is contributing to the issue. ${VAR} expansion or matrix builds or slaves. Would you consider a screen share or webex meeting to look closer at these issues?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24188) p4 credentials does not work for slave
Paul Allen closed JENKINS-24188 as Fixed p4 credentials does not work for slave Fixed 1.0.11 Change By: Paul Allen (13/Aug/14 1:58 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync Is the log truncated? The node log stops at "... force update false", I would have expected to see "... bypass have false" unless the populate options are different? I don't think it is possible to have different populate options for the nodes, unless there is some corruption. It could be a Windows bug; I need to setup a Windows environment to look at this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync I tried this out using Windows slaves, but have had no success at reproducing the issue. I have added more logging for remote slaves (change 9987 on the main branch). I have a theory that would be great if you could test out for me... My gut feeling here is that this is a serialization issue and old objects are not being read/passed correctly. To prove/disprove this the perfect way would be to setup a clean Jenkins install and see if you still have the bug. However, a quicker alternative would be to create a new Perforce Credentials object (delete the old one if you like) and perhaps try it with a new Jenkins Job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-19568) Support OpenGrok as SCM Browser for Perforce
Paul Allen commented on JENKINS-19568 Support OpenGrok as SCM Browser for Perforce I had a quick look at adding this, most of the work is done except I am not familiar with OpenGrok. Would you be willing to send me some sample urls so I can check the end-point/params correct? I would need the following: View a file Diff a file with an earlier revision View a job/issue View a change-set Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync The error message "rsmsnbuild119 is a client, not a label" suggest that you have provided a client workspace name and not a label? Was this intended? I know in Perforce you can sync at a client workspace, but the use case for Jenkins is not clear to me? The good news is that the "For input string: "3605760456"" error has gone, and looked like it was due to an invalid serialized object. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen
commented on JENKINS-24055
Matrix Job Unable To Sync
Is the configuration the same as when you opened the issue?
Workspace: Static
Character set: None
Workspace Name: ${NODE_NAME}
Populate Options: Sync Only, populate have list, pin to label unchecked
Polling Filters: None
Repo Browser: Auto
or are you specifying a Label, using the 'pin to label' or as a build param?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen
commented on JENKINS-24055
Matrix Job Unable To Sync
In the old code the error message "rsmsnbuild119 is a client, not a label" could only occur when trying to sync at a client workspace e.g.
p4 sync //some/path/...@client_workspace
I reproduced this by setting the Pin at Label to ${NODE_NAME} and got the same error. Even if this is not exactly the issue you are experiencing it needed to be fixed.
Have you tried a clean Jenkins Job? It seemed that creating a clean Credentials object fixed the serialization issue, perhaps your current Job is also corrupt.
If you like send me the XML for the job and I'll check the schema, it is located somewhere like:
$JENKINS_HOME/jobs/Job Name/config.xml
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync Could you send me the config.xml (please paste it in the issue or send it to me by email). Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync I found why it is syncing at your workspaces... (spaces get eaten, I'm hope the dots keep the indentation) ..axes hudson.matrix.LabelAxis ..namelabel/name ..values stringrsmsnbuild116/string stringrsmsnbuild117/string stringrsmsnbuild118/string stringrsmsnbuild119/string stringrsmsnbuild120/string stringrsmsnbuild121/string ./values /hudson.matrix.LabelAxis ../axes The axis name is called 'label' and Perforce picks this up as a build arg. Reserved build arg names are (label, change, review and status). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen edited a comment on JENKINS-24055 Matrix Job Unable To Sync I found why it is syncing at your workspaces... (spaces get eaten, I hope the dots keep the indentation) ..axes hudson.matrix.LabelAxis ..namelabel/name ..values stringrsmsnbuild116/string stringrsmsnbuild117/string stringrsmsnbuild118/string stringrsmsnbuild119/string stringrsmsnbuild120/string stringrsmsnbuild121/string ./values /hudson.matrix.LabelAxis ../axes The axis name is called 'label' and Perforce picks this up as a build arg. Reserved build arg names are (label, change, review and status). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync Great news! Thank you for your patients helping to debug this. Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [perforce] (JENKINS-24342) Plugin invalidates ticket when testing connection and using P4TICKETS
Paul Allen commented on JENKINS-24342 Plugin invalidates ticket when testing connection and using P4TICKETS Thanks for logging the issue under JIRA, I believe it is the same as this one: https://github.com/p4paul/p4-jenkins/issues/6 I have a fix submitted and hope to release it in 1.0.13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24328) View Mapping goes blank
Paul Allen commented on JENKINS-24328 View Mapping goes blank This is due to a bit of _javascript_ I added for the Manual workspace option. It populates the View text box, but Jenkins acts a bit odd with some click actions. I'm not sure the best way to fix this? I might have to ask the community. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24189) Need more info on Perforce credential connection error
Paul Allen commented on JENKINS-24189 Need more info on Perforce credential connection error Do you have the error message or part of the stack trace? Something like, 'P4: Unable to connect: ' Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24342) Plugin invalidates ticket when testing connection and using P4TICKETS
Paul Allen closed JENKINS-24342 as Fixed Plugin invalidates ticket when testing connection and using P4TICKETS Patched in 1.0.13 Change By: Paul Allen (22/Aug/14 2:19 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24189) Need more info on Perforce credential connection error
Paul Allen commented on JENKINS-24189 Need more info on Perforce credential connection error I have added more error logging and a second stage where the connection URI path is checked before establishing a Perforce connection. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24189) Need more info on Perforce credential connection error
Paul Allen closed JENKINS-24189 as Fixed Need more info on Perforce credential connection error Patched in 1.0.13 Change By: Paul Allen (22/Aug/14 2:20 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
Paul Allen commented on JENKINS-24202 Pin Build at Label Does not Sync at the CL of the Label Please can you check this with 1.0.13; I'm hoping it is fixed with all the other label updates. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24187) Perforce Credential 'Trust' field needs explantion ( ie implement the '?')
Paul Allen closed JENKINS-24187 as Fixed Perforce Credential Trust field needs explantion ( ie implement the ?) I have added error reporting with the Server's Trust fingerprint. Perhaps I should add a help bubble, but is this really necessary? Change By: Paul Allen (22/Aug/14 2:24 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
It may be a long shot, but is one of your axis names using a reserved name e.g. 'label'?
(I updated the docs; 'label', 'change', 'status', 'review', 'pass', and 'fail') Using any of these as axis names will have a strange effect.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen commented on JENKINS-24101 Poll Watching Label Continually Triggering JENKINS-24202 is now closed. Please can you verify if this job is now resolved? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
Paul Allen closed JENKINS-24202 as Fixed Pin Build at Label Does not Sync at the CL of the Label 1.0.13 Change By: Paul Allen (26/Aug/14 12:46 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin
Paul Allen commented on JENKINS-24427 P4 Trust error show up when integrate Parameterize Trigger Plugin Perhaps auto accept is the way to go; I wanted to actively encourage the user to verify the trust, but once established it should not change. With a shared home directory each client might access the trust file; could cause a threading issue. I'll need to look at this in more depth. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Are you using a the Manual workspace configuration (or Spec/Static/Stream/Template)?
Please can you send me the workspace view in Jenkins (if using the Manual mode)...
...and the client's view in Perforce. `p4 client -o client_name`
and let me know which view is which.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Thanks for the details. Kind of odd why the root is null and the view is missing; I'll look into it.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Thinking about this; Manual mode was the only one I intended to use for variable expansion ${foo} in the View. However, Template and Streams were the modes I had thought would be used for slave/matrix builds.
As you can see the View is expanded for the Parent as I would expect, but the workspace is assumed to have already been created for the children and so the fields are blank.
I could enhance the plugin to either:
1. Support view expansion for template workspaces (not possible for streams as the View is managed by the server).
or
2. For manual builds, auto create workspaces for the children at build time.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-23890) Error on Maven build with SCM changes
Paul Allen commented on JENKINS-23890 Error on Maven build with SCM changes Very strange? I have setup a Windows + Maven environment; I did get some other Web/Jelly errors, due to XStream on Java 8. I upgraded Jenkins to 1.558 and all the errors vanished. What version of Jenkins are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24490) 'Poll Only' or 'Disable Sync' option
Paul Allen commented on JENKINS-24490 Poll Only or Disable Sync option I had been looking at this issue a few weeks back for another customer. Frustratingly the code is quite simple to detect/disable the triggering for the parent/children. The harder part has been adding the option to the UX, so that it appears within the context of Matrix builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24493) P4 Plugin cannot sync symlinks
Paul Allen commented on JENKINS-24493 P4 Plugin cannot sync symlinks You need to be running Java 7 or later (symlinks were only recently supported in Java nio). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24512) Add option to lock the created workspace to a host
Paul Allen commented on JENKINS-24512 Add option to lock the created workspace to a host Initially I did set the host field, but Jenkins did not reliably give me the correct host (master vs remote slave builds). I'll look into this again and see if I can extract it from another location. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24512) Add option to lock the created workspace to a host
Paul Allen commented on JENKINS-24512 Add option to lock the created workspace to a host I can set the host using InetAddress.getLocalHost().getHostName(); however should I set the workspace before every build? Or just at creation? The issue is at creation you don't necessarily know which Slaves the workspace will run on? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen closed JENKINS-24101 as Cannot Reproduce Poll Watching Label Continually Triggering Unable to reproduce; seems to be resolved. Change By: Paul Allen (02/Sep/14 10:53 AM) Status: Reopened Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24390) P4TICKETS credential should honor default values
Paul Allen
commented on JENKINS-24390
P4TICKETS credential should honor default values
Sorry; yes.
With different operating systems the location can move. P4TICKETS is not always set (the command line defaults to $HOME/.p4tickets). Perhaps an enhancement for P4JAVA to look in the default or my plugin.
{Reassigned as a feature}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-23890) Error on Maven build with SCM changes
Paul Allen commented on JENKINS-23890 Error on Maven build with SCM changes Does this occur with just one Maven style project or all? I'm out of ideas at the moment and the only thing I can think it could be is an out of date object created with an earlier version of the plugin. Perhaps try creating a new Maven style project with the same settings and see if this fails. If it does fail please send me a copy of your config.xml (under the 'jobs/project/' folder) and the latest build.xml (under the 'jobs/project/builds/nnn/ folder). Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24390) P4TICKETS credential should honor default values
Paul Allen updated JENKINS-24390 P4TICKETS credential should honor default values Change By: Paul Allen (02/Sep/14 10:55 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24499) workspace's root directory should be translate into real directory
Paul Allen closed JENKINS-24499 as Incomplete workspaces root directory should be translate into real directory Closing to tidy up the list (and you have a similar job open). Change By: Paul Allen (02/Sep/14 10:24 AM) Status: Open Closed Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24493) P4 Plugin cannot sync symlinks
Paul Allen commented on JENKINS-24493 P4 Plugin cannot sync symlinks For the Runtime (JRE): http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html If you want to Build/Compile (JDK): http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen commented on JENKINS-24101 Poll Watching Label Continually Triggering Sorry for the delay (been out on vacation). I'm travelling the next few weeks with work, but hope to make some progress with Jenkins. If the polling interval is shorter than the sync time, I could see how this situation would occur. I will have to either: 1. check builds in-progress and only trigger on new changes? or 2. stall polling if a build is already in-progress? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24493) P4 Plugin cannot sync symlinks
Paul Allen resolved JENKINS-24493 as Not A Defect P4 Plugin cannot sync symlinks Hi Tom, glad to hear all is ok. Thanks for the reminder about the Crypto libs. Closing the issue. Change By: Paul Allen (15/Sep/14 11:51 AM) Status: Open Resolved Assignee: PaulAllen Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23974) Private maven repo got wipe out every build
Paul Allen commented on JENKINS-23974 Private maven repo got wipe out every build How did the other plugin do this? Exclude filter on path or file extension? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24855) Build Review not working with Swarm
Paul Allen commented on JENKINS-24855 Build Review not working with Swarm It looks like the '=' is missing on the review attribute. It should read 'review=247': .../review/build?status=shelvedreview=247pass=... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24855) Build Review not working with Swarm
Paul Allen closed JENKINS-24855 as Not A Defect Build Review not working with Swarm Change By: Paul Allen (01/Oct/14 11:18 PM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
resolved JENKINS-24028 as Fixed
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Fixed in 1.0.15
Change By:
Paul Allen
(02/Oct/14 3:22 PM)
Status:
Reopened
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24607) Need ability to build changes sequentially
Paul Allen commented on JENKINS-24607 Need ability to build changes sequentially I was thinking about adding a option for incremental changelist building under the 'Polling build filters'. This would allow you to set it per-project. I like Morne Joubert's idea of a binary bisect; not sure I could implement that in the plugin, but would be happy to review any shelved changes or pull requests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24599) Parameters are not resolved in stream
Paul Allen
commented on JENKINS-24599
Parameters are not resolved in stream
A quick workaround would be '//${streamDepot}/${codeline}' or '//${streamPath}
The '//' is a sanity check; to use a ${var} param I would need to test the expanded var. However, depending on how you set the ${var} it may not be valid on the page check.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24599) Parameters are not resolved in stream
Paul Allen
commented on JENKINS-24599
Parameters are not resolved in stream
No, they were just example variables.
The only 'special' variables are: ${label}, ${change}, ${status}, ${pass}, ${fail}. They are reserved for the Review/Shelve feature (avoid using them as 'axis' names in a multi config project).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24427) P4 Trust error show up when integrate Parameterize Trigger Plugin
Paul Allen closed JENKINS-24427 as Fixed P4 Trust error show up when integrate Parameterize Trigger Plugin Change By: Paul Allen (07/Oct/14 9:55 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24978) Change entry repeated
Paul Allen resolved JENKINS-24978 as Fixed Change entry repeated Fixed in 1.0.15 Change By: Paul Allen (07/Oct/14 9:58 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23718) Unable to use ${NODE_NAME} as a Workspace name
Paul Allen
commented on JENKINS-23718
Unable to use ${NODE_NAME} as a Workspace name
I'm still looking into the best implementation for this issue.
Currently I only support ${...} formatters for template and streams workspaces, but I can understand why you need them for static workspaces.
That part of change is fairly simple, but I am trying to understand how to access environment vars. I have been experimenting with Parameters builds vars and environment vars, but not sure about their visibility outside of a build (e.g. SCM polling).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-23760) Workspace Name Format cannot contain spaces
Paul Allen assigned JENKINS-23760 to Paul Allen Workspace Name Format cannot contain spaces Change By: Paul Allen (21/Jul/14 1:14 PM) Assignee: PaulAllen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23760) Workspace Name Format cannot contain spaces
Paul Allen resolved JENKINS-23760 as Fixed Workspace Name Format cannot contain spaces Fixed in version 1.0.5 P4 client replaces a space with an underscore (bug in p4java). Change By: Paul Allen (21/Jul/14 1:17 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23889) Remove Eclipse generate files from source tree
Paul Allen resolved JENKINS-23889 as Fixed Remove Eclipse generate files from source tree Removed the .classpath and .project files from Workshop (never made it into GitHub) Change By: Paul Allen (21/Jul/14 1:25 PM) Status: Open Resolved Assignee: PaulAllen Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23718) Unable to use ${NODE_NAME} as a Workspace name
Paul Allen
commented on JENKINS-23718
Unable to use ${NODE_NAME} as a Workspace name
The latest 1.0.6 release should allow access to the NODE_NAME parameter. I also extended the other workspaces to accept the formatting parameters.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-23718) Unable to use ${NODE_NAME} as a Workspace name
Paul Allen
closed JENKINS-23718 as Fixed
Unable to use ${NODE_NAME} as a Workspace name
Fixed in 1.0.6
Change By:
Paul Allen
(28/Jul/14 9:17 AM)
Status:
Open
Closed
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-23890) Error on build with SCM changes
Paul Allen commented on JENKINS-23890 Error on build with SCM changes Change 9745 might have resolved this, but I have a feeling that something else is at play here. Looking in the forums it might that Tomcat is a factor. Perhaps it can't find the digest.jelly page or resolves paths in a different way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23953) Expose Enviornment Variable that contains the current changelist
Paul Allen closed JENKINS-23953 as Fixed Expose Enviornment Variable that contains the current changelist Fixed in 1.0.6 Change 9761 Change By: Paul Allen (28/Jul/14 9:29 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23974) Private maven repo got wipe out every build
Paul Allen commented on JENKINS-23974 Private maven repo got wipe out every build If the Populate option is set to remove unversioned files between builds, then yes this file will go; I think this behaviour is unchanged from the first release. You could uncheck the 'DELETE generated files' option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23881) Too much changelog
Paul Allen commented on JENKINS-23881 Too much changelog Considering to change the reporting so that the first build will only report one change and not all the changes on that branch. An alternative is to limit the changes to the last 10. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24022) Running 'files' command for multiple hours with a label
Paul Allen closed JENKINS-24022 as Fixed Running files command for multiple hours with a label Release 1.0.8 Limit to 50 files and number of reported changes on first build. Change By: Paul Allen (30/Jul/14 4:39 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
closed JENKINS-24028 as Fixed
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Release 1.0.8
Replace "/" "=" and "," with "-" as per old plugin
Change By:
Paul Allen
(30/Jul/14 4:40 PM)
Status:
Open
Closed
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24027) Null Pointer Exception when trying to update workspace
Paul Allen closed JENKINS-24027 as Fixed Null Pointer Exception when trying to update workspace Release 1.0.8 Shared Workshop object was not cloned for Matrix Builds and not required for non client functions like p4 changes/p4 files. Should fix this issue; please reopen if required. Change By: Paul Allen (30/Jul/14 4:43 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24004) dev and main branch versions are out of sync
Paul Allen closed JENKINS-24004 as Fixed dev and main branch versions are out of sync Done Change By: Paul Allen (30/Jul/14 4:52 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23881) Too much changelog
Paul Allen closed JENKINS-23881 as Fixed Too much changelog Resolved in 1.0.8 (perhaps even 1.0.7) Change By: Paul Allen (30/Jul/14 4:54 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24024) Opt-out of pulling changelist info for Build Changes
Paul Allen commented on JENKINS-24024 Opt-out of pulling changelist info for Build Changes Should the opt-out be global or configured for each Jenkins Build Job? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24025) Unable to set line ending format for stream workspace
Paul Allen commented on JENKINS-24025 Unable to set line ending format for stream workspace I can add this to the 'Stream' option for generating streams workspaces. Are you able to use the 'Manual', 'Spec', or 'Static' workspace options? I guess that they are not as easy for matrix builds as you would have to set them up individually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24005) Pin build at Perforce Label does not support variable expansion
Paul Allen commented on JENKINS-24005 Pin build at Perforce Label does not support variable expansion Interesting uses case; I had not thought of that option. Out of interest what sort of variables do you use? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23890) Error on build with SCM changes
Paul Allen commented on JENKINS-23890 Error on build with SCM changes Please can you check this with the 1.0.8 release. I have not been able to reproduce this issue, it seems that Jetty swallows up the error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23974) Private maven repo got wipe out every build
Paul Allen commented on JENKINS-23974 Private maven repo got wipe out every build Should I close this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23974) Private maven repo got wipe out every build
Paul Allen closed JENKINS-23974 as Fixed Private maven repo got wipe out every build Change By: Paul Allen (31/Jul/14 8:27 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync I'm unable to reproduce this with a simple setup (all running on the master). Do you use slave nodes? Are they pinned in any way? Please can you see if there are any clues in the Jenkins log (stack trace etc...) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
Paul Allen commented on JENKINS-25085 email-ext showPaths does not work with p4-plugin Happy to try and support this, but I'm going to need a lot more to go on here. The change data is recorded in the XML files; the parser is there. I'm guessing that an enhancement is needed in the email-ext plugin to access/read the new format. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-19568) Support OpenGrok as SCM Browser for Perforce
Paul Allen closed JENKINS-19568 as Fixed Support OpenGrok as SCM Browser for Perforce 1.0.16 - Basic support added (please open a new JIRA issues/features as required) Change By: Paul Allen (13/Oct/14 9:49 AM) Status: Open Closed Assignee: PaulAllen Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24599) Parameters are not resolved in stream
Paul Allen
resolved JENKINS-24599 as Wont Fix
Parameters are not resolved in stream
As outlined the sanity check can't necessarily expand the ${var}.
The alternative would be to remove the check altogether. If common use changes from explicit paths to expanded vars then I may change the sanity check.
Change By:
Paul Allen
(13/Oct/14 9:55 AM)
Status:
Open
Resolved
Resolution:
WontFix
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [p4] (JENKINS-24607) Need ability to build changes sequentially
Paul Allen closed JENKINS-24607 as Fixed Need ability to build changes sequentially Added in 1.0.16 Change By: Paul Allen (13/Oct/14 9:57 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
Paul Allen commented on JENKINS-25085 email-ext showPaths does not work with p4-plugin I'll see what I can implement. My concern is that I don't want to store 1000s files in the Jenkins XML like the old plugin. As the data is in Perforce, all I have been storing is the change numbers, then I can look the files up as needed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25134) Enhance 'Auto cleanup and sync' populate option to not remove private repository directory
Paul Allen commented on JENKINS-25134 Enhance Auto cleanup and sync populate option to not remove private repository directory I think your requested is related to JENKINS-23974 I'm looking for a neat solution, I don't necessarily want to reimplement the old plugin. Have you tried a workspace exclusionary mapping? e.g. //depot/my_proj/... //workspace/... -//depot/my_proj/.repository //workspace/.repository This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25134) Enhance 'Auto cleanup and sync' populate option to not remove private repository directory
Paul Allen commented on JENKINS-25134 Enhance Auto cleanup and sync populate option to not remove private repository directory Pleased to hear that worked for you, I'll see if it satisfies JENKINS-23974. Thanks for closing the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-23974) Private maven repo got wipe out every build
Paul Allen commented on JENKINS-23974 Private maven repo got wipe out every build I had a similar request in JENKINS-25134 and suggested an exclusionary workspace view mapping. e.g. //depot/my_proj/... //workspace/... -//depot/my_proj/.repository/... //workspace/.repository/... Would that work for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25134) Enhance 'Auto cleanup and sync' populate option to not remove private repository directory
Paul Allen commented on JENKINS-25134 Enhance Auto cleanup and sync populate option to not remove private repository directory Just thought you might need /... on the end if .repository is a dir. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-24624) Support for shared workspaces
Paul Allen commented on JENKINS-24624 Support for shared workspaces It may be possible to share workspaces using the client -s flag (with -t or -S). The -s flag would switch the view and a sync should only fetch the differences. This would help with the storage requirements for a workspace as there is only one root required per executor. How to implemented under Jenkins is going to need some careful thought. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Sorry if I missed something, but from what I can see in the config files you are using the label/tag feature to create a label called 'basic_check', which gets updated on each build. Then the other build is pinned to this label. I'll see if I can reproduce this. I did notice that the config file references p4@1.0.13? Are you running the latest build, as I have recently changed the way changes are calculated (1.0.16). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Could you send me the last build.xml file from the job reporting no changes and the details of the label. e.g. p4 label -o basic_check Label: basic_check ... Revision: @370 I want to see if the buildChange class="int" value is lower than the 'Revision' specified in the label. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [p4] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
Paul Allen commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Yes I see the issue... buildChange class="string"basic_check/buildChange I store the label, not the change. When I try to calculate the changes since the last build I access the label, but that has been updated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
