Re: Job Not Triggering after Being Re-Enabled

2015-10-13 Thread Nick Lee
ste Mathus wrote: > Hi, > With seemingly bugs, it's generally better to provide your relevant > environment informations: jenkins & plugin versions, OS... > Is there anything about it in the logs when you reenable/before? > Thanks > > 2015-10-13 18:41 GMT+02:00 Nick Lee

Job Not Triggering after Being Re-Enabled

2015-10-13 Thread Nick Lee
I have a job that uses a periodic build trigger. I've set the trigger to "H/10 * * * *" -- basically, build every ten minutes. Now this works perfectly fine most of the time. However, if I disable the job for a long period of time (say, 30 minutes), then re-enable it, the build trigger won't re

Re: pathignore plugin help

2015-06-03 Thread Nick Lee
In case it helps, here's the console output too: Including paths matching patterns: ["d:\my_project_root\**"] No paths passed filter, skipping build. Changed paths: [] Skipped archiving because build is not successful No emails were triggered. Finished: NOT_BUILT It seems fishy to me that "Chan

pathignore plugin help

2015-06-03 Thread Nick Lee
I'm trying to set up a job that only triggers when files in certain directories have changed. I'm using Perforce SCM and have that set up properly to sync files. I've downloaded and installed the pathignore plugin. In the project configuration, I've enabled the "Do not build if only specified p

Setting up Template Workspace with P4 Plugin

2015-05-26 Thread Nick Lee
I'm trying to set up a build project using the P4 plugin in Jenkins. Specifically, I'm using the following Source Code Management settings: - Workspace Behavior: "Template" - Template workspace: "client-jenkins-template" - Workspace Name Format: "client-jenkins-${NODE_NAME}" Essential