Cheking in Script files to JiRA

[Vishwas]

Hi Team,

We have customized JIRA to highest extent based on the business needs. And we have 100's of Script files in Script Runner Plugin in QA and Prod.

We need to keep changing the script files very often. And It has become very difficult have lost track of the changes. Is there any suggested way we can manage the version control of Script files we have in the Script runner plugin?

Please suggest us a better way to manage the script files either with some version control Tool.

[Martin Bayer _MoroSystems_ s_r_o__]

Hi @Vishwas , welcome on the community, I think the easiest way is to track your scripts using BitBucket (or some other versioning platform). I really suggest you to use GitFlow workflow if you neet do track also releases (https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).

Then you need to have access to your Git repository on the QA and PROD server... release means only one command (git pull) on the server. Let me know if you need more information.

[Nic Brough -Adaptavist-]

Just to be clear, this needs you to use scripts off the disk, instead of inline scripts.  Source controlling scripts like this is exactly what the "run script from disk" was implemented for!

[Vishwas]

Hi @Nic Brough -Adaptavist-  

Could you explain in little more details as how use "scripts off the disk"? and how to "run script from the disk"? It would be useful. Any reference material?

@Martin Bayer _MoroSystems_ s_r_o__ 

Could you help me explore more have this setup for QA and Prod using GitFlow with some sample or any video's if you can refer me to any existing if present.

Thanks,

Vishwas

[Nic Brough -Adaptavist-]

When you go to look at a script that is in use somewhere (for example, workflow -> edit workflow -> transition -> post-function -> add/edit scripted post-function), you will see a load of fields for configuring the script. 

The main one is, of course, a text box to put the script in, but there is also another option - a simple string which asks for the path to a script to run on the disk.

[Martin Bayer _MoroSystems_ s_r_o__]

HI @Vishwas I think the documentation provides all the necessary information. Basically you need to have more branch types

• develop (main branch)
  • feature and release branches are created from it
  • pull request from feature branches are created against it
• master
  • this branch is released to PROD
  • hotfix branch is created from it if needed
• feature
  • it is created from develop branch
  • developer creates it for every feature/story/bug
• release
  • it is created from develop branch when all the necessary feature branches are merged to it
  • it is released to QA environment so features are tested against this code
  • bug fixes for a release are implemented in it

I hope it will help.

[Vishwas]

Thank you.