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

[Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>]

Note that both GitHub Pull Request and Environment Injector Plugin are installed by default in all provided Jenkins instances.

Cheers,

Mikaël Barbero 

Team Lead - Release Engineering | Eclipse Foundation

📱 (+33) 642 028 039 | 🐦 @mikbarbero

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Le 14 sept. 2018 à 05:05, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> a écrit :

On 14 September 2018 at 13:03, Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

Currently I did not use it in my jobs on eclipse.org where I'm trying to do everything in the shell script because it's better readable.

But I have several jobs where it helps:

- Shell step prepares environment, counts versions, etc. and stored version numbers and other things are passed to maven step which calls release plugin.

Thanks Tomas, I will consider whether that would be useful in the project I am looking to add the pipeline for.

Tomas

Dne 14/09/18 v 13:53 Tom Jenkinson napsal(a):

On 14 September 2018 at 12:51, Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

Dne 14/09/18 v 13:11 Tom Jenkinson napsal(a):

On 14 September 2018 at 10:56, Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

Hi Tom,

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

I guess that is to tag the release right? 

Yes, this is for github push.

Another plugins that may be helpful are:

 - GitHub Pull Request Builder

 - Environment Injector Plugin

What do you use this bit for?

GitHub Pull Request Builder: Can build incomming PR reuests
Environment Injector Plugin: Stores shell script variables and allows to use them by other build/postbuild steps

Sorry, I wasn't clear in my question. I was speaking specifically to the Environment Injector Plugin - what kind of variables might need to be passed between the steps? 

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

_______________________________________________
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

_______________________________________________
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

_______________________________________________
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

Attachment: signature.asc
Description: Message signed with OpenPGP