On Wed, May 15, 2019 at 8:56 PM Kenneth Knowles <[EMAIL PROTECTED]> wrote:
So something as Multibranch Pipeline [https://jenkins.io/doc/book/pipeline/multibranch/
] and some integration
with GitHub [ https://plugins.jenkins.io/github-branch-source
that seems to address this issue. Of course we would need to investigate in
how that will align with our current workflow, but seems worth a look.
Docker could certainly be of help here. And there have been some proposals
how to address docker in docker. Maybe some sidecar approach [https://jenkins.io/doc/book/pipeline/docker/
] could also help.
But for the time being, as far a I understand we do/should have some
configuration files for Jenkins agent setup (some playbook). Are those
under VCS? Could not find that in our beam repo. Is it possible to link
with our releases or will it be sufficient to align by 'date', as change
rate is probably rather low on that configuration? Who currently owns that