Version 8.1.0?

[smk508]

I noticed that version 8.1.0 is no longer available, and also the latest tag now points to an older version of Jira. Is there any way to get the 8.1.0 image back?

[bobswift]

I noticed the CI builder says: Updated Atlassian JIRA Software master branch to latest version 8.1.0. So, it would seem CI builder knows about 8.1.0 from Atlassian at least.

[perlan]

Looks like JIRA_VERSION was updated but Dockerfile is still fetching atlassian-jira-software-7.13.3.tar.gz. This seems a little brittle and would probably be fixed by PR #56.

[smk508]

Also the CircleCI builder keeps reverting master to 7.13 after trying to upgrade to 8.1. It just did it again yesterday.

[perlan]

Yes, It seems like the bin/prepare script is not working correctly. It will always pick the last entry for the tar file (the opposite to the comment in the file) and update the JIRA_VERSION back and forth between the two available versions. My guess is that previously, it has been only one entry in the Atlassian response.

[perlan]

The version feed is now back to just single jira version (8.1.0) so the latest build is back to using 8.1.0. The problem in bin/prepare is still there so it will break again the next time there are multiple versions in the version feed.

[smk508]

I think that atlassian considers 7.13.3 to be the 'long-term' version of Jira while 8.1 is the latest one, which is why the feed gives tars for both versions. So perhaps both of them should be built into separate branches?
Also, even though 8.1 is on master now, there isn't a separate branch for it like for the other Jira versions, so there's no way to pin to that version when pulling from Docker other than to pull latest.

Also, this is the line in the bash script that pulls the version feed and is causing issues for reference:

docker-atlassian-jira-software/bin/prepare

Line 25 in e2a08c4

curl -Ls 'https://my.atlassian.com/download/feeds/current/jira-software.json' | sed 's/downloads(\(.*\))/\1/g' | jq -r '.[] | select(.description | test("TAR\\.GZ Archive")) | ("" + .zipUrl + " " + .version)' | while read -r URL VERSION

[zoispag]

It is now done.

[blop]

https://hub.docker.com/r/cptactionhank/atlassian-jira/tags
https://hub.docker.com/r/cptactionhank/atlassian-jira-software/tags

Still no sign of the 8.1+

[zoispag]

@blop maybe not explicitly tagged, but it is there.

I am using latest: cptactionhank/atlassian-jira-software:latest

[blop]

Using ":latest" in production configurations is not recommended :
https://vsupalov.com/docker-latest-tag/

[viceice]

https://hub.docker.com/r/cptactionhank/atlassian-jira/tags
https://hub.docker.com/r/cptactionhank/atlassian-jira-software/tags

Still no sign of the 8.1+

at least jira software 8.1.0 is finally there

[cptactionhank]

As long as the feed (https://my.atlassian.com/download/feeds/current/jira-software.json) does not contain any later version, this will not have that either.

You could push Atlassian for updating their feed.

[blop]

https://my.atlassian.com/download/feeds/current/jira-software.json -> JIRA 8.2.1
cptactionhank/atlassian-jira-software:8.2.1 not found: manifest unknown: manifest unknown

Maybe it's the same issue ?

[loneken79]

As a workaround you can pull the latest images and tag it localy, so you can use it in your process.

Assuming the latest commit is refering to the desired tag update (8.3.0 actually) the commands are:

1. docker pull cptactionhank/atlassian-jira-software (get "latest" version of the image)
2. docker tag cptactionhank/atlassian-jira:latest cptactionhank/atlassian-jira:8.3.0 (tag this image locally)
3. check that you see both "latest" and "8.3.0" version with the same "Image ID" in docker images | head listing
4. docker rmi cptactionhank/atlassian-jira:latest (clean unused "latest" version)