Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend the version check to the tailored jira servicedesk version #383

Merged
merged 3 commits into from
Jul 6, 2021

Conversation

diLLec
Copy link
Contributor

@diLLec diLLec commented Jun 15, 2021

Pull Request (PR) description

The current version check does not take the JIRA servicedesk package into account. This package has an other versioning schema - see here: https://www.atlassian.com/de/software/jira/service-management/download-archives

This Pull Request (PR) fixes the following issues

Currently, if the following parameters are choosen to init the jira class, the output shows

JIRA versions older than 8.0.0 are no longer supported. Please use an older version of this module to upgrade first

class { 'jira':
    #
    # JIRA parameters
    version   => '4.17.0',
    product  => 'servicedesk',
...

@oranenj
Copy link
Contributor

oranenj commented Jun 25, 2021

@diLLec the change breaks if someone is installing "jira-core". I confess I don't know if that's even a valid option anymore, but you need to add it to the enum or return it to a string and then fix the version comparison logic to take that into account.

Copy link
Contributor

@oranenj oranenj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above comment

@diLLec
Copy link
Contributor Author

diLLec commented Jun 29, 2021

Thanks @oranenj - I've added that option and the tests seam to be succeeding now.

@oranenj
Copy link
Contributor

oranenj commented Jun 29, 2021

@diLLec you don't need to check for "jira" in the conditional. Doing that changes behaviour for jira-core since previously the version check was for any software.

I think in order for this not to be a breaking change you need to check for != "servicedesk". Strictly speaking making the String into an Enum is a breaking change too, but if all actually existing choices are enumerated then it should be fine. (there's jira, jira-core and servicedesk, but is that all?)

With these changes, the issue can be fixed without breaking the API.
My brain was in C mode somehow.
@oranenj
Copy link
Contributor

oranenj commented Jul 6, 2021

I made the changes directly from Github, I think this should be good enough to fix the issue and not break API.

@oranenj oranenj merged commit 6440f52 into voxpupuli:master Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants