[JIRA] [perforce] (JENKINS-22487) reporting p4.prog name to perforce server
Jarek Kapica updated JENKINS-22487 reporting p4.prog name to perforce server Change By: Jarek Kapica (08/Apr/14 8:51 AM) Description: Ihavecreatedapullrequestongithubthatenablesreportingp4programnametoPerforceserver.Imcurrentlyusingthepatchontopofperforce-1.3.27.Itisisveryusefulforidentifyingtheconnectionsthatcomefromautomatedsystemsandaccountforthem.Thereisaglobalsettingthatallowssettingsystemwidedefaultvalue,aswellasperjobspecificvalue.Ifdesireditisalsopossibletospecifydifferentvaluejustforpollingqueries.Moredetailsareinhelpsnippets.Pullrequestlink:https://github.com/jenkinsci/perforce-plugin/pull/ 46 47 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-22487) reporting p4.prog name to perforce server
Jarek Kapica created JENKINS-22487 reporting p4.prog name to perforce server Issue Type: New Feature Assignee: Rob Petti Components: perforce Created: 03/Apr/14 3:45 PM Description: I have created a pull request on github that enables reporting p4 program name to Perforce server. I'm currently using the patch on top of perforce-1.3.27. It is is very useful for identifying the connections that come from automated systems and account for them. There is a global setting that allows setting system wide default value, as well as per job specific value. If desired it is also possible to specify different value just for polling queries. More details are in help snippets. Poll request link: https://github.com/jenkinsci/perforce-plugin/pull/46 Project: Jenkins Priority: Major Reporter: Jarek Kapica 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-22487) reporting p4.prog name to perforce server
Jarek Kapica updated JENKINS-22487 reporting p4.prog name to perforce server Change By: Jarek Kapica (03/Apr/14 3:46 PM) Description: Ihavecreatedapullrequestongithubthatenablesreportingp4programnametoPerforceserver.Imcurrentlyusingthepatchontopofperforce-1.3.27.Itisisveryusefulforidentifyingtheconnectionsthatcomefromautomatedsystemsandaccountforthem.Thereisaglobalsettingthatallowssettingsystemwidedefaultvalue,aswellasperjobspecificvalue.Ifdesireditisalsopossibletospecifydifferentvaluejustforpollingqueries.Moredetailsareinhelpsnippets. Poll Pull requestlink:https://github.com/jenkinsci/perforce-plugin/pull/46 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-19794) Prevent password exposure in perforce
Jarek Kapica commented on JENKINS-19794 Prevent password exposure in perforce I would expect passwordExposeDisabled, to override local value, but not change it. Currently it's incidentally changing it, when user saves job's configuration. Consider scenario: 1. Initially passwordExposeDisabled is false in global config 2. User sets exposeP4Passwd to true in job's config 3. Admin notices nice new global passwordExposeDisabled option and sets it to true to enhance security 4. User notices they job started to fail for some reason, and tries to fix it by changing something irrelevant in job's config. They doesn't have access to exposeP4Passwd, and so on first save it is implicitly reset to false 5. Some time later, Admin realize that step 3 is the cause of the break, so they sets passwordExposeDisabled in global config back to false, to allow security breaches be addressed without stopping vulnerable production 6. The job is still failing because in step 4, value of job specific exposeP4Passwd, was implicitly saved to false My point is passwordExposeDisabled shall override, but not change the original value of exposeP4Passwd. 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce
Jarek Kapica edited a comment on JENKINS-19794 Prevent password exposure in perforce Totally agree. And very good point with the warning. User should be aware that the option has been disabled globally and be able to disable it on his end, to turn off the warning. 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce
Jarek Kapica commented on JENKINS-19794 Prevent password exposure in perforce Totally agree. And very good point with the warning. User should be aware that the option has been disabled and be able to disable it on his end, to turn off the warning. 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce
Jarek Kapica commented on JENKINS-19794 Prevent password exposure in perforce Agree. But I believe there is no need to depend position of the option in the form (main/advanced) in respect to global setting. This is cosmetic change and it shouldn't be a problem to just move it to advanced, especially since you want to deprecate 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce
Jarek Kapica commented on JENKINS-19794 Prevent password exposure in perforce Wouldn't this change reset job specific setting, rather than merely overriding it. Is that what is really intended? https://github.com/jenkinsci/perforce-plugin/pull/36/files#diff-a6a8e160fa20240410923ec7114cfacfR2711 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce
Jarek Kapica reopened JENKINS-19794 Prevent password exposure in perforce Change By: Jarek Kapica (22/Nov/13 11:38 PM) Resolution: Fixed Status: Resolved Reopened 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-17889) Build one changeset at a time
Jarek Kapica commented on JENKINS-17889 Build one changeset at a time Thanks for suggestion. The pull request: https://github.com/jenkinsci/perforce-plugin/pull/38 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-17889) Build one changeset at a time
Jarek Kapica updated JENKINS-17889 Build one changeset at a time I have created a patch that implements this feature. Can it be included in upstream release? Change By: Jarek Kapica (05/Jun/13 9:48 AM) Attachment: Added-One-Changelist-Only-option.patch 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-17889) Build one changeset at a time
Jarek Kapica updated JENKINS-17889 Build one changeset at a time Change By: Jarek Kapica (05/Jun/13 12:07 PM) Attachment: Added-One-Changelist-Only-option.patch 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/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18013) Make Project Name to be a hyperlink
Jarek Kapica created JENKINS-18013 Make Project Name to be a hyperlink Issue Type: Improvement Assignee: Fred G Components: extra-columns Created: 20/May/13 1:45 PM Description: When showing "Project Name" in "Project description" column, it should be a hyperlink to project details as is normally with the default "Project Name" column. That would allow taking off the default "Project Name" column from the view. Currently without the default column, there is no lonk to the project overview screen. It would be ideal if the link is active as currently is. I.e. showing submenu when hovering over it. But it would also be ok if it is just plain link. Project: Jenkins Priority: Major Reporter: Jarek Kapica 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/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18013) Make Project Name to be a hyperlink
Jarek Kapica updated JENKINS-18013 Make Project Name to be a hyperlink Change By: Jarek Kapica (20/May/13 1:46 PM) Description: WhenshowingProjectNameinProjectdescriptioncolumn,itshouldbeahyperlinktoprojectdetailsasisnormallywiththedefaultProjectNamecolumn.ThatwouldallowtakingoffthedefaultProjectNamecolumnfromtheview.Currentlywithoutthedefaultcolumn,thereisno lonk link totheprojectoverviewscreen.Itwouldbeidealifthelinkisactiveascurrentlyis.I.e.showingsubmenuwhenhoveringoverit.Butitwouldalsobeokifitisjustplainlink. 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-17889) Build one changeset at a time
Jarek Kapica created JENKINS-17889 Build one changeset at a time Issue Type: Improvement Assignee: Rob Petti Components: perforce Created: 07/May/13 3:40 PM Description: Provide a possibility to build every changeset, one at a time. The proposed implementation concept: Add a checkbox in advanced plugin configuration to build next changeset after the one that have been previously built. Then if it is ticked, perforce plugin could calculate the next changeset after the one used in last build, and check out that one instead. That would mean there is also a need for catchup solution for bigger projects, but for small and average frequent pooling should be enough. This would be very useful when you need to build all changesets to e.g. detect who broke the build. Project: Jenkins Priority: Major Reporter: Jarek Kapica 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/groups/opt_out.
