Alan Harder added a comment - 2010-11-18 08:44 Unassigning.. as I don't use cvs I don't think I can spend any more time digging into this. Perhaps you can find someone who does use this plugin to help, or try debugging/fixing yourself. Otherwise you can try cvs plugin version 1.1 and see if that still works (w/o the "all upstream" option checked), or if something else changed to cause this problem. Good luck..

fernandor added a comment - 2010-11-18 10:05 How could I downgrade the cvs plugin? It does not give-me the option.

Alan Harder added a comment - 2010-11-18 10:17 On the advanced tab you can provide a file to upload.. get v1.1 from http://jenkins-ci.org/download/plugins/cvs/ Or you can just drop the file in your $HUDSON_HOME/plugins dir and restart.

Tomas Boremalm added a comment - 2011-07-07 12:20 Im having this issue on v1.4 and v1.1

Christoffer Børrild added a comment - 2011-11-22 10:16 I've observed the same problem in Jenkins 1.440 and I believe I found the cause of the problem. CAUSE : Debugging the code reveals that an access-exception is thrown during tagging. However, the code fails to catch this exception, probably because it was unexpected when code was written. The exception is thrown because the CVSSCM.TagWorkerThread-class calls the "keepLog()"-method of the "hudson.model.Run"-class. This method, in turn, checks if the current user has the "UPDATE" right. However, since the "perform"-method of the TagWorkerThread is run from a separate thread it has no user associated with it and thus uses the "anonymous" user, hence the observations in the log-files. I believe the issue has arisen due to a security-fix (actually authored by "mindless") that introduced the check for the UPDATE-permission and hence broke the tagging function in the CVS plugin (...when security is enabled). WORKAROUND : A workaround of the problem can be to grant the "UPDATE"-permission to the anonymous user. If this is the only privilege granted to the anonymous user it will not interfere visually with the UI (from what I've seen so far) but of course it's not a viable solution to a publicly exposed system. FIX : A quick-fix of the code would be to completely remove the call to "keepLog()" as it doesn't seem to play any vital part in the tagging - I guess it was supposed to store the output of the tagging process for later querying, however, I've never seen any logs in my old installation where tagging still works. I've tried to catch the exception and just ignore it (in a plugin that was based on the CVSSCM-code) and in this case the tagging succeeds. Anyway, here's the faulty peace of code ( hudson.scm.CVSSCM.java, line 1679 ): protected void perform(TaskListener listener) { for (Entry<AbstractBuild<?,?>, String > e : tagSet.entrySet()) { TagAction ta = e.getKey().getAction(TagAction.class); if (ta== null ) { listener.error(e.getKey()+ " doesn't have CVS tag associated with it. Skipping" ); continue ; } listener.getLogger().println(Messages.CVSSCM_TagginXasY(e.getKey(),e.getValue())); try { e.getKey().keepLog(); } catch (IOException x) { x.printStackTrace(listener.error(Messages.CVSSCM_FailedToMarkForKeep(e.getKey()))); } ta.perform(e.getValue(), listener); listener.getLogger().println(); } } and here's a fix: protected void perform(TaskListener listener) { for (Entry<AbstractBuild<?,?>, String > e : tagSet.entrySet()) { TagAction ta = e.getKey().getAction(TagAction.class); if (ta== null ) { listener.error(e.getKey()+ " doesn't have CVS tag associated with it. Skipping" ); continue ; } listener.getLogger().println(Messages.CVSSCM_TagginXasY(e.getKey(),e.getValue())); // try { // e.getKey().keepLog(); //} catch (IOException x) { // x.printStackTrace(listener.error(Messages.CVSSCM_FailedToMarkForKeep(e.getKey()))); //} ta.perform(e.getValue(), listener); listener.getLogger().println(); } } EPILOG : I'm not in loop with all this project/github/patching/branching-stuff so I suggest somebody better suited try to commit the fix.

Christoffer Børrild added a comment - 2011-11-27 12:50 I've committed a pull-request with the fix on github: https://github.com/Boerrild/cvs-plugin/commit/57e1806398772e5b7a6ba32a8a02a47b095e0d23 . Not sure what happens from here(!?)

Michael Clarke added a comment - 2012-01-22 11:48 Whilst Christoffer's fix seems to work, I've not merged it as we have a bigger change pending which incorporates an variant of this fix.