[JIRA] [fstrigger-plugin] (JENKINS-21571) FSTrigger doesn't trigger scheduled jobs on restart
Eric Anker commented on JENKINS-21571 FSTrigger doesnt trigger scheduled jobs on restart I'm running into this issue as well. Below are a bunch of guesses by a novice Jenkins Plugin developer. Having a look at: fstrigger-plugin/src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FolderContentTrigger.java and xtrigger-lib/src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java ...it's my *GUESS* that Mr. Boissinot is using the "offlineSlaveOnStartup" member variable to denote that it is the first time that the trigger has been run since the Jenkins Server initialized. It looks like the "MapString, FileInfo md5Map" is just resident in memory and is not saved between sessions. I think it needs to initialize once before the plug-in has a point of reference for future "checkIfModified()" calls. Suggested solutions going forward: EASY: Maybe the message should be more descriptive as to what's going on: "Initilaizing Folder md5Map... Waiting for next schedule to check if there are modifications."); or LESS EASY: Initialize the "md5Map" right when Jenkins starts? (instead of waiting for the next scheduled run) A.K.A. Override: public void start(BuildableItem project, boolean newInstance)??? or HARD?: The "md5Map" variable should be committed to disk... somehow? and reloaded after a Jenkins Server Reboot. 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] [role-strategy] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Eric Anker commented on JENKINS-24767 Role-based Authorization Strategy not working with sub-folders Thank you for the speedy response. I got what I needed by making 2 roles. Folder1View with RegEx: "Folder1" and Job/Read ticked Folder1FolderA with RegEx: "Folder1/FolderA.*" and Job/Read + Job/Build ticked 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] [role-strategy] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Eric Anker closed JENKINS-24767 as Not A Defect Role-based Authorization Strategy not working with sub-folders Some additional help text somewhere would be welcome. Thanks for your help! Change By: Eric Anker (22/Sep/14 2:07 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] [role-strategy] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Eric Anker
updated JENKINS-24767
Role-based Authorization Strategy not working with sub-folders
Change By:
Eric Anker
(22/Sep/14 2:05 PM)
Description:
Usingthefolderstructurebelow,tryingtogiveauseraccesstoONLYthecontentsofFolderA.Idexpect
{noformat}
.*FolderA.*
{noformat}
todothat.ToReproduce:Createthisfolderstructure:Folder1/Folder1/FolderA/Folder1/FolderA/JobAFolder1/FolderB/Folder1/FolderB/JobBFolder1/Job1Trythesesearchexpressions:
{noformat}
-
.*Folder1.*
Works-
.*FolderA.*
DoesNOTwork-
.*JobA.*
DoesNOTwork-
.*FolderB.*
DoesNOTwork-
.*JobB.*
DoesNOTwork-
.*Job1.*
DoesNOTwork
{noformat}
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] [cloudbees-folder] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Eric Anker created JENKINS-24767 Role-based Authorization Strategy not working with sub-folders Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder, role-strategy Created: 18/Sep/14 6:37 PM Description: Using the folder structure below, trying to give a user access to ONLY the contents of FolderA. I'd expect .FolderA. to do that. To Reproduce: Create this folder structure: Folder1/ Folder1/FolderA/ Folder1/FolderA/JobA Folder1/FolderB/ Folder1/FolderB/JobB Folder1/Job1 Try these search expressions: - .Folder1. Works - .FolderA. Does NOT work - .JobA. Does NOT work - .FolderB. Does NOT work - .JobB. Does NOT work - .Job1. Does NOT work Environment: Jenkins ver. 1.565.2 CloudBees Folders Plugin 4.6.1 Role-based Authorization Strategy 2.2.0 Windows 7 Project: Jenkins Labels: security folders role regex Priority: Major Reporter: Eric Anker 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] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break Those settings fixed it. Thank you so much for your attention to 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] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break Sorry for the delay. Thanks for following up. That scenario appears to work! So there's something not right with my fairly stock tomcat instance then? 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] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break I'm using pure Tomcat (No Apache web server) so, I don't that Jk setting applies... I tried upgrading to Jenkins ver. 1.554.2 and updating all the plugins on my test system - The Manage Jenkins Page has no warnings about reverse-proxy and the issue is still present. Thank you for your continued support, Daniel. Where should I look next? 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] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break Jenkins ver. 1.514 / apache-tomcat-7.0.39 No complaint on the Manage Jenkins Page What else can I look for? 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] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break I don't believe so. it's a single server and the issue is present on localhost. How else can I help diagnose? 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] [plugin] (JENKINS-18244) Passwords should not be stored as clear text in config.xml and should not be printed out to the log
Eric Anker created JENKINS-18244 Passwords should not be stored as clear text in config.xml and should not be printed out to the log Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: plugin, rqm Created: 06/Jun/13 9:17 PM Description: RQM plugin v1.0 stores the password for the RQM server in clear text in the config.xml for the project In addition, it prints the password out to the log. Passwords should be at least obscured. It's common to use 64 bit encoding to store in flat text config files. Passwords should probably also NOT be printed to the log... ever. Project: Jenkins Labels: plugin security configuration Priority: Major Reporter: Eric Anker 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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Eric Anker commented on JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Suggested Fix Here: https://github.com/jenkinsci/xunit-plugin/pull/4 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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Eric Anker
created JENKINS-17438
xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
xunit
Created:
02/Apr/13 8:14 PM
Description:
When using the xUnit Custom Tool and specifying a Global Property (ex. ${XUNIT_RFT_TO_JUNIT} ) as the Custom stylesheet, the property does not get resolved. This makes the plugin look for a file named "${XUNIT_RFT_TO_JUNIT}" in the workspace directory. When is should be looking for the path specified in the Global Property
Note: The Custom Tool Pattern accepts and resolves Global Properties just fine. (ex ${XUNIT_CUSTOM_XML} )
Project:
Jenkins
Priority:
Minor
Reporter:
Eric Anker
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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Eric Anker updated JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Config screenshot console screenshot Change By: Eric Anker (02/Apr/13 8:15 PM) Attachment: XUNIT_CUSTOM1.png Attachment: XUNIT_CUSTOM2.png 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.
