[JIRA] (JENKINS-34839) Add new provider UpstreamComitterSinceLastSuccess
Title: Message Title Jim Searle commented on JENKINS-34839 Re: Add new provider UpstreamComitterSinceLastSuccess Thanks. I was hoping it was because there was some other way to handle it. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34839) Add new provider UpstreamComitterSinceLastSuccess
Title: Message Title Jim Searle commented on JENKINS-34839 Re: Add new provider UpstreamComitterSinceLastSuccess Is there are reason this has never been released? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] [email-ext-plugin] (JENKINS-34839) Add new provider UpstreamComitterSinceLastSuccess
Title: Message Title Jim Searle updated an issue Jenkins / JENKINS-34839 Add new provider UpstreamComitterSinceLastSuccess Change By: Jim Searle Create a provider like UpstreamComitterRecipientProvider from JENKINS-17742 for UpstreamComitterSinceLastSuccess which gets all committers of changes since the current job was last successful. This should look up the entire tree of job dependencies and find all committers since you may have multiple upstream jobs that do scm checkouts. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-17742) Pick Up Committer from Upstream Job
Title: Message Title Jim Searle commented on JENKINS-17742 Re: Pick Up Committer from Upstream Job Done https://issues.jenkins-ci.org/browse/JENKINS-34839 Thank you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-34839) Add new provider UpstreamComitterSinceLastSuccess
Title: Message Title Jim Searle created an issue Jenkins / JENKINS-34839 Add new provider UpstreamComitterSinceLastSuccess Issue Type: New Feature Assignee: Alex Earl Components: email-ext-plugin Created: 2016/May/15 4:46 PM Labels: plugin Priority: Major Reporter: Jim Searle Create a provider like UpstreamComitterRecipientProvider from JENKINS-17742 for UpstreamComitterSinceLastSuccess which gets all committers of changes since the current job was last successful. Add Comment
[JIRA] [email-ext-plugin] (JENKINS-17742) Pick Up Committer from Upstream Job
Title: Message Title Jim Searle commented on JENKINS-17742 Re: Pick Up Committer from Upstream Job Thanks. Can anyone help with adding it? We are stuck with using the blame subversion plugin but would like to have a better solution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-17742) Pick Up Committer from Upstream Job
Title: Message Title Jim Searle commented on JENKINS-17742 Re: Pick Up Committer from Upstream Job Is it possible to add all upstream committers since last success to this Provider? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15658) EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable
Jim Searle commented on JENKINS-15658 EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable Thanks! Where do I get the new version of the plugin? 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
[JIRA] (JENKINS-15658) EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable
Jim Searle commented on JENKINS-15658 EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable That fixed it. Thanks! 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
[JIRA] (JENKINS-15658) EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable
Jim Searle
created JENKINS-15658
EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
envinject
Created:
29/Oct/12 11:01 PM
Description:
In my jenkins configuration for "Global properties", I have a property TEST_WORKSPACE defined as ${WORKSPACE}.
Then in my jenkins job I have "prepare an environment for the run" defined to a file which does not set TEST_WORKSPACE or WORKSPACE.
But, when I run the job, TEST_WORKSPACE is not defined in console, I get this:
EnvInject - Loading node environment variables.
EnvInject - Preparing an environment for the build.
EnvInject - Keeping Jenkins system variables.
EnvInject - Keeping Jenkins build variables.
EnvInject - Adding build parameters as variables.
EnvInject - Injecting as environment variables the properties file path '/home/jims/global.prop'
EnvInject - Variables injected successfully.
EnvInject - Injecting contributions.
Building on master in workspace /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace
workspace $ /bin/sh -x /tmp/hudson3013573853871224155.sh
+ echo 'WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace'
WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace
+ echo 'TEST_WORKSPACE = '
TEST_WORKSPACE =
Notifying upstream projects of job completion
Finished: SUCCESS
If I revert back to envinject 1.36, then it is defined and I see this in the console:
EnvInject - Preparing an environment for the job.
EnvInject - Keep Jenkins system variables.
EnvInject - Keep Jenkins build variables.
EnvInject - Injecting as environment variables the properties file path '/home/jims/global.prop'
EnvInject - Variables injected successfully.
EnvInject - Unset unresolved 'TEST_WORKSPACE' variable.
Building on master in workspace /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace
workspace $ /bin/sh -x /tmp/hudson3503397345619621354.sh
+ echo 'WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace'
WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace
+ echo 'TEST_WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace'
TEST_WORKSPACE = /projects/BCMQUAL/jenkins_test/jobs/test-envinject/workspace
Notifying upstream projects of job completion
Finished: SUCCESS
Environment:
Linux lc-irv-1231 2.6.9-89.0.9.ELsmp #1 SMP Wed Aug 19 08:06:10 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Jenkins 1.486
envinject 1.72
Project:
Jenkins
Priority:
Major
Reporter:
Jim Searle
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
[JIRA] (JENKINS-2244) ext-email builds dev list different than mail
Jim Searle commented on JENKINS-2244 ext-email builds dev list different than mail Copy of my comment from JENKINS-9336: Our problem is a different. I created a small test case to show the issue, we have these jobs. "init" Triggers "regress", Uses join trigger on "regress-done". The regress and regress-done jobs uses blamesubversion plugin. #1: commit by usera, init fails. #2: commit by userb, init fails. #3: commit by userc, init passes, regress #1 passes, regress-done #1 fails, only userc is notified. Is this a problem with email-ext or blamesubversion plugin? 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
[JIRA] (JENKINS-9336) Culprits Email List - Names Can be Dropped
Jim Searle commented on JENKINS-9336 Culprits Email List - Names Can be Dropped Yes, this does still seem to be an issue. We are on Email-ext 2.21 with Jenkins 1.472. My example was slightly different because the final job is using the blame-subversion plugin, but I will test with just using straight svn. 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
[JIRA] (JENKINS-9364) Add support for tokens from the token-macro plug-in
Jim Searle commented on JENKINS-9364 Add support for tokens from the token-macro plug-in Sorry, I was wrong. The email does get sent, but I'd still like to have the option to shut this off since it shows a huge error message in the console. 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
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
Jim Searle resolved JENKINS-12176 as Fixed Unable to delete a job that has a fstrigger Looks like this is fixed now. Thanks for the support! Change By: Jim Searle (14/Jun/12 9:58 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
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163815#comment-163815 ] Jim Searle commented on JENKINS-12176: -- Thanks for continuing to look into this. It seems that Jenkins is running the trigger multiple times, we have a lot of jobs using the file-trigger plugin, with a polling time of every minute... I guess we need to increase this polling time to avoid this? Poll @ 10:22:28 524 descriptors are open #5 $JENKINS_HOME/jobs/JOB_NAME/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 11 10:18:28 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) #98 $JENKINS_HOME/jobs/JOB_NAME/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 11 10:20:28 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) #280 $JENKINS_HOME/jobs/JOB_NAME/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 11 10:21:28 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) #370 $JENKINS_HOME/jobs/JOB_NAME/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 11 10:22:28 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) #404 $JENKINS_HOME/jobs/JOB_NAME/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 11 10:19:28 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Poll @ 10:26 #2 $JENKINS_HOME/jobs/JOB_NAME/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 11 10:24:28 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90)
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Searle reopened JENKINS-12176: -- The file handles plugin reports that it is coming from xtrigger: #4 /projects/brcm/bcg/jenkins/jobs/chip-import-cycloneA0-mem-memory_isb/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 04 17:25:00 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Unable to delete a job that has a fstrigger --- Key: JENKINS-12176 URL: https://issues.jenkins-ci.org/browse/JENKINS-12176 Project: Jenkins Issue Type: Bug Components: fstrigger Reporter: Jim Searle Assignee: Gregory Boissinot I have a fstrigger that polls every minute, and most of the time when I try to delete the job I get an error: java.io.IOException: Unable to delete /some/path/.nfs018e26ca00236d2f so I look at that file, and it contains the fstrigger polling log. If I disable the fstrigger, then I am able to delete the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Searle updated JENKINS-12176: - Component/s: xtrigger (was: fstrigger) Unable to delete a job that has a fstrigger --- Key: JENKINS-12176 URL: https://issues.jenkins-ci.org/browse/JENKINS-12176 Project: Jenkins Issue Type: Bug Components: xtrigger Reporter: Jim Searle Assignee: Gregory Boissinot I have a fstrigger that polls every minute, and most of the time when I try to delete the job I get an error: java.io.IOException: Unable to delete /some/path/.nfs018e26ca00236d2f so I look at that file, and it contains the fstrigger polling log. If I disable the fstrigger, then I am able to delete the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163515#comment-163515 ] Jim Searle edited comment on JENKINS-12176 at 6/5/12 7:57 PM: -- The file handles plugin reports that it is coming from xtrigger: #4 $JENKINS_HOM/jobs/$JOB_NAME/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 04 17:25:00 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) was (Author: jimsearle): The file handles plugin reports that it is coming from xtrigger: #4 /projects/brcm/bcg/jenkins/jobs/chip-import-cycloneA0-mem-memory_isb/trigger-polling-files.log by thread:Jenkins cron thread on Mon Jun 04 17:25:00 PDT 2012 at java.io.FileOutputStream.init(FileOutputStream.java:181) at java.io.FileOutputStream.init(FileOutputStream.java:131) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:97) at hudson.util.StreamTaskListener.init(StreamTaskListener.java:90) at org.jenkinsci.lib.xtrigger.AbstractTrigger.run(AbstractTrigger.java:130) at hudson.triggers.Trigger.checkTriggers(Trigger.java:259) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:207) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Unable to delete a job that has a fstrigger --- Key: JENKINS-12176 URL: https://issues.jenkins-ci.org/browse/JENKINS-12176 Project: Jenkins Issue Type: Bug Components: xtrigger Reporter: Jim Searle Assignee: Gregory Boissinot I have a fstrigger that polls every minute, and most of the time when I try to delete the job I get an error: java.io.IOException: Unable to delete /some/path/.nfs018e26ca00236d2f so I look at that file, and it contains the fstrigger polling log. If I disable the fstrigger, then I am able to delete the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163523#comment-163523 ] Jim Searle commented on JENKINS-12176: -- What about: lsof | grep 'trigger-polling-files.log' But that doesn't show anything for me either... But this currently shows 603 lines for me: ls -la /proc/5498/fd | grep trigger-polling-files.log where 5498 is the jenkins process id, and I don't have 603 jobs using fstrigger. I see a duplicates for some jobs. Actually, I was looking at the duplicates, I didn't look at every one, but those that I did look at, the job is disabled! The trigger-polling-files.log says: The job is not buildable. Activate it to poll again. Hopefully that will help you debug? Sorry my responses are slow, but for some reason jira is not notifying me of comments, so I have to keep checking. Unable to delete a job that has a fstrigger --- Key: JENKINS-12176 URL: https://issues.jenkins-ci.org/browse/JENKINS-12176 Project: Jenkins Issue Type: Bug Components: fstrigger Reporter: Jim Searle Assignee: Gregory Boissinot I have a fstrigger that polls every minute, and most of the time when I try to delete the job I get an error: java.io.IOException: Unable to delete /some/path/.nfs018e26ca00236d2f so I look at that file, and it contains the fstrigger polling log. If I disable the fstrigger, then I am able to delete the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163528#comment-163528 ] Jim Searle commented on JENKINS-12176: -- It's a UNIX thing, there is a directory in /proc for each process id, and /proc/pid/fd contains a list of all files opened by that pid. Sorry, I don't know OSX at all... I was following the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+too+many+open+files+error Can you see anything in the code where if a job is disabled it might not close the file? Unable to delete a job that has a fstrigger --- Key: JENKINS-12176 URL: https://issues.jenkins-ci.org/browse/JENKINS-12176 Project: Jenkins Issue Type: Bug Components: fstrigger Reporter: Jim Searle Assignee: Gregory Boissinot I have a fstrigger that polls every minute, and most of the time when I try to delete the job I get an error: java.io.IOException: Unable to delete /some/path/.nfs018e26ca00236d2f so I look at that file, and it contains the fstrigger polling log. If I disable the fstrigger, then I am able to delete the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12176) Unable to delete a job that has a fstrigger
[ https://issues.jenkins-ci.org/browse/JENKINS-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Searle reopened JENKINS-12176: -- We are debugging a too many open files issue, and following the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+too+many+open+files+error I do a: ls -la /proc/2141/fd on our jenkins machine, and it looks like every single job that uses the fstrigger keeps it's log file open all the time: /jenkins_home/jobs/job_name/trigger-polling-files.log Unable to delete a job that has a fstrigger --- Key: JENKINS-12176 URL: https://issues.jenkins-ci.org/browse/JENKINS-12176 Project: Jenkins Issue Type: Bug Components: fstrigger Reporter: Jim Searle Assignee: Gregory Boissinot I have a fstrigger that polls every minute, and most of the time when I try to delete the job I get an error: java.io.IOException: Unable to delete /some/path/.nfs018e26ca00236d2f so I look at that file, and it contains the fstrigger polling log. If I disable the fstrigger, then I am able to delete the job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162842#comment-162842
]
Jim Searle commented on JENKINS-13114:
--
Yes, we had the same issue, but discovered that it works in Internet Explorer...
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161245#comment-161245
]
Jim Searle commented on JENKINS-13114:
--
Same problem with Jenkins 1.458. It works in IE 7.0, FF 3.6. Fails in FF 11.0
and Chrome 18.0.
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
[JIRA] (JENKINS-13198) Saving jenkins config with dropdown views plugin causes json error
[
https://issues.jenkins-ci.org/browse/JENKINS-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161246#comment-161246
]
Jim Searle commented on JENKINS-13198:
--
Should this be closed as a duplicate to
https://issues.jenkins-ci.org/browse/JENKINS-13114 ?
Saving jenkins config with dropdown views plugin causes json error
--
Key: JENKINS-13198
URL: https://issues.jenkins-ci.org/browse/JENKINS-13198
Project: Jenkins
Issue Type: Bug
Components: core, dropdown-viewstabbar
Environment: jenkins 1.456
dropdown views tabbar plugin (latest)
Reporter: Marc Robinson
Assignee: jieryn
Status Code: 500
Exception:
Stacktrace:
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[ws.albors.CountJobsViewsTabBar,hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
at
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
at
hudson.views.ViewsTabBar$GlobalConfigurationImpl.configure(ViewsTabBar.java:84)
at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2620)
at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
at
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
at
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
[JIRA] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Jim Searle created JENKINS-13348: Summary: EnvInject overriding WORKSPACE variable Key: JENKINS-13348 URL: https://issues.jenkins-ci.org/browse/JENKINS-13348 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Reporter: Jim Searle Assignee: gbois Priority: Blocker I upgraded Jenkins to 1.458 and envinject from 1.36 to 1.44. After the upgrade all my jobs that did not use envinject were getting their WORKSPACE variable set to another jobs that did use envinject WORKSPACE. Downgraded envinject to 1.36 and the problem went away. Here's an edited log that shows initially the workspace is correct, even after EnvInject line, but when the shell script runs, it is wrong. Also, I don't know why EnvInject is even being run for this job since it is not enabled anywhere... [EnvInject] - Preparing an environment for the build. Building on master in workspace --correct-workspace-- Updating http://svn At revision 36652 no change for http://svn since the previous build No emails were triggered. [bronze-bin] $ /bin/sh -xe /tmp/hudson6983282044770433158.sh + echo --some-other-jobs-workspace-- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13348) EnvInject overriding WORKSPACE variable
[ https://issues.jenkins-ci.org/browse/JENKINS-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161262#comment-161262 ] Jim Searle commented on JENKINS-13348: -- Thanks. I am sure... I will try something on our test server and get back to you. EnvInject overriding WORKSPACE variable --- Key: JENKINS-13348 URL: https://issues.jenkins-ci.org/browse/JENKINS-13348 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Reporter: Jim Searle Assignee: gbois Priority: Blocker I upgraded Jenkins to 1.458 and envinject from 1.36 to 1.44. After the upgrade all my jobs that did not use envinject were getting their WORKSPACE variable set to another jobs that did use envinject WORKSPACE. Downgraded envinject to 1.36 and the problem went away. Here's an edited log that shows initially the workspace is correct, even after EnvInject line, but when the shell script runs, it is wrong. Also, I don't know why EnvInject is even being run for this job since it is not enabled anywhere... [EnvInject] - Preparing an environment for the build. Building on master in workspace --correct-workspace-- Updating http://svn At revision 36652 no change for http://svn since the previous build No emails were triggered. [bronze-bin] $ /bin/sh -xe /tmp/hudson6983282044770433158.sh + echo --some-other-jobs-workspace-- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13022) EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
Jim Searle created JENKINS-13022: Summary: EnvInject 1.33 doesn''t seem to work with Jenkins 1.454 Key: JENKINS-13022 URL: https://issues.jenkins-ci.org/browse/JENKINS-13022 Project: Jenkins Issue Type: Bug Components: envinject Reporter: Jim Searle Assignee: gbois I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not being set. I downgraded envinject to 1.31 and it worked again. I'm using Prepare an environment for the job Properties Content section and have Keep Jenkins Environment Variables and Keep Jenkins Build Variables enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12924) FSTrigger triggers builds on jenkins restart
[ https://issues.jenkins-ci.org/browse/JENKINS-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159978#comment-159978 ] Jim Searle edited comment on JENKINS-12924 at 3/8/12 12:27 AM: --- This is with version 0.29: Polling started on Mar 7, 2012 4:16:51 PM Polling for the job ... Searching a node to run the polling for the label '...'. Polling remotely on ... Checking one file: '...'. Slave(s) were offline at startup. Waiting for next schedule to check if there are modifications. Checking one file: '...'. The file didn't exist for the previous polling and now it exists. Polling complete. Took 0.7 sec. Changes found. Scheduling a build. was (Author: jimsearle): Polling started on Mar 7, 2012 4:16:51 PM Polling for the job ... Searching a node to run the polling for the label '...'. Polling remotely on ... Checking one file: '...'. Slave(s) were offline at startup. Waiting for next schedule to check if there are modifications. Checking one file: '...'. The file didn't exist for the previous polling and now it exists. Polling complete. Took 0.7 sec. Changes found. Scheduling a build. FSTrigger triggers builds on jenkins restart Key: JENKINS-12924 URL: https://issues.jenkins-ci.org/browse/JENKINS-12924 Project: Jenkins Issue Type: Bug Components: fstrigger Reporter: Jim Searle Assignee: gbois I'm using FSTrigger 0.28, when I restart jenkins it kicked off all my jobs that were previously built. The log says: The file didn't exist for the previous polling and now it exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12888) Would like to have fstrigger show what file changed in the build cause
[ https://issues.jenkins-ci.org/browse/JENKINS-12888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159578#comment-159578 ] Jim Searle commented on JENKINS-12888: -- Thanks! I'll check this out today. Would like to have fstrigger show what file changed in the build cause -- Key: JENKINS-12888 URL: https://issues.jenkins-ci.org/browse/JENKINS-12888 Project: Jenkins Issue Type: Improvement Components: fstrigger Reporter: Jim Searle Assignee: gbois Priority: Minor I have a job that monitors a few files, currently fstrigger sets the build cause to: [FSTrigger] Triggered by a change to a file It would be nice if it said which file actually changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12888) Would like to have fstrigger show what file changed in the build cause
Jim Searle created JENKINS-12888: Summary: Would like to have fstrigger show what file changed in the build cause Key: JENKINS-12888 URL: https://issues.jenkins-ci.org/browse/JENKINS-12888 Project: Jenkins Issue Type: Improvement Components: fstrigger Reporter: Jim Searle Assignee: gbois Priority: Minor I have a job that monitors a few files, currently fstrigger sets the build cause to: [FSTrigger] Triggered by a change to a file It would be nice if it said which file actually changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12827) api should return the build number that was queued.
Jim Searle created JENKINS-12827: Summary: api should return the build number that was queued. Key: JENKINS-12827 URL: https://issues.jenkins-ci.org/browse/JENKINS-12827 Project: Jenkins Issue Type: New Feature Components: core Reporter: Jim Searle I second this. It would be really nice to see the actual build number created in the response somewhere when using the api build and buildWithParameters calls. We can try to figure it out based on the nextBuildNumber, plus parsing through the queue/api/xml output, but it is not guaranteed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
