New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decouple JobHelper as a standalone project #7

Open

Andrey9kin opened this issue Apr 18, 2016 · 1 comment

Labels

Prio 3 - could have Size 2 - medium Status - workable

Milestone

Contributor

Andrey9kin commented Apr 18, 2016

Idea is to decouple JobHelper to a separate project so it could be reused by more instances of Jenkins without inheriting JenkinsAsCodeReference

In this way JobHelper will be built as an artifact, deployed to maven central and could be picked as a binary dependency using grab

Andrey9kin added Action - needs grooming Prio 3 - could have Size 4 - too big labels

Andrey9kin added Size 2 - medium Status - workable and removed Action - needs grooming Size 4 - too big labels

Contributor Author

Andrey9kin commented May 30, 2016

Already move to the https://github.com/Praqma/jobdsl-helpers
What is left is to setup deployments to the maven central

lakruzz modified the milestone: Backlog

ewelinawilkosz mentioned this issue

Use offical pretested integration jobdsl support instead of configure block #1

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment