-
Task
-
Resolution: Fixed
-
Critical
-
-
Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4, Blue Ocean 1.1
Ideally the publishing of the blueocean-plugin multimodule would be moved to a (parametrised?) job on ci.jenkins.io, or some "standard and secure" location so published can be performed on demand by multiple users.
This may involve a release branch, or a parametrised job, not sure. We need to find out what the "standard" process is (if there is one).
I think we can't use dogfood as it is not a "trusted" environment for credentials, due to it running frequently updated and experimental versions of itself. Publishing should be like the official docker image which is published on jenkins.io secure infrastructure. (need to talk to KK about best way for this).
In scope:
- A jenkins setup to host deployments that is "trusted"
- github token and settings.xml to allow deployment
- A pipeline to allow parametrised deployment from a given branch usign batch mode mvn release:prepare release:deploy