[JIRA] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Andy Bigos commented on JENKINS-17873 FSTrigger does not accept Parameters Same situation here. Would be good to avoid repeating the value if such as mechanism was possible. 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Gregory Boissinot commented on JENKINS-17873 FSTrigger does not accept Parameters Job Parameters are only processed at build tine. They cannot be used by XTrigger plugin as the FSTrigger plugin. Therefore, you have to put the plain value. 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Gregory Boissinot started work on JENKINS-17873 FSTrigger does not accept Parameters Change By: Gregory Boissinot (08/May/13 7:38 PM) Status: Open InProgress 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Gregory Boissinot commented on JENKINS-17873 FSTrigger does not accept Parameters Does it suit 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/groups/opt_out.
[JIRA] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Ken Beal commented on JENKINS-17873 FSTrigger does not accept Parameters Hi Gregory, not exactly. Our scenario is: we want to define the location in one place, and reference it from the other. Right now we have it as a Parameter, and also as an FSTrigger setting. I understand that job Parameters cannot be used here the question now is: is there any mechanism to avoid having this information hard-coded in two locations? The FSTrigger is to a completion file that the build writes when it is done; we also want to do a directory of that for forensics, so we know time/date and size etc. The location is a complex path with the "branch" as a component of the path. We create new build jobs for new branches, and it would be far preferable to have to update one piece of data with the new branch, rather than needing to update two. Is there any possibility that some other functionality might assist us here? Thanks! Ken 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Ken Beal created JENKINS-17873 FSTrigger does not accept Parameters Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: fstrigger Created: 06/May/13 3:58 PM Description: Repro steps: 1. Create a new job, "Test-FSTrigger". 2. Configure a string Parameter "monitor", with value "c:\test". 3. Check the "FSTrigger - Monitor files", then click "Add file to monitor" and in the "File Path" text field, enter "$monitor". 4. In the "Schedule" text field, enter "* * * * *" so it will monitor every minute. 5. Save the job, and wait one minute. Then click on the "FSTrigger Files Log" link in the left menu. Expected results: It should have said the folder doesn't exist (and then I would create the folder, wait a minute to see what it said then; then create the file, and wait a minute to see it function). Actual results: It shows an error: "ERROR - Polling error The given pattern for the file to monitor must have a directory." Environment: Windows 7 Project: Jenkins Priority: Major Reporter: Ken Beal 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.
