Skip to content
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.

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

Suspend Confluence Publisher plugin due to closed source dependency #3856

Closed
basil opened this issue Dec 10, 2023 · 8 comments · Fixed by jenkins-infra/update-center2#756
Closed

Comments

@basil
Copy link
Collaborator

basil commented Dec 10, 2023

Service(s)

Update center

Summary

The Confluence Publisher plugin is using dependencies that are closed source and are not licensed with an OSI-approved open source license. The Jenkins project governance document and the hosting page state that we deliver plugins with open source licenses.

We should suspend distribution of the Confluence Publisher plugin.

The specific license of concern is:

From the /plugin/confluence-publisher/wrapper/thirdPartyLicenses page of a Jenkins installation that includes the Confluence Publisher plugin:

Using the Atlassian Customer Agreement:

  • com.atlassian.confluence:confluence-java-api:7.14.0
  • com.atlassian.confluence:confluence-rest-client:7.14.0
  • com.atlassian.confluence:confluence-rest-serialization:7.14.0
  • com.atlassian.confluence:confluence-rest-api:7.14.0

Reproduction steps

  1. Install Jenkins 2.426.1 (or any other recent Jenkins version).
  2. Install the Confluence Publisher plugin.
  3. Open the /plugin/confluence-publisher/wrapper/thirdPartyLicenses URL and confirm the abovementioned license is visible.
@basil basil added the triage Incoming issues that need review label Dec 10, 2023
Copy link

Take a look at these similar issues to see if there isn't already a response to your problem:

  1. 83% Suspend Crowd2 integration plugin due to closed source dependency #3854

@MarkEWaite
Copy link

MarkEWaite commented Dec 11, 2023

I've sent an email message to the maintainers of the plugin with a copy to the Jenkins board. The maintainers are:

@NotMyFault
Copy link
Member

Approved.

@dduportal dduportal added this to the infra-team-sync-2023-12-12 milestone Dec 11, 2023
MarkEWaite added a commit to MarkEWaite/update-center2 that referenced this issue Dec 11, 2023
* Suspend Confluence publisher plugin distribution - uses closed source dependency

jenkins-infra/helpdesk#3856 explains that the
Confluence publisher plugin uses a dependency that is not open source
licensed.

The Confluence publisher libraries are Atlassian licensed including:

* com.atlassian.confluence:confluence-java-api:7.14.0
* com.atlassian.confluence:confluence-rest-client:7.14.0
* com.atlassian.confluence:confluence-rest-serialization:7.14.0
* com.atlassian.confluence:confluence-rest-api:7.14.0

The Atlassian license is not an open source license.  Refer to
https://www.atlassian.com/legal/software-license-agreement for the
details of the license.

https://www.jenkins.io/project/governance/#license says that the Jenkins
project requires plugins that it distributes to be open source, including
their dependencies.  When a closed source dependency is detected in a
plugin, we suspend distribution of that plugin.  If maintainers update
the plugin to remove the closed source dependency, distribution can
begin for the new release that removes the closed source dependency.

Fixes jenkins-infra/helpdesk#3856
@basil
Copy link
Collaborator Author

basil commented Dec 11, 2023

I've submitted a documentation pull request to the Confluence Publisher plugin repository explaining why it will be suspended:

daniel-beck pushed a commit to jenkins-infra/update-center2 that referenced this issue Dec 12, 2023
* Suspend Confluence publisher plugin distribution - uses closed source dependency

jenkins-infra/helpdesk#3856 explains that the
Confluence publisher plugin uses a dependency that is not open source
licensed.

The Confluence publisher libraries are Atlassian licensed including:

* com.atlassian.confluence:confluence-java-api:7.14.0
* com.atlassian.confluence:confluence-rest-client:7.14.0
* com.atlassian.confluence:confluence-rest-serialization:7.14.0
* com.atlassian.confluence:confluence-rest-api:7.14.0

The Atlassian license is not an open source license.  Refer to
https://www.atlassian.com/legal/software-license-agreement for the
details of the license.

https://www.jenkins.io/project/governance/#license says that the Jenkins
project requires plugins that it distributes to be open source, including
their dependencies.  When a closed source dependency is detected in a
plugin, we suspend distribution of that plugin.  If maintainers update
the plugin to remove the closed source dependency, distribution can
begin for the new release that removes the closed source dependency.

Fixes jenkins-infra/helpdesk#3856
@MarkEWaite
Copy link

Closing as complete because the pull requests have been merged:

Confirmed that the updates.jenkins.io/latest is no longer listing confluence-publisher as a distributed plugin. Confirmed with my local Jenkins controller that confluence-publisher was listed in the update center from 18 hours ago and is no longer listed in the current update center.

Plugins site is not yet updated to show that the plugin is no longer distributed. I assume we'll need several more hours before it is visible there.

@dduportal dduportal removed the triage Incoming issues that need review label Dec 12, 2023
@amarjit25
Copy link

what is the alternate of confluence publisher plugin to push the jenkins build information to Confluence

@MarkEWaite
Copy link

what is the alternate of confluence publisher plugin to push the jenkins build information to Confluence

I think that you could contact Atlassian for their recommendations. try the Atlassian command line interface, or try the Confluence command line interface.

@amarjit25
Copy link

Thanks Mark

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

Successfully merging a pull request may close this issue.

5 participants