Critical Issue with SVN Plugin: File Contents Doubled

[Kenny Ayers]

Hey folks,

  We're seeing an issue with the Jenkins SVN plugin where files that are svn moved, then added back to the repo have their contents doubled upon checkout when using any strategy except "Always checkout a fresh copy".  This seems like a fairly critical issue that was first filed last year, which a good number of votes and replies with reproduction steps.

  This issue was filed last year, and has a good number of votes and replies with reproduction steps.  What (if any) steps can be taken to make this more visible to the SVN plugin developers?

  https://issues.jenkins-ci.org/browse/JENKINS-14551

Thank you in advance,

Kenny

[Andrew Gray]

Suggestion: Migrate to Git.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Michael Clarke]

On a slightly different note:

Jenkins and its plugins are built by a variety of users, many in their spare time at their own expense. If you need an issue to be fixed urgently then your options are:

1. Vote on the issue. This makes it clear how many people need it fixed.  

[Michael Clarke]

...

2. Try and fix this yourself. There are plenty of people who would be happy to provide guidance on where to begin and we'd be happy for any contributions.

3. Pay for this to be fixed. There are companies out there who provide commercial support for Jenkins, or sites such as Freedom Sponsors allow you to place a bounty for fixing a bug.

4. Alter your job to use options not impacted by this issue. If you can't get the issue fixed then look for a workaround. It may not seem like the best option, but it at least allows you to continue working until someone fixes the issue.

Thanks

Michael

[Kenny]

I'm sure your heart is in the right place Michael, but I understand how open source software works.  I've voted on the issue, replied with my case information, and implemented a work-around until this is resolved.  This is a critical bug that was reported 9 months ago that affects the entire user-base.  It deserves some attention, if possible.

[Baptiste Mathus]

Hi Kenny,

You're talking about a workaround, couldn't you try working on it to become a fix and submit the corresponding pull request?

Btw, "affecting entire user-base" sounds excessive to me since we also have a lot of svn projects and I don't think we're actually affected by this issue. I suppose that's also the reason none bothered fixing it at that point.

My 2 cents, cheers

Le 16 avr. 2013 10:22, "Kenny" <theother...@gmail.com> a écrit :

I'm sure your heart is in the right place Michael, but I understand how open source software works.  I've voted on the issue, replied with my case information, and implemented a work-around until this is resolved.  This is a critical bug that was reported 9 months ago that affects the entire user-base.  It deserves some attention, if possible.

--

[Kenny Ayers]

Hey Baptiste,

  The assertion that this is affecting the entire user base is valid I believe, given the commonality of the use case for merging branched files when using SVN. In our case, we even see the issue when adding files to the repo via svn mv. Are you saying you've executed the repro steps and you've seen other results?

-Kenny

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/RqVeeriUJ9M/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.