svn.jenkins-ci.org will be SHUT DOWN on March 31

[R. Tyler Croy]

At the end of the month, I will be shutting down svn.jenkins-ci.org


From the access logs it doesn't appear that there is any traffic going to
svn.jenkins-ci.org that originates from developers. If you are still using
svn.jenkins-ci.org we need to talk about moving your work over to GitHub
(which has supported SVN for 6 years
https://github.com/blog/626-announcing-svn-support)


Again, I will be shutting off svn.jenkins-ci.org at the end of March.


Cheers
- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[Oleg Nenashev]

Could we manually check the migration status of plugins before deleting the data?
Are you also going to persist the backup for a while?

четверг, 17 марта 2016 г., 17:10:50 UTC+1 пользователь R Tyler Croy написал:

[R. Tyler Croy]

(replies inline)

On Thu, 17 Mar 2016, Oleg Nenashev wrote:

> Could we manually check the migration status of plugins before deleting the
> data?

*You* can, I'm not signing up for any more work maintaining this system :)

> Are you also going to persist the backup for a while?

I'm going to back up the data for a while, but if you want to persist the data
that's fine too.


> ??????????????, 17 ?????????? 2016 ??., 17:10:50 UTC+1 ???????????????????????? R Tyler Croy ??????????????:

> >
> >
> > At the end of the month, I will be shutting down svn.jenkins-ci.org
> >
> >
> > From the access logs it doesn't appear that there is any traffic going to
> > svn.jenkins-ci.org that originates from developers. If you are still
> > using
> > svn.jenkins-ci.org we need to talk about moving your work over to GitHub
> > (which has supported SVN for 6 years
> > https://github.com/blog/626-announcing-svn-support)
> >
> >
> > Again, I will be shutting off svn.jenkins-ci.org at the end of March.
> >
> >
> > Cheers
> > - R. Tyler Croy
> >
> > ------------------------------------------------------
> > Code: <https://github.com/rtyler>
> > Chatter: <https://twitter.com/agentdero>
> >
> > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> > ------------------------------------------------------
> >

> _______________________________________________
> Jenkins-infra mailing list
> Jenkin...@lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra

[Oleg Nenashev]

I'm just aware about losing code for plugins.

IIRC Nicolas made some work on migrating such stale plugins, but I'm not sure if we've migrated all of them.

Backups are cheap, so I would vote for keeping the dump before somebody decides to join the archaeology team :)

[Baptiste Mathus]

I did something for MojoHaus (MOJO @ Codehaus) along that: https://github.com/mojohaus/convert-to-git/ 

And the associated docker image: https://hub.docker.com/r/batmat/mojohaus-converter/

Might be we could do something like that. 

Also, we can use GitHub LFS to store the dump in some of the jenkinsci org repo (or maybe preferrably a new one).

My 2 cents

--
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/CAPfivLBF6zo-EyqRCU4uECzN2AZpPC4RF-wfLNapB8zxat%2BjRg%40mail.gmail.com.

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

[Manuel Jesús Recena Soto]

Hello,

It seems there are tests using this SVN server:
https://github.com/jenkinsci/subversion-plugin/blob/5da9ddbcf8d7ab9f8710ad7a8fd29c5bb27f24fa/src/test/java/hudson/scm/SubversionEnvInjectTest.java#L16

Regards,

> --
> 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/20160317161039.GF13352%40blackberry.coupleofllamas.com.

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

--
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

[Oliver Gondža]

On 03/17/2016 10:17 PM, Manuel Jesús Recena Soto wrote:
> Hello,
>
> It seems there are tests using this SVN server:
> https://github.com/jenkinsci/subversion-plugin/blob/5da9ddbcf8d7ab9f8710ad7a8fd29c5bb27f24fa/src/test/java/hudson/scm/SubversionEnvInjectTest.java#L16

Good catch, the test should better live in ATH with the rest that talk
to real repository (in docker contianer).

https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/SubversionPluginTest.java
--
oliver

[Daniel Beck]

On 17.03.2016, at 17:10, R. Tyler Croy <ty...@monkeypox.org> wrote:

> At the end of the month, I will be shutting down svn.jenkins-ci.org
>
> From the access logs it doesn't appear that there is any traffic going to
> svn.jenkins-ci.org that originates from developers. If you are still using
> svn.jenkins-ci.org we need to talk about moving your work over to GitHub

There are a few plugins still being developed in SVN with commits in the past 1.5 years.

* https://wiki.jenkins-ci.org/display/JENKINS/Serenity+Plugin
* http://wiki.jenkins-ci.org/display/JENKINS/Klaros-Testmanagement+Plugin
* http://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+Plugin
* https://wiki.jenkins-ci.org/display/JENKINS/VncViewer+Plugin
* http://wiki.jenkins-ci.org/display/JENKINS/ImageComparison+Plugin

CCing their developers.

[Baptiste Mathus]

I think I've seen that practiced somewhere in the past:

How about temporarily disabling the SVN server as a preliminary testing, say during 12 or 24h with announce beforehand in the very short term?

Then set it back up.

The idea is to potentially detect crashing tests, people still using it and so on, before the real shutdown.

This is not a perfect solution, we'll still miss some things, but that may help detect tests at least some things and potentially have some more time to fix those.

@Tyler if you can provide the dump /somewhere/, I can handle the LFS push + doc somewhere under a jenkinsci repo.

-- Baptiste

--
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/8DE23CB8-F4FD-4743-967B-CEFCA06B31C2%40beckweb.net.

[Torsten Stolpmann]

Hi Daniel,

thanks for taking care of us plugin developers, this is much appreciated.

Speaking for the Klaros-Testmanagement Plugin, which is still under
active development, can anybody please tell me what the preferred way of
migrating the plugin away from svn would be?

I am aware of
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins but I think
there must be better ways to achieve this without starting from zero.

Thanks,

Torsten

--
Torsten Stolpmann
Managing Director

verit Informationssysteme GmbH
Europaallee 10
67657 Kaiserslautern
Germany

Email: stol...@verit.de
Phone: +49 631 520 840 00
Fax: +49 631 520 840 01
Web: http://www.verit.de/

[R. Tyler Croy]

(replies inline)

On Fri, 18 Mar 2016, Torsten Stolpmann wrote:

> Hi Daniel,
>
> thanks for taking care of us plugin developers, this is much appreciated.
>
> Speaking for the Klaros-Testmanagement Plugin, which is still under active
> development, can anybody please tell me what the preferred way of migrating
> the plugin away from svn would be?
>
> I am aware of https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
> but I think there must be better ways to achieve this without starting from
> zero.

This (https://help.github.com/articles/importing-from-subversion/) might be
something Daniel, or I, could do as jenkinsci github organization
administrators.

> On 18.03.2016 09:08, Daniel Beck wrote:
> >
> >On 17.03.2016, at 17:10, R. Tyler Croy <ty...@monkeypox.org> wrote:
> >
> >>At the end of the month, I will be shutting down svn.jenkins-ci.org
> >>
> >> From the access logs it doesn't appear that there is any traffic going to
> >>svn.jenkins-ci.org that originates from developers. If you are still using
> >>svn.jenkins-ci.org we need to talk about moving your work over to GitHub
> >
> >There are a few plugins still being developed in SVN with commits in the past 1.5 years.
> >
> >* https://wiki.jenkins-ci.org/display/JENKINS/Serenity+Plugin
> >* http://wiki.jenkins-ci.org/display/JENKINS/Klaros-Testmanagement+Plugin
> >* http://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+Plugin
> >* https://wiki.jenkins-ci.org/display/JENKINS/VncViewer+Plugin
> >* http://wiki.jenkins-ci.org/display/JENKINS/ImageComparison+Plugin
> >
> >CCing their developers.
> >
>
> --
> Torsten Stolpmann
> Managing Director
>
> verit Informationssysteme GmbH
> Europaallee 10
> 67657 Kaiserslautern
> Germany
>
> Email: stol...@verit.de
> Phone: +49 631 520 840 00
> Fax: +49 631 520 840 01
> Web: http://www.verit.de/
>

> --
> 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/56EBD396.40907%40gmail.com.

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

[Michael O'Cleirigh]

Hello,

I wrote a whole subversion to git repository conversion program.

Anyways I used it to convert the svn.jenkins-ci.org into git.

https://github.com/mocleiri/svn.jenkins-ci.org

I need to write some additional branch detection rules and rerun the export but in principal it seems to have worked.

Branch detection is right to left so there are some mistakes that can be fixed with repo specific branch detection.

Nicely there weren't any files greater than 100 MB in size so no rewriting was needed before it could be uploaded to github.

FYI the svn repo on disk itself is 1.8 GB (I mirrored it), a bzipped svn dump is around 700 MB.  The git repo is around 400 mb.

Typically post conversion the test is do the trunk branches build and are the release tags accurate.

This page has a section on how you can checkout the key branch from svn and then turn that tree into a git commit.  Then it can be diff'd with the git importer conversion and if there is no difference it's an accurate conversion.

https://github.com/kuali-student/git-repository-tools/blob/master/README.txt

If a reasonably sized list of such key branches can be made I can have a look at the accuracy of the conversion.

Regards,

Michael

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20160318164356.GQ13352%40blackberry.coupleofllamas.com.

[Torsten Stolpmann]

If this is possible, please do so. My GitHub id is stolp. Please let me
know how I can support this by adding information or executing
additional actions.

Regards,

Torsten

[Dimitri Tenenbaum]

"This (https://help.github.com/articles/importing-from-subversion/) might be
something Daniel, or I, could do as jenkinsci github organization
administrators. "

If this is possible, could you please import the following plugins too:

http://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/VncViewer+Plugin
http://wiki.jenkins-ci.org/display/JENKINS/ImageComparison+Plugin

My GitHub id is dtbaum. I am on vacation till the 3rd April, therefore my possibilities to support the migration are unfortunately limited by my iPad and flaky hotel Wi-Fi.

Regards,
Dimitri

[Michael O'Cleirigh]

Hello,

I identified the tags for each of the svn.jenkins-ci.org plugins and started doing comparisons with what is in the live svn repo.

https://docs.google.com/document/d/1MnYEIVPkNFDWOjXqUYGx-Ic6uYrvpZvTByM8GNiIhMM/edit?usp=docslist_api

Aside from some file permissions the git converted trunk is an exact replica of svn.

I'm planning on creating separate repo's per plugin with their hudson/plugins/<plugin-name> extract to the root to match the tags.

I tried git filter-branch --subdirectory-filter but it only works for trunk not the tags.  I'm working on a --commit-filter that will keep the tag path as-is but collapse trunk commits on the target hudson/plugins/<plugin-name> path. 

Once this is done I will upload the split repos to github and they can be vetted and migrated into the regular jenkinsci github. 

Once split the trunk branches for each (or perhaps renamed to master) need to be updated to migrate the plugin's release setup to work in git. 

Hope to have the repo's split within a day or two,

Regards,

Michael

--
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/40304318-fb78-4ed6-a2d6-5052466f1471%40googlegroups.com.

[R. Tyler Croy]

(replies inline)

On Tue, 29 Mar 2016, Michael O'Cleirigh wrote:

> Hello,
>
> I identified the tags for each of the svn.jenkins-ci.org plugins and
> started doing comparisons with what is in the live svn repo.
>
> https://docs.google.com/document/d/1MnYEIVPkNFDWOjXqUYGx-Ic6uYrvpZvTByM8GNiIhMM/edit?usp=docslist_api
>
> Aside from some file permissions the git converted trunk is an exact
> replica of svn.
>
> I'm planning on creating separate repo's per plugin with their

> *hudson/plugins/<plugin-name>
> *extract to the root to match the tags.
>
> I tried *git filter-branch --subdirectory-filter* but it only works for

> trunk not the tags. I'm working on a --commit-filter that will keep the
> tag path as-is but collapse trunk commits on the target

> *hudson/plugins/<plugin-name>* path.

>
> Once this is done I will upload the split repos to github and they can be
> vetted and migrated into the regular jenkinsci github.
>
> Once split the trunk branches for each (or perhaps renamed to master) need
> to be updated to migrate the plugin's release setup to work in git.
>
> Hope to have the repo's split within a day or two,

This is great news Michael, thanks for taking the initiative here! If there's
anything you need from me or that I can help with, let me know, I am generally
on #jenkins-infra most of the US/West's business day (and then some).


Cheers

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

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

[Michael O'Cleirigh]

Hello,

Just to give an update.

I've switched over to using Java and JGit for rewriting/splitting out the plugins.

I have some repo cleaning code that I'm adapting fit this case.

My splitter can extract the module where it exists. And preserve the release tags.

The current issue I'm solving is how to prune commits that don't include the module at all.

These are mostly from the beginning of the repository (early history).

I have a test case in https://github.com/kuali-student/git-repository-tools in SplitMultiModuleRewriterTestCase that builds an example git repository and then applies the splitter.

I don't have the asserts setup but I debug through it in eclipse and inspect the resultant repo for accuracy.

I hope to have this issue solved and the split repos available by the end if the week.

Regards,

Michael

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20160329183535.GX15060%40blackberry.coupleofllamas.com.

[R. Tyler Croy]

(replies inline)

On Tue, 05 Apr 2016, Michael O'Cleirigh wrote:

> Hello,
>

> Just to give an update.
>
> I've switched over to using Java and JGit for rewriting/splitting out the
> plugins.
>
> I have some repo cleaning code that I'm adapting fit this case.
>
> My splitter can extract the module where it exists. And preserve the
> release tags.
>
> The current issue I'm solving is how to prune commits that don't include
> the module at all.
>
> These are mostly from the beginning of the repository (early history).
>
> I have a test case in https://github.com/kuali-student/git-repository-tools
> in SplitMultiModuleRewriterTestCase that builds an example git repository
> and then applies the splitter.
>
> I don't have the asserts setup but I debug through it in eclipse and
> inspect the resultant repo for accuracy.
>
> I hope to have this issue solved and the split repos available by the end
> if the week.

Thanks for the update! As you may or may not have noticed, svn.jenkins-ci.org
is still online. Unfortunately I got sick over the weekend so I wasn't able to
spend any time on decommissioning it.

I consider the service's decommissioning deadline extended to next weekend (April
9) instead.

[Dimitri Tenenbaum]

 Hello,

 

please let me know if I can somehow support the migration of my SVN based plugins.

Regards 

Dimitri 

 

[R. Tyler Croy]

I have 404'ed all requests to data under svn.jenkins-ci.org as part of this
weekend's maintenance.

[Daniel Beck]

> On 17.04.2016, at 17:27, R. Tyler Croy <ty...@monkeypox.org> wrote:
>
> I have 404'ed all requests to data under svn.jenkins-ci.org as part of this
> weekend's maintenance.

GitHub repositories for the plugins I listed earlier in this thread:

https://wiki.jenkins-ci.org/display/JENKINS/Serenity+Plugin
https://github.com/jenkinsci/serenity-plugin

https://wiki.jenkins-ci.org/display/JENKINS/Klaros-Testmanagement+Plugin
https://github.com/jenkinsci/klaros-testmanagement-plugin

https://wiki.jenkins-ci.org/display/JENKINS/VncRecorder+Plugin
https://github.com/jenkinsci/vncrecorder-plugin

https://wiki.jenkins-ci.org/display/JENKINS/VncViewer+Plugin
https://github.com/jenkinsci/vncviewer-plugin

https://wiki.jenkins-ci.org/display/JENKINS/ImageComparison+Plugin
https://github.com/jenkinsci/imagecomparison-plugin

They've recently been updated with the latest commits from SVN.

[Torsten Stolpmann]

Hello,

As of now, it seems that the SVN repository has finally been shut down.

I was about to release a new version of our klaros-testmanagement plugin
today, but I no longer have a repository to commit to.

Is there any progress on the task of migrating the existing plugins to
GitHub? Is there any way I can assist with this?

Thanks,

Torsten (being quite aware that the imminent Jenkins 2.0 release is
probably more urgent for most of the devs here)

[Daniel Beck]

> On 19.04.2016, at 17:05, Torsten Stolpmann <torsten....@gmail.com> wrote:
>
> I was about to release a new version of our klaros-testmanagement plugin today, but I no longer have a repository to commit to.
>
> Is there any progress on the task of migrating the existing plugins to GitHub? Is there any way I can assist with this?
>

Hi Torsten,

All the plugins have been imported into GitHub again this week. See my previous email in this thread.

Daniel

[Michael O'Cleirigh]

Hello, 

I think the git-svn import of the active plugins done by Daniel are fine.  

I finally got my JGit based splitter code to work to split out the essentially the same repo's from the full repository conversion that I made ( https://github.com/mocleiri/svn.jenkins-ci.org).

https://github.com/kuali-student/git-repository-tools/blob/master/git-repo-cleaner/src/main/java/org/kuali/student/git/cleaner/SplitMultiModuleJGitRewriter.java

If any other module needs to split out later this would be a tool to use to do it, now that the svn repo is gone.

Since it took me so long to get the splitter working I ran it on the modules anyways:

https://github.com/mocleiri/klaros-testmanagement-plugin

https://github.com/mocleiri/imagecomparison-plugin

https://github.com/mocleiri/vncviewer-plugin

https://github.com/mocleiri/vncrecorder-plugin

https://github.com/mocleiri/serenity-plugin

But I don't think these need to be used since they look to be almost exactly like the git-svn imported repo's.

Regards, 

Michael

--
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/E3ABD175-ADFC-40C7-A776-E7F84277B4D3%40beckweb.net.

[Dimitri Tenenbaum]

Hello,

 

great work - thank you for plugin migration!

Could anybody please enable the write access for my migrated plugins?

https://github.com/jenkinsci/vncviewer-plugin

https://github.com/jenkinsci/vncrecorder-plugin 

https://github.com/jenkinsci/imagecomparison-plugin

My GitHub id is dtbaum.

Thanks, 

Dimitri

[Oliver Gondža]

On 04/26/2016 01:20 PM, Dimitri Tenenbaum wrote:
> Hello,
>
> great work - thank you for plugin migration!
> Could anybody please enable the write access for my migrated plugins?

You should have the access to all 3 of them.

Cheers
--
oliver

[Dimitri Tenenbaum]

It doesn't seem to me that I have write access, see screenshot below. Am i doing something wrong?

[Daniel Beck]

> On 26.04.2016, at 13:58, Dimitri Tenenbaum <dim....@gmail.com> wrote:
>
> It doesn't seem to me that I have write access, see screenshot below. Am i doing something wrong?
>

You need to accept the invitation into the jenkinsci organization. Click the link in the email from GitHub, or at https://github.com/jenkinsci/

[Dimitri Tenenbaum]

Thank you!

[Jesse Glick]

Beware that this shutdown has broken some automated tests:

https://github.com/jenkinsci/parameterized-trigger-plugin/blob/1501044da555bd6a22f7ddafcc6e7536649a128d/src/test/java/hudson/plugins/parameterizedtrigger/test/SubversionRevisionBuildTriggerConfigTest.java
https://github.com/jenkinsci/subversion-plugin/blob/7fa8b019ba895080d0b1c414c693bd93e64e45d8/src/test/java/hudson/scm/SubversionEnvInjectTest.java
https://github.com/jenkinsci/subversion-plugin/blob/7fa8b019ba895080d0b1c414c693bd93e64e45d8/src/test/java/hudson/scm/SubversionSCMTest.java
https://github.com/jenkinsci/subversion-plugin/blob/7fa8b019ba895080d0b1c414c693bd93e64e45d8/src/test/java/hudson/scm/SubversionEnvVarsTest.java
https://github.com/jenkinsci/subversion-plugin/blob/7fa8b019ba895080d0b1c414c693bd93e64e45d8/src/test/java/hudson/scm/SVNWorkingCopyTest.java
https://github.com/jenkinsci/acceptance-test-harness/blob/2b5dadc9caa266ed8aaf684642e8aa5f9416d267/src/test/java/plugins/no_docker/SubversionPluginNoDockerTest.java
https://github.com/jenkinsci/acceptance-test-harness/blob/2b5dadc9caa266ed8aaf684642e8aa5f9416d267/src/test/java/plugins/MultipleScmsPluginTest.java

GitHub allows Subversion protocol access to Git repositories so
perhaps these should be switched to using GitHub demo repos (if it is
impractical to make them run offline).

[Ullrich Hafner]

> https://github.com/jenkinsci/acceptance-test-harness/blob/2b5dadc9caa266ed8aaf684642e8aa5f9416d267/src/test/java/plugins/no_docker/SubversionPluginNoDockerTest.java

I think that this test class can be safely deleted. The same tests are available in SubversionPluginTest that now use a SVN repository in a docker container. We just did not delete these tests yet since docker might not be available on every machine.

[Torsten Stolpmann]

Hi Michael,

thanks a lot for your efforts on migrating the plugin code.

I checked this out and tried to check in my modifications on
klaros-testmanagement-plugin but received the following error message
from EGit:

Failed pushing to klaros-testmanagement-plugin - origin:
https://github.com/jenkinsci/klaros-testmanagement-plugin.git:
git-receive-pack not permitted

Is there anything that needs to be added in regards to authorization for
my GitHub user account (stolp)? Am I missing something?

Thanks and regards,

Torsten

On 20.04.2016 06:02, Michael O'Cleirigh wrote:
> Hello,
>
> I think the git-svn import of the active plugins done by Daniel are fine.
>
> I finally got my JGit based splitter code to work to split out the
> essentially the same repo's from the full repository conversion that I
> made ( https://github.com/mocleiri/svn.jenkins-ci.org).
>
> https://github.com/kuali-student/git-repository-tools/blob/master/git-repo-cleaner/src/main/java/org/kuali/student/git/cleaner/SplitMultiModuleJGitRewriter.java
>
> If any other module needs to split out later this would be a tool to use
> to do it, now that the svn repo is gone.
>
> Since it took me so long to get the splitter working I ran it on the
> modules anyways:
>
> https://github.com/mocleiri/klaros-testmanagement-plugin
> https://github.com/mocleiri/imagecomparison-plugin
> https://github.com/mocleiri/vncviewer-plugin
> https://github.com/mocleiri/vncrecorder-plugin
> https://github.com/mocleiri/serenity-plugin
>
> But I don't think these need to be used since they look to be almost
> exactly like the git-svn imported repo's.
>
> Regards,
>
> Michael
>
>
>
>
>
> On Tue, Apr 19, 2016 at 4:31 PM, Daniel Beck <m...@beckweb.net

> <mailto:m...@beckweb.net>> wrote:

>
>
> > On 19.04.2016, at 17:05, Torsten Stolpmann <torsten....@gmail.com <mailto:torsten....@gmail.com>> wrote:
> >
> > I was about to release a new version of our klaros-testmanagement plugin today, but I no longer have a repository to commit to.
> >
> > Is there any progress on the task of migrating the existing plugins to GitHub? Is there any way I can assist with this?
> >
>
> Hi Torsten,
>
> All the plugins have been imported into GitHub again this week. See
> my previous email in this thread.
>
> Daniel
>
> --
> 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

> <mailto:jenkinsci-dev%2Bunsu...@googlegroups.com>.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/E3ABD175-ADFC-40C7-A776-E7F84277B4D3%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.
>
>

> --
> 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

> <mailto:jenkinsci-de...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-dev/CAGUfqupVv4hu4QuHd-J7Z_KhzwKHaS9y0jU6bv8MNtushB__MA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAGUfqupVv4hu4QuHd-J7Z_KhzwKHaS9y0jU6bv8MNtushB__MA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

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

[Jesse Glick]

On Fri, Apr 29, 2016 at 5:43 PM, Ullrich Hafner
<ullrich...@gmail.com> wrote:
>> https://github.com/jenkinsci/acceptance-test-harness/blob/2b5dadc9caa266ed8aaf684642e8aa5f9416d267/src/test/java/plugins/no_docker/SubversionPluginNoDockerTest.java
>
> I think that this test class can be safely deleted.

If you know something about it, file a PR to clean it up please.