[JIRA] [core] (JENKINS-32024) Wrongly claims reverse proxy broken
Title: Message Title aristedes resolved as Not A Defect My bad. Sorry for wasting your time. I read that page 5 times without seeing that line. Jenkins / JENKINS-32024 Wrongly claims reverse proxy broken Change By: aristedes Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32024) Wrongly claims reverse proxy broken
Title: Message Title aristedes commented on JENKINS-32024 Re: Wrongly claims reverse proxy broken If you mean the global setting with the label "Jenkins URL" under the heading "Jenkins Location" then no, I already checked that and it starts with "https". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32024) Wrongly claims reverse proxy broken
Title: Message Title aristedes reopened an issue Sorry, but I've read that page several times and cannot find any reference to the fact that Jenkins cannot be run behind a proxy that does SSL. There is in fact no actual problem with the operation of Jenkins, but the error message in this case is extraneous with no obvious way to get rid of it. Jenkins / JENKINS-32024 Wrongly claims reverse proxy broken Change By: aristedes Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32024) Wrongly claims reverse proxy broken
Title: Message Title aristedes created an issue Jenkins / JENKINS-32024 Wrongly claims reverse proxy broken Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Dec/15 5:35 AM Priority: Minor Reporter: aristedes Our Jenkins instance sits behind Apache httpd 2.4. There is no functional problem, but a recent update (sometime at or before 1.639) shows the message: It appears that your reverse proxy set up is broken Running the recommended script give me this result: http://build.acme.com/manage vs. https://build.acme.com/manage Clearly Jenkins is confused about the missing SSL, however apache is taking care of the SSL within the virtualhost before the ProxyPass kicks in. ProxyPass / http://localhost:8180/ nocanon ProxyPassReverse / http://localhost:8180/ ProxyRequests Off AllowEncodedSlashes NoDecode
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title aristedes commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. How can you display the realm for a repository? For me with svn 1.8.13 on OSX I get this: $ svn info Path: . Working Copy Root Path: /Users/ari/svn/apache-foundation URL: https://svn.apache.org/repos/private/foundation Relative URL: ^/foundation Repository Root: https://svn.apache.org/repos/private Repository UUID: 694d45b4-53eb-0310-9336-ddcd440d954d Revision: 59701 Node Kind: directory Schedule: normal Last Changed Author: clr Last Changed Rev: 59700 Last Changed Date: 2015-06-25 10:54:00 +1000 (Thu, 25 Jun 2015) which part is the realm that Jenkins is wanting? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25538) Add Phabricator as Repository Browser
Title: Message Title aristedes commented on JENKINS-25538 Re: Add Phabricator as Repository Browser Thanks for that clarification. If we just incorporate the repoCode into the base URL, then it shouldn't matter how long it is. We don't need to worry about git SHA since this task is only for the svn plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25538) Add Phabricator as Repository Browser
Title: Message Title
aristedes edited a comment on JENKINS-25538
Re: Add Phabricator as Repository Browser
Toassistwiththedevelopmentofthis,hereisthepattern: http[s]?:// {{ ${baseURL}/r${repoCode}${commitNumber} }} ${repoCode}isaonecharactercodedefinedfortherepository.Ithastheletterrbeforeit.Really,itcouldallbepartofthebaseURLlikethis: {{ baseURL=https://phabricator.acme.com/rC }} andthenwejuststickthecommitnumberattheend.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25538) Add Phabricator as Repository Browser
Title: Message Title
aristedes edited a comment on JENKINS-25538
Re: Add Phabricator as Repository Browser
Toassistwiththedevelopmentofthis,hereisthepattern:{{$ { baseURL } /r$ { repoCode } $ { commitNumber}} } $ { repoCode } isaonecharactercodedefinedfortherepository.Ithastheletterrbeforeit.Really,itcouldallbepartofthebaseURLlikethis (where'C'istherepositorycode) :{{baseURL=https://phabricator.acme.com/rC}}andthenwejuststickthecommitnumberattheend.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher Thanks for your excellent and quick response on this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher tr style=opacity: 1;td class=setting-leftspacenbsp;/tdtd class=setting-nameTriggers/tdtd class=setting-maindiv class=hetero-list-container with-drag-drop div class=repeated-chunk name=project_triggers id=yui-gen138table style=width:100%tbodytrtd colspan=3div class=dd-handle id=yui-gen139b/b/div/tdtd class=setting-no-help/td/trtr style=display:nonetdinput type=hidden name=stapler-classinput type=hidden name=$class/td/trtrtd colspan=4div align=rightspan class=yui-button yui-push-button repeatable-delete danger id=yui-gen144span class=first-childbutton type=button tabindex=0 id=yui-gen144-buttonRemove Trigger/button/span/span/div/td/tr/tbody/table/divdiv class=repeatable-insertion-point/divdivspan class=yui-button yui-menu-button id=yui-gen140span class=first-childbutton type=button tabindex=0 id=yui-gen140-button class=hetero-list-add suffix=project_triggersAdd Trigger/button/span/span/div/div/tdtd class=setting-helpa helpurl=/plugin/email-ext/help/projectConfig/addATrigger.html href="" class="code-quote" style="color: #009100"># class=help-button tabindex=img src="" class="code-quote" style="color: #009100">/static/32547464/images/16x16/help.png class=icon-help icon-sm alt=Help for feature: Triggers style=width: 16px; height: 16px; /a/td/tr That's the block of html with the empty trigger which is created by default when you add a new Editable Email Notification. The problem seems to happen for me on Firefox 38 (haven't tested others) and it doesn't matter if you add the action to the release phase or the post-build phase. If you try to save without expanding the advanced section and removing the blank trigger, then you get an error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher I've got the same issue with Jenkins 1.612 and 2.40.1 of this plugin. The workaround is to: go into advanced settings within the email configuration remove the blank trigger that appears there Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher The release plugin is a common way to structure release builds. I also downgraded your plugin to 2.40 and it didn't help. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher Yes, it has defaultTriggers hudson.plugins.emailext.plugins.trigger.FailureTrigger_-DescriptorImpl replacesList/ defaultRecipientProviders hudson.plugins.emailext.plugins.recipients.DevelopersRecipientProvider/ /defaultRecipientProviders /hudson.plugins.emailext.plugins.trigger.FailureTrigger_-DescriptorImpl /defaultTriggers But in the plugin configuration, none of the checkboxes are ticked in the list of default triggers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher Nothing I can see. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher java -version openjdk version 1.7.0_80 OpenJDK Runtime Environment (build 1.7.0_80-b15) OpenJDK 64-Bit Server VM (build 24.80-b11, mixed mode) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title aristedes commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher uname -a FreeBSD delish.ish.com.au 10.1-RELEASE-p9 FreeBSD 10.1-RELEASE-p9 #0: Tue Apr 7 01:09:46 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Jenkins 1.612. I think a previous poster reported it in Linux though. I'm not the original poster... I just found this thread when I hit the same problem. For all I know this issue has been happening for a long time, since I don't often add new email messages to existing jobs. I have no clear idea when it might have started happening. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title aristedes commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Does anyone have a workaround for this? About 20% of our builds fail because of this. Running the build again and everything works. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25538) Add Phabricator as Repository Browser
aristedes
commented on JENKINS-25538
Add Phabricator as Repository Browser
To assist with the development of this, here is the pattern:
https?://${baseURL}/r${repoCode}${commitNumber}
${repoCode} is a one character code defined for the repository. It has the letter "r" before it. Really, it could all be part of the baseURL like this:
baseURL = https://phabricator.acme.com/rC
and then we just stick the commit number at the end.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @davida2009 If you want to upgrade a workspace, then the easiest way is to use Jenkins to delete the contents of the workspace entirely. Make sure the general settings has subversion set to 1.8 as the default. This upgrade will not change the behaviour of existing workspaces which were checked out in 1.7 mode. I've been using this for over a week in production and have had zero problems. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 OK, if that's the way it is supposed to work, then fine. I deleted the workspace and your upgraded plugin worked perfectly, creating a version 1.8 checkout. So that's quite enough for me to use it in production. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I upgraded to "2.5-SNAPSHOT (private-11/08/2014 10:24-jenkins)" and it installed fine. However despite changing the preference to "1.8" it did not upgrade any checked out repository. Other than that it worked fine. Will we need to manually destroy all workspaces in order to get them upgraded to 1.8? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 For all those people eagerly awaiting an outcome on this task, I can report that a commit was pushed to the main github repo about 24 hours ago which removes the customised svnkit and replaces it with the standard library. This was the main stumbling block that prevented svnkit from being upgraded (and in fact was the reason why it was such a huge task to move forward every time svnkit was upgraded). Now I think it is just about testing and then upgrading svnkit to 1.8 and more testing, so hopefully this will happen soon. Steve Christou, you have the thanks of everyone here! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Ben I think the whole problem is that no one is working on this plugin, so someone needs to step forward with the time available to do it. In my opinion, the job here is not to "upgrade svnkit". That part is trivial. The real work is to unravel the customisations made to svnkit and remove them from this project, finding other ways to solve the problems they were put in there to solve. Once we are using plain vanilla svnkit, the rest is simple. The problem is that in my cursory review it wasn't obvious why the svnkit fork was made. Some were clearer (like making some classes serializable presumably to handle Jenkins slaves) but others not. It will need some time to review if the original person who made those changes is not available to help. Here is the beginning of the analysis of the changes: https://gist.github.com/ari/f1fc75c22b92ab17a73d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Also we have a gradle toolchain that performs svn operations as part of the build process. And because svnkit cannot operate on a 1.7 repository this is holding back all our users from upgrading svn on their desktops. I did spend some time looking at the work Steve Wills contributed, but I haven't had the time to try and pull apart the long and undocumented set of changes hacked over the top of svnkit. I don't know if someone else might be able to do that, but I fear that without a contributor willing to pull this apart, we are likely to be stuck on 1.7 indefinitely. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I started adding in commit comments: https://gist.github.com/ari/f1fc75c22b92ab17a73d So far, many of the commits are around exception reporting, which might be just a cosmetic thing and could be discarded. Another commit is marked as fixed upstream. One the commits was a workaround for a problem in a fork of a Java clone of SSH. Where do we even begin unravelling all this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Kanstantsin I think you are just seeing frustration from people who don't know how else to assist. At any rate, my question is not "can we fork this plugin". Obviously anyone can do that. The real problems here are: svnkit has been modified in some way for Jenkins. My guess is that that's the root cause of the problem with upgrading. There is no documentation for this modification that I could find and when I tried to diff the modified version against the original svnkit I found it hard to know what versions to diff against. this happens every single time svn is upgraded. svnkit lags about 6 months behind svn itself, and Jenkins sometimes lags another 12 months behind that. if I put in the hours to rip out svnkit and replace it with calls to command line svn or javahl, will that change be accepted back into the project? I have no interest in maintaining my own fork of this plugin forever. alternatively, could someone document why svnkit needs to be modified so that either someone else can pick up the work or figure a way to use plain vanilla svnkit? I am guessing that this is the bulk of the work needed each time svnkit updates. finally, although Kohsuke was trying to help by getting 90% of the changes done, this has effectively stopped anyone else working on the problem since we are all waiting for the last 10%. Do we continue to wait or should someone else start again? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 From the pom file: dependency groupIdorg.jenkins-ci.svnkit/groupId artifactIdsvnkit/artifactId version1.7.10-jenkins-1/version /dependency Which I think points to: https://github.com/jenkinsci/svnkit More recent changes can be seen here https://github.com/jenkinsci/svnkit/commits/master-1.8.x but this is 40 commits behind master, so I'm not sure what exactly needs merging. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @steve That's helpful. Do you want to try that again but against the master-1.8.x branch and svnkit 1.8. Maybe we can figure out what is going on. There seems to be a bunch of things around exception handling (perhaps to get better exceptions into Jenkins logs) and some things to do with authentication. There are also a bunch of whitespace (and import) changes that have no effect. Were these changes ever submitted to svnkit for merging? I don't know where to start looking for such a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Looks like svnkit-jenkins is 1.8.3 given this modified-1.8/svnkit/src/main/java/org/tmatesoft/svn/util/Version.java So perhaps the diff to 1.8.3 is even less. Once you get past the changes to imports, gitignore, pom, etc. then the changes don't look significant. I wonder what is needed to remove them entirely? I assume there was a good reason for them originally. Perhaps we need to find the commits one at a time. For example, here is one: https://github.com/jenkinsci/svnkit/commit/e48e3376b1a6b8b923a313f160456529c67f7dd1 But the commit message doesn't tell us anything useful about WHY this was done. What problem was solved? Maybe something to do with sending configuration to a Jenkins slave? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Kohsuke since this plugin isn't a high priority for core Jenkins developers, what can the community do to get this moving? Can we rip out svnkit entirely from this plugin and instead rely on svn binaries? At least that way we will not be 18 months behind every svn release. Although it might not seem important that Jenkins be on the latest release, this is causing a lot of pain to some of us since we have to maintain two completely separate toolchains to support developers (who have moved to 1.8 12 months ago) and our special svn commit process inside Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-9505) Add description as release #${release.version}
aristedes
commented on JENKINS-9505
Add description as release #${release.version}
I no longer care about this feature since I've moved away from maven.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Thanks for your tireless work on this project. Out of interest, is svnkit still forked from the official release or have you been able to go back to the main release so that future upgrades will be simpler and less work? Also, is this plugin set to automatically upgrade the working copy or only when we try to tag or write to the wc? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I think it is pointless being narky about it. I'd love for this to be done, but it appears that Jenkins is using a modified svnkit build which might need to be reviewed and merged. I looked through github to see if I could help, but it was not immediately obvious why or how svnkit was forked. Hopefully whatever patch was required is no longer needed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
aristedes commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Please note that svnkit 1.8 final has now been released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15457) Passwords leaked in logs
aristedes commented on JENKINS-15457 Passwords leaked in logs Here is the output from a similar run of our maven plugin: [INFO] --- maven-release-plugin:2.1:prepare (default-cli) @ services --- [INFO] Verifying that there are no local modifications... [INFO] ignoring changes on: pom.xml.next, release.properties, pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag [INFO] Executing: /bin/sh -c cd /var/hudson/workspace/onCourse-services svn --username andrey --password '*' --no-auth-cache --non-interactive status [INFO] Working directory: /var/hudson/workspace/onCourse-services [INFO] Ignoring SNAPSHOT depenedencies and plugins ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15457) Passwords leaked in logs
aristedes edited a comment on JENKINS-15457 Passwords leaked in logs Here is the output from a similar run of the maven plugin: [INFO] --- maven-release-plugin:2.1:prepare (default-cli) @ services --- [INFO] Verifying that there are no local modifications... [INFO] ignoring changes on: pom.xml.next, release.properties, pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag [INFO] Executing: /bin/sh -c cd /var/hudson/workspace/onCourse-services svn --username andrey --password '*' --no-auth-cache --non-interactive status [INFO] Working directory: /var/hudson/workspace/onCourse-services [INFO] Ignoring SNAPSHOT depenedencies and plugins ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15457) Passwords leaked in logs
aristedes created JENKINS-15457 Passwords leaked in logs Issue Type: Bug Assignee: Gregory Boissinot Components: gradle Created: 10/Oct/12 6:33 AM Description: Adding a password type parameter to a build causes that password to be passed to gradle like this: -Dpassword=mySecret This is fine, but the password should be obfuscated with * in the logs. I suspect this line is wrong https://github.com/jenkinsci/gradle-plugin/blob/master/src/main/java/hudson/plugins/gradle/Gradle.java#L215 and I know other jenkins plugins handle this properly, but I'm not sure of the exact fix. Project: Jenkins Priority: Critical Reporter: aristedes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15458) Pass parameters with -P
aristedes created JENKINS-15458 Pass parameters with -P Issue Type: Improvement Assignee: Gregory Boissinot Components: gradle Created: 10/Oct/12 6:35 AM Description: Right now all parameters are passed to gradle with -D. It would be more convenient in the gradle world to pass them with -P. Perhaps a switch: Pass parameters to gradle as: [ drop down list ] don't pass any parameters as gradle parameters (-P) as Java parameters (-D) Project: Jenkins Priority: Major Reporter: aristedes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
aristedes commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request I found the cause of one of the enormous confusions with this plugin for me. If you have a matrix build, then: on the server (not the slave) at the unguessable path of /jobs/jobname/configurations/axis-foo/bar/axis-foo1/bar1/subversion.credentials you will find the old cached credentials. In all my testing trying to solve the original problems with svnkit upgrade, I changed the user and reset the password. It would have been great if somewhere jenkins would have reported which user it was trying to use. Also, deleting the job from the client, doesn't clear the credentials buried against every axis on the server. Why are they on every axis? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13859) Emulate clean check out seems to fail after upgrading to v1.4 of subversion plugin
aristedes commented on JENKINS-13859 Emulate clean check out seems to fail after upgrading to v1.4 of subversion plugin This also happens for me with 1.7 workspace and 1.7 subversion server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13835) upgrading Subversion Plugin to 1.40 totally ruined our CI server
[
https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163307#comment-163307
]
aristedes commented on JENKINS-13835:
-
I can report a very similar issue. The Subversion 1.7.4 server. 1.40 svn
jenkins plugin. Pre-existing 1.6 workspace, and Jenkins set to use a 1.7
checkout format. The problem goes away if you choose 1.6 as the workspace
format.
{code}
ERROR: Failed to update https://acme.com/ish/angel/trunk
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /ish/!svn/vcc/default
failed
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:328)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
at
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557)
at
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414)
at
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324)
at
org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27)
at
org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11)
at
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391)
at
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Caused by: svn: E175002: REPORT /ish/!svn/vcc/default failed
at
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 33 more
{code}
Looks like it tries to upgrade the workspace and fails.
upgrading Subversion Plugin to 1.40 totally ruined our CI server
Key: JENKINS-13835
URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
Project: Jenkins
Issue Type: Bug
Components: subversion
Environment: Jenkins ver. 1.460; Subversion Plugin ver. 1.40, 1.39;
Windows Server 2003 R2 x64 SP2; Subversion server ver. 1.6.16.
Reporter: pancake
Labels: plugin, subversion, windows
Updating Subversion Plugin to 1.40 caused multiple bugs. Rolling back to 1.39
resulted to {color:red}complete inability to perform a checkout. CI server is
totally unusable now.{color}
*Issue #1*
After updating to Subversion Plugin to 1.40 (from 1.39) this exception
started occurring _sometimes_ (various salves, various jobs):
{quote}
Checking out a fresh workspace because there's no workspace at
C:\_JenkinsCI\workspace\XXX
Cleaning local Directory .
[JIRA] (JENKINS-11120) Add a possiblity to skip/override the normal build in case of a release.
[ https://issues.jenkins-ci.org/browse/JENKINS-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163055#comment-163055 ] aristedes commented on JENKINS-11120: - Peter, do you have any further thoughts about allowing us to suppress or override the regular build goals for a maven project with this release plugin? Is that something that it is likely you'll be able to add? It would make such a big different to being able to better support the maven release process. Add a possiblity to skip/override the normal build in case of a release. Key: JENKINS-11120 URL: https://issues.jenkins-ci.org/browse/JENKINS-11120 Project: Jenkins Issue Type: New Feature Components: release Reporter: Krzesmir Florek Assignee: Peter Hayes It'd be really cool to be able to run a special release build instead of the normal one, either by skipping the normal one (and defining the special build in pre-/post-actions) or by overriding it by a defined release actions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
