Jira tasks system for tests must be able to start fully automated

[buep]

In #19 we tried to find a way to start a Jira Software server in a fully automated way so we could use it for integration tests.

We didn't success complete as Jira do not support unattended installation - the problem is the initial Jira Setup Wizard. There is a lot of details in #19 about the research we done, and the temporary solution we created.

Problems with current solution is

• we are using a committed container, where we manually configured the server first time with Jira Setup Wizard and saved the container state - so you need to trust our work log to know what's in there.
• License expire May 15 2016 (we can't publish our Jira developer license, so we use a evaluation license)
• Test data was imported in the container - we don't import or create them during tests.

  Requirements for a valid solution

• fully automated
• must take all Jira Setup Wizard inputs from a configuration file or as input to the scripts
• importing test data somehow must be supported

  Try Selenium

I have one idea, that I think we should try as a first proof-of-concept. Try using Selenium, and write a test that takes parameters as input and fill out the Jira Setup Wizard. That would be a good solution - then we can just start and use the https://hub.docker.com/r/blacklabelops/jira/ Jira image and auto configure it every time we start a new.

We could write a test data import the same way.

Atlassian support couldn't help us

We filed a request to Atlassian support (we are Atlassian Experts), but they couldn't help and they do not support any such fancy things as fully automated installation ;-)

My reference is: https://support.atlassian.com/servicedesk/customer/portal/20/GHS-39047

References

• Generating test data for Jira very easy: http://jumble.expium.com/
• Spinning up Atlassian products for plugin development to their products: https://developer.atlassian.com/docs/getting-started/writing-and-running-plugin-tests/create-test-data-and-a-test-fixture
• One of the ugly hack to get through the Jira Setup Wizard: https://answers.atlassian.com/questions/14812734/automating-jira-installation-without-going-through-the-wizard

[buep]

Current solution:

• https://github.com/Praqma/Praqmatic-Automated-Changelog/blob/master/README.md#integration-tests-for-supported-tasks-systems
• https://github.com/Praqma/Praqmatic-Automated-Changelog/tree/master/test/resources/jira-env

[buep]

Interesting input from @hoeghh:

Hi,

Heres the project that automates the wizard for atlassian products.

My thought was, that we made something simular, containerzied, and then run that in Staci as a final step.

https://github.com/Adaptavist/avst-wizard

But someone needs to figure out how they do it.

[buep]

Relates to something we did ourselves for Staci: https://github.com/Praqma/jira_auto_import

[MadsNielsen]

Probably not going to be possible, since Fogcreek no longer offers a self hosted solution.

[buep]

What do Fogcreek have to do with Atlassian ?

[buep]

Anyway, even though Fogbugz can be put in a container, we could have an instance that we use the API against though. But that is another issue - this is only related to Jira.

[buep]

@hoeghh demoed yesterday a new feature in staci that allow one to restore from backup a full jira and spin it up ready to use. That could also be a possible way fix the licensing problem.

Challenge are we can't inject license, as it needs to be in file. Injecting it would mean on command line a parameter, so we can hide the secret on our Jenkins system. Further we would have to have a backup of an empty system, done manually, but that could also be okay.

[buep]

https://github.com/Praqma/Praqmatic-Automated-Changelog/issues/35#issuecomment-236580037

jira_auto_import does not exist anymore, that became the feature in staci.

[buep]

Renewing licenses again - see #67

[buep]

Still relevant for PAC 2.0x