Skip to content

atlassian: new releases, bamboo 13 (jdk25); zabbix 8.0 LTS - #196

Open
stamepicmorg wants to merge 2 commits into
masterfrom
develop
Open

stamepicmorg wants to merge 2 commits into
masterfrom
develop

Conversation

@stamepicmorg

Copy link
Copy Markdown
Member

Atlassian - new releases from the feeds, generated with bin/ansible:

  • jira 9.12.42 / 10.3.27 / 11.3.13; confluence 9.2.27 / 10.2.20 / 11.0.1; bitbucket 9.4.27 / 10.2.9 / 10.5.2; crowd 7.2.6; fisheye-crucible 4.9.16; bamboo 10.2.26 / 12.1.13; mesh 3.4.21 / 4.2.6 / 4.6.1
  • bamboo 13 line on jdk25 (13.0.1 = latest; Java 25 only per Atlassian supported platforms): role task + jdk25 templates + workflow atlassian.bamboo.13.yml + README row. Built locally, server starts (HTTP 302 to setup).
  • atlassian-versions-update.py: EXCLUDE list (crowd 1.4.8 has no standalone tarball, was re-added by the feed); latest.txt never steps back (current feed listed only LTS lines: bitbucket 10.2.9 / mesh 3.4.21 would have replaced 10.5.x / 4.6.x).

Zabbix 8.0 LTS - linux/advanced/zabbix/8.0, all ten components FROM zabbix/:8.0-ubuntu-latest (Ubuntu resolute, same as 7.4), same additions; README tables via readme-sync. agent2 and server-pgsql built locally (Zabbix 8.0.0).

readme-sync --check and oci-labels-sync --check clean.

Atlassian (bin/python/atlassian-versions-update.py + bin/ansible generation):
jira 9.12.42 / 10.3.27 / 11.3.13, confluence 9.2.27 / 10.2.20 / 11.0.1,
bitbucket 9.4.27 / 10.2.9 / 10.5.2, crowd 7.2.6, fisheye-crucible 4.9.16,
bamboo 10.2.26 / 12.1.13, mesh 3.4.21 / 4.2.6 / 4.6.1. New bamboo 13 line
(13.0.1, latest) on jdk25 - Java 25 only per Atlassian supported platforms;
built and started locally. The update script gets an EXCLUDE list (crowd
1.4.8, WAR only) and keeps latest monotonic (the current feed listed only
LTS lines for bitbucket / mesh).

Zabbix 8.0 LTS: all ten components FROM zabbix/<component>:8.0-ubuntu-latest,
same additions as 7.4; agent2 and server-pgsql built locally (8.0.0).
initdb flags follow the old cluster (checksums via pg_controldata, -k;
18 enables checksums by default), alternative init via epicmorg/postgres
with the same POSTGRES_INITDB_ARGS, one mount for --link/--clone (EXDEV),
-w /tmp for the sockets, clean stop of the old container.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant