Hi,
I'm relatively new to Confluence / Jira and i've been struggling to set up auto re-indexing of Jira. I was told by Confluence support to download the Confluence Command Line Interface plugin but haven't a clue how to implement this tool in CentOS. Isn't there perhaps a layman's how-to manual to show me the way? My background is Microsoft so...enough said
Regards
See this article: https://answers.atlassian.com/questions/92800/activating-jira-indexing-via-script
CLI is a commmand line interface. You will find lot of info, including installation, usage etc, here: https://bobswift.atlassian.net/wiki/display/JCLI/JIRA+Command+Line+Interface
On CentOS, you have shell script that you can run.
Thank you kindly sir
I've come across this post but what do i do with it? Obviously i have to add this to a file and point CLI to it. There isn't really set by step instruction to set this up:
https://confluence.atlassian.com/display/JIRACOM/Automating+JIRA+operations+via+wget?focusedCommentId=229839497#comment-229839497
You're getting confused.
The CLI is for making the remote functions easier to use when you're scripting outside.
The script you have found is a script for the sh shell. It's nothing to do with the CLI, you just run it on a Unix box. The "curl" command may need to be added, but all it does is log into Jira and click the "re index" button for you, without a browser.
They both hit Jira remotely (you can run them on any machine that can talk to your Jira), and they don't need a browser. But they're different methods.
Hi there,
There are so many customers enquiring about auto-indexing, why doesn't Atlassian just build their new Jira releases with auto-indexing built in?
There aren't actually many asking about it.
Having to re-index the whole system is unusual, and thinking "we should do this regularly" is simply patching over a problem you should really be trying to fix the root cause of.
From JIRA 6.1 onwards, it is possible to trigger a re-index via the REST API:
https://docs.atlassian.com/jira/REST/6.1/#d2e3239
However, any changes done to the plugins require you to perform a re-index on the machine which is not that practical when you have to perform the re-index when the employees leave the office. Performing a background index will decrease the perofrmance on the system... so that is not an option.
Correct, but adding an add-on that requires indexing should be something considered as system maintenance, and the indexing should be done manually by an admin when it is required and the users agree to the downtime. Not regular indexing.
I know that this is an old thread.
Just meaning to ask if it would be wise to trigger a scheduled re-index, via a cronjob as you have stated here.
My JIRA instance is of version 6.4.4 at the moment.
I have checked that the using the REST API has some caused some bugs, for example
Would it be better to trigger the re-index from the JIRA UI instead of through the REST API?.
Thanks,
Hi Alfie,
Although it is possible to schedule a period re-index, this operation should only be triggered when necessary (e.g. after changes that require a re-index).
The bug JRASERVER-63284 only affects Data Center installations.
Taking that into consideration, if you're running a Data Center version of JIRA, we'd recommend you to trigger the re-index via the UI instead. Otherwise, if you're on JIRA Software Server, either option should be fine.
Cheers
Hi Danilo,
Thank you for the reply, even though this is an old thread.
I understand, i will take note of what you have said.
Thank you
It looks like you're new here. Sign in or register to get started.
![Photo of Jobin Kuruvilla [Adaptavist]](https://us.v-cdn.net/6038660/uploads/avatars/17/c4/n17c4b8c7de7da6cee02bd69e8a3b017b.png)
