One fine morning. While zipping coffee on the couch, I made up my design. It is going to be a service that reads configuration data saved using Active Objects. Easy peasy. So I thought!
I wrote my service faster than I planned, looking at my own tutorial, compiled it and everything looked fine.
Ever thought of running scheduled tasks within JIRA? Why do we need scheduled tasks when we have the JIRA Services? We have seen how to write a service in one of the previous posts. But in spite of all its advantages discussed there, services have a disadvantage. It always starts when JIRA is restarted and runs at regular intervals after that. So if you have a service that do some heavy memory intensive operation and if you restart JIRA in the middle of the day, you will suddenly find your instance's performance compromised! If it is scheduled to run every 24 hours, you will find the same service running in the middle of the day from then on until the next restart.
Scheduled tasks in JIRA are a good way to make sure all such operations happen at quite times, midnight for example. In this post we will write a real simple scheduled tasks and see how easy that can be!
A service that runs at regular intervals is a much wanted feature in any web application. It is more so if it is one that can be managed with user configured parameters and without having to reboot etc. JIRA offers a mechanism to add new services on to it that runs at regular intervals after every start-up. It lets us do things related to JIRA and things independent of it. It lets us integrate with third party applications. It lets us do wonders!
There are built-in services in JIRA. Export Service, POP Service etc to name a few. Here we are going to see how we can add a custom service on to JIRA