# Improovements made to JenkinsPipelineUnit in a Work setting

**URL:** <https://community.jenkins.io/t/improovements-made-to-jenkinspipelineunit-in-a-work-setting/35525>\
**Category:** Contributing\
**Tags:** question\
**Created:** [August 29, 2025, 10:11am UTC](https://community.jenkins.io/t/improovements-made-to-jenkinspipelineunit-in-a-work-setting/35525 "2025-08-29T10:11:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ggarcia24](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/ggarcia24/32/16751_2.png) [@ggarcia24](https://community.jenkins.io/u/ggarcia24)\
**Post date:** [August 29, 2025, 10:11am UTC](https://community.jenkins.io/t/improovements-made-to-jenkinspipelineunit-in-a-work-setting/35525/1 "2025-08-29T10:11:26Z")

</div>

Hello!

I’m working for a company that’s using JenkinsPipelineUnit to write unit tests for the share libraries we are developing, as part of using the library for a while we made some changes and we want to contribute those to the project. But it’s not clear for me yet _how_ to do that, Is it required (for me or the company) to sign the contributor agreement? The [project goverance page](https://www.jenkins.io/project/governance/) wording it’s a bit confusing for me, but it seems to say that because this is NOT jenkins core it’s not, but if someone can clarify that it will be awesome.

I’ve tried to contact the maintainers in Gitter/Matrix a while ago but it seems that the chat is no longer used, so I was wondering if maybe there’s another place we I could contact them? Some of the changes add new features and some are code clean up / improvements to how the library works and some are just to make it a bit more easy to use. I’m not sure if it’s “better” to split all the changes into issues and create several pull requests or if perhaps the maintainers have a different preference

Hoping some one can offer some guidance

Best regards  
Gonzalo G.

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [August 29, 2025, 11:13pm UTC](https://community.jenkins.io/t/improovements-made-to-jenkinspipelineunit-in-a-work-setting/35525/2 "2025-08-29T23:13:12Z")

</div>

> [@ggarcia24](#):
>
> But it’s not clear for me yet _how_ to do that, Is it required (for me or the company) to sign the contributor agreement?

A contributor license agreement is not required for plugin pull requests. You are welcome to submit a contributor license agreement if you wish. The Jenkins projects uses EasyCLA from the Linux Foundation. Refer to the [instructions for submitting a contributor license agreement](https://github.com/jenkinsci/infra-cla?tab=readme-ov-file#how-to-submit-a-cla).

> [@ggarcia24](#):
>
> I’m not sure if it’s “better” to split all the changes into issues and create several pull requests or if perhaps the maintainers have a different preference

I’m not a maintainer of JenkinsPipelineUnit, but there is a consistent preference for smaller pull requests in all the repositories that I’ve watched. You’re safest if you use several pull requests.