Liquibase Plugin and INFRA-2622

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Liquibase Plugin and INFRA-2622

Robert Reeves-2

Hi!

 

Regarding the blocker on releasing the fixed Liquibase Plugin, I wanted to start a conversation on releasing the plugin.

 

https://issues.jenkins-ci.org/browse/INFRA-2622

 

Please let me know your thoughts.

 

Thanks!

 

Robert

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ea5b1866-79c5-437c-af6d-86ad65f0de2c%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Liquibase Plugin and INFRA-2622

Oleg Nenashev
Hi Robert,

I confirm that there is a problem with the current library distribution, and that we could not distribute it as is according to the current Governance document. I am happy to bring up this topic at the today's governance meeting, but my personal recommendation is to consider technical solutions which would prevent bundling of the proprietary library in the plugin.

Did you consider suggestions by Daniel in the Infra ticket?

 Flyway is implemented as a tool installer, so the Jenkins project only distributes pure OSS:

https://github.com/jenkinsci/flyway-runner-plugin/blob/master/src/main/java/sp/sd/flywayrunner/installation/FlywayInstaller.java

Similar approaches were done in the past; a popular one for a while was to have an "installer" plugin, like https://github.com/jenkinsci/cloudbees-enterprise-plugins-plugin – then the only bits actually distributed by the Jenkins project are under an open source license.



Best regards,
Oleg 

On Thursday, May 28, 2020 at 3:45:31 PM UTC+2, Robert Reeves wrote:

Hi!

 

Regarding the blocker on releasing the fixed Liquibase Plugin, I wanted to start a conversation on releasing the plugin.

 

<a href="https://issues.jenkins-ci.org/browse/INFRA-2622" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FINFRA-2622\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGgpQG-0H7D8s0oZ9v0nKyKPR2B8g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FINFRA-2622\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGgpQG-0H7D8s0oZ9v0nKyKPR2B8g&#39;;return true;">https://issues.jenkins-ci.org/browse/INFRA-2622

 

Please let me know your thoughts.

 

Thanks!

 

Robert

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a03eb843-b329-4a68-87cb-fcfe7a3e15db%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Liquibase Plugin and INFRA-2622

Robert Reeves
We absolutely have! Thanks!

I would love for you to bring it up at the Governance meeting today. Would it be possible to resolve this at an agreed upon date and release it as is in the interim? If it isn't resolved by the agreed date, I would expect the plugin to be unpublished.

Please let me know the team's toughts!

Robert

On Wednesday, June 3, 2020 at 11:38:19 AM UTC-5, Oleg Nenashev wrote:
Hi Robert,

I confirm that there is a problem with the current library distribution, and that we could not distribute it as is according to the current Governance document. I am happy to bring up this topic at the today's governance meeting, but my personal recommendation is to consider technical solutions which would prevent bundling of the proprietary library in the plugin.

Did you consider suggestions by Daniel in the Infra ticket?

 Flyway is implemented as a tool installer, so the Jenkins project only distributes pure OSS:

<a href="https://github.com/jenkinsci/flyway-runner-plugin/blob/master/src/main/java/sp/sd/flywayrunner/installation/FlywayInstaller.java" rel="nofollow" style="color:rgb(53,85,100)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fflyway-runner-plugin%2Fblob%2Fmaster%2Fsrc%2Fmain%2Fjava%2Fsp%2Fsd%2Fflywayrunner%2Finstallation%2FFlywayInstaller.java\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEAz6lJ0THGrSY9iraJ2qdcg8-VYw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fflyway-runner-plugin%2Fblob%2Fmaster%2Fsrc%2Fmain%2Fjava%2Fsp%2Fsd%2Fflywayrunner%2Finstallation%2FFlywayInstaller.java\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEAz6lJ0THGrSY9iraJ2qdcg8-VYw&#39;;return true;">https://github.com/jenkinsci/flyway-runner-plugin/blob/master/src/main/java/sp/sd/flywayrunner/installation/FlywayInstaller.java

Similar approaches were done in the past; a popular one for a while was to have an "installer" plugin, like <a href="https://github.com/jenkinsci/cloudbees-enterprise-plugins-plugin" rel="nofollow" style="color:rgb(53,85,100)" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcloudbees-enterprise-plugins-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE7jcNbaRoO0CpNyrPBaZ-xzSqtnA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcloudbees-enterprise-plugins-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE7jcNbaRoO0CpNyrPBaZ-xzSqtnA&#39;;return true;">https://github.com/jenkinsci/cloudbees-enterprise-plugins-plugin – then the only bits actually distributed by the Jenkins project are under an open source license.



Best regards,
Oleg 

On Thursday, May 28, 2020 at 3:45:31 PM UTC+2, Robert Reeves wrote:

Hi!

 

Regarding the blocker on releasing the fixed Liquibase Plugin, I wanted to start a conversation on releasing the plugin.

 

<a href="https://issues.jenkins-ci.org/browse/INFRA-2622" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FINFRA-2622\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGgpQG-0H7D8s0oZ9v0nKyKPR2B8g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FINFRA-2622\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGgpQG-0H7D8s0oZ9v0nKyKPR2B8g&#39;;return true;">https://issues.jenkins-ci.org/browse/INFRA-2622

 

Please let me know your thoughts.

 

Thanks!

 

Robert

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7c34dd49-fe46-4e54-83ef-f69b74d5de75%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Liquibase Plugin and INFRA-2622

Oleg Nenashev
Hello Robert,

Unfortunately we did not get to this topic today at the meeting. The consensus is that we would be doing it in the mailing list. Unfortunately the meeting was already in progress when your response arrived, and we did not consider the interim solution. So let's keep discussing it here.

My IMHO: To be published on an interim basis, it would need an explicit sign-off from the Governance Board, Jenkins Security Officer, and a general consensus among participants of this thread. It would also need to comply with other criteria defined for hosting plugins.

Best regards,
Oleg


On Wed, Jun 3, 2020 at 8:40 PM Robert Reeves <[hidden email]> wrote:
We absolutely have! Thanks!

I would love for you to bring it up at the Governance meeting today. Would it be possible to resolve this at an agreed upon date and release it as is in the interim? If it isn't resolved by the agreed date, I would expect the plugin to be unpublished.

Please let me know the team's toughts!

Robert

On Wednesday, June 3, 2020 at 11:38:19 AM UTC-5, Oleg Nenashev wrote:
Hi Robert,

I confirm that there is a problem with the current library distribution, and that we could not distribute it as is according to the current Governance document. I am happy to bring up this topic at the today's governance meeting, but my personal recommendation is to consider technical solutions which would prevent bundling of the proprietary library in the plugin.

Did you consider suggestions by Daniel in the Infra ticket?

 Flyway is implemented as a tool installer, so the Jenkins project only distributes pure OSS:

https://github.com/jenkinsci/flyway-runner-plugin/blob/master/src/main/java/sp/sd/flywayrunner/installation/FlywayInstaller.java

Similar approaches were done in the past; a popular one for a while was to have an "installer" plugin, like https://github.com/jenkinsci/cloudbees-enterprise-plugins-plugin – then the only bits actually distributed by the Jenkins project are under an open source license.



Best regards,
Oleg 

On Thursday, May 28, 2020 at 3:45:31 PM UTC+2, Robert Reeves wrote:

Hi!

 

Regarding the blocker on releasing the fixed Liquibase Plugin, I wanted to start a conversation on releasing the plugin.

 

https://issues.jenkins-ci.org/browse/INFRA-2622

 

Please let me know your thoughts.

 

Thanks!

 

Robert

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/dRz1QP_ndPo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7c34dd49-fe46-4e54-83ef-f69b74d5de75%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBX8mb0rs78BdHgMVkqJhKxSkBoKXSKzCcqiBTh%3DeLm%3Dw%40mail.gmail.com.