Plugins hosted in svn

[Jesse Glick]

There are still a few plugins hosted in the Jenkins Subversion
repository. I am not sure if active changes are being made there.
Confusingly, when github.com/jenkinsci was created, we also mirrored
those subdirectories as Git repositories. Naturally people have since
then submitted GitHub PRs and in some cases pushed to the Git repo
while the Subversion repo was active, meaning the plugin is
effectively forked. This is a freaking mess.

I think we should simply abandon the Subversion repo, meaning creating
a new commit that deletes everything, and then removing write access,
and request plugin authors to use GitHub. If they insist on using
Subversion (and not via the bridge to Git), they can use some other
hosting site, but the plugin should not be considered “hosted on
jenkins-ci.org”.

Ideally some final check would be done for outstanding changes in svn
that did not make it into Git for whatever reason.

[Robert Sandell]

IIRC when the bridge was setup it was done so that when new content started to turn up on the github repo that was not in svn the svn -> github replication would stop.

/B

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0j2rsHcDmj1X%3DgBFo%2Bb0tKFkFF5DG7B45yyXor%2BYe5vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Robert Sandell

Software Engineer

CloudBees Inc.

[Jesse Glick]

On Wed, Apr 22, 2015 at 9:16 AM, Robert Sandell <rsan...@cloudbees.com> wrote:
> when the bridge was setup it was done so that when new content started
> to turn up on the github repo that was not in svn the svn -> github
> replication would stop.

Right, but there have been cases where commits were made after that
point in svn (so forked), and surely there are many cases where the
plugin maintainer simply forgot to close the svn dir.

[Daniel Beck]

On 22.04.2015, at 14:59, Jesse Glick <jgl...@cloudbees.com> wrote:

> I am not sure if active changes are being made there.

More than 100 commits this year. Granted, most by just one user, Dimitri Tenenbaum (and some of those because of the recent Artifactory auth problem IIRC), but still.

> surely there are many cases where the plugin maintainer simply forgot to close the svn dir.

Did you actually check the individual plugin folders? More than half of them contain just zero or one file (a README pointing to Github). I cleaned quite a few up in November, replacing sources by a notice that the plugin was moved as seems to be customary when continuing on Github. And most of the rest were plugins untouched for a few years, and I doubt they suddenly became active in large numbers.

> This is a freaking mess.

I don't see it. Sure, if the intention is to reduce the infra we need to maintain, freeing resources for other things, moving plugins to Github could be done. But I don't have the impression that SVN is a drain on resources. And IMO the mess is not nearly as bad as you seem to assume.

Of course, what we could do is force all plugins that haven't been updated in either repo since e.g. 2012 (Nicolas' POM mass cleanup) to migrate to Github. I doubt we'll have more than a handful left, and if those ever get picked up again, it'd likely be on Github anyway.

[Richard Bywater]

Just to throw something out there...

I've never used it so perhaps its not fit for purpose, but given that Github supposedly supports people accessing the repositories via SVN, wouldn't an idea be to make sure that all repositories live on Github and people simply use their choice of SCM tool?

Richard.

--
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 jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5A30E1DB-6B93-4C1E-8474-E1BA8D5743F3%40beckweb.net.

[Jan Ruzicka]

Hi,

Can there be a mass release of plugin POM updates to redirect to git?

There is the infra_plugin_changes_report [1] that should update Plugin report page[2], but upload to Wiki is failing (for over a year now).

It may be an easy change to generate another list showing plugins with SVN as SCM source.

Jan

[1] https://ci.jenkins-ci.org/job/infra_plugin_changes_report/

[2] https://wiki.jenkins-ci.org/display/JENKINS/Unreleased+Plugin+Changes

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945%3DeANNAbLLoU3z%3DtjdmGNV5ejMHvf4mDuJbqJqZELUMQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Jan Ruzicka
Senior Software Engineer
Comtech Mobile Datacom Corporation
20430 Century Blvd, Germantown, MD 20874
Office: 240-686-3300
Fax: 240-686-3301
 
The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please so notify the sender immediately, and delete it and all attachments from your computer and network.

---

NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and/or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media.

[Dimitri Tenenbaum]

Hi,

I have decided to use Subversion for my now 4-weeks old vncviewer plugin because according to Hosting Plugins Tutorial usage of Jenkins Subversion repository is still a valid way of plugin distribution.

The idea "simply abandon"  something which is valid today from one day to the next is not a good one.

Provided there is a consensus amongst the Jenkins core maintainers to drop the Subversion repo (is that really the case??) I would split the issue into several steps:

1. Update  Hosting Plugins Tutorial, don't offer Subversion for hosting of new plugins
   
2. Create simple migration how-to for existing plugins which would make the migration easier for git newbies
3. After long enough (6 months ?) grace period for migration of existing plugins "simply abandon the Subversion repo"