Re: [ee4j-build] Minimal common set of plugins for CI/CD pipelines?

[Werner Keil <werner.keil@xxxxxxxxx>]

While Travis is certainly optional, should build system fragmentation be reduced to those projects that really need both, or is it a common pattern recommended by those involved here and the PMC?

I am familiar with all 3 in plenty of projects both on GitHub or with customers, but rarely use multiple systems for one particular repository.

Werner

On Fri, Sep 14, 2018 at 11:57 AM Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

Hi Tom,

I'm usually requesting only SSH Agent plugin to pass key into shell environment.

Another plugins that may be helpful are:

 - GitHub Pull Request Builder

 - Environment Injector Plugin

But they are not mandatory. PR build can be done using Travis.

Tomas

Dne 14/09/18 v 10:22 Tom Jenkinson napsal(a):

As per https://github.com/eclipse-ee4j/jsonp/wiki/JSONP-release-job it recommends to request a list of Jenkins plugins a job needs.

Is there a minimal set of plugins that we know we have to request, for example something to do with the artifact upload or the source code repo type?

Thanks,

Tom

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build