I've been working on fully automating deployment of our test instance from backups of production and one of the crucial steps is turning off the email puller and the email processor.
I currently am doing this as an api call after the instance goes up but would really prefer to turn it off through the db. As I'm making a number of changes in the db to turn a production clone into a test environment already this would make life easier.
Any help would be greatly appreciated.
Location in UI: /secure/admin/GlobalMailSettings.jspa
Actually, no, you should minimise database change as much as possible.
You can kill off most email access by amending the setenv.sh file in the bin directory of the test install. See https://confluence.atlassian.com/adminjiraserver073/restoring-data-861253828.html#RestoringData-1.Disablingemailsending/receiving
Thanks for this, but as mentioned I am already doing a bunch of db changes in my script - changing the base URL, site name etc - and would prefer to make one more update than do something else. I'm sure its changing a one to a zero somewhere in there.
I'm already doing it through the api but would prefer to turn the pullers and processors off before jira boots up.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event