Releases via CI

[XoMEX]

It would be nice if releases would be done automatically via CI (Jenkins).
As of now releases are automatically pushed to our internal nexus repo.
To minimize the amount of work needed to do a public release, the CI on the public repos could also push new artifacts to maven central.

[XoMEX]

As further motivation: The TLS-Scanner 7.4.0 release is currently broken. An automated process would either reject such a release (preferred), or publish all dependencies.

[ERROR] Failed to execute goal on project tls-scanner-core: Could not resolve dependencies for project de.rub.nds.tls.scanner:tls-scanner-core:jar:7.4.0
[ERROR] dependency: de.rub.nds:asn1-attacker:jar:4.2.3 (compile)
[ERROR] 	Could not find artifact de.rub.nds:asn1-attacker:jar:4.2.3 in central (https://repo.maven.apache.org/maven2)
[ERROR] dependency: de.rub.nds:x509-attacker:jar:4.3.10 (compile)
[ERROR] 	Could not find artifact de.rub.nds:x509-attacker:jar:4.3.10 in central (https://repo.maven.apache.org/maven2)
[ERROR] dependency: de.rub.nds.tls.attacker:tls-core:jar:7.6.0 (compile)
[ERROR] 	Could not find artifact de.rub.nds.tls.attacker:tls-core:jar:7.6.0 in central (https://repo.maven.apache.org/maven2)
[ERROR] dependency: de.rub.nds.tls.attacker:transport:jar:7.6.0 (compile)
[ERROR] 	Could not find artifact de.rub.nds.tls.attacker:transport:jar:7.6.0 in central (https://repo.maven.apache.org/maven2)
[ERROR] dependency: de.rub.nds.tls.attacker:utils:jar:7.6.0 (compile)
[ERROR] 	Could not find artifact de.rub.nds.tls.attacker:utils:jar:7.6.0 in central (https://repo.maven.apache.org/maven2)
[ERROR] dependency: de.rub.nds.tls.dockerlib:tls-docker-library:jar:3.2.2 (test)
[ERROR] 	Could not find artifact de.rub.nds.tls.dockerlib:tls-docker-library:jar:3.2.2 in central (https://repo.maven.apache.org/maven2)

[XoMEX]

On that note: We should also create a CI step that validates that a public repo's main (or at least a release) is buildable without internal versions.