|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Agreed
Can you point me to this "advanced project option"? I have been unable to locate any option that effectively disables this behavior, advanced or not. Perhaps it's too well hidden![]()
Possibly for small projects, or projects that are relatively well structured. Large projects, with code written decades ago with varying degrees of "cleanliness" are not so easily managed.
Doing so would require me to do all of my own artifact management, thus defeating the purpose of using Jenkins in the first place, but may be worth considering.
Interesting suggestion. If I could create a scheduled task that could trigger when changes were made to a source-code repository, I would consider that approach, but so far as I can tell this is not possible. The closest thing would be to have a task scheduled to run every minute, which I'm not sure would work so well on Windows.![]()
For future reference, can you give me more details of where this 'jenkinsci-users' list is, or where the 'appropriate' venue for this discussion would be?