[JIRA] [svnmerge] (JENKINS-21781) Handle feature branches in subfolder correctly
Hugues Chabot created JENKINS-21781 Handle feature branches in subfolder correctly Issue Type: Improvement Affects Versions: current Assignee: Hugues Chabot Components: svnmerge Created: 12/Feb/14 4:13 AM Description: Using a slash '/' in a feature branch name like features/issue-123 will create the Subversion branch correctly but will create two Jenkins jobs: issue-123 project-features/issue-123 The expected result is one job with the long name (preferably using dashes '-' instead of 'slashes' for consistency). Project: Jenkins Priority: Minor Reporter: Hugues Chabot 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] [svnmerge] (JENKINS-11012) Ability to provide merge comments to svn command
Hugues Chabot assigned JENKINS-11012 to Hugues Chabot Ability to provide merge comments to svn command Change By: Hugues Chabot (13/Feb/14 4:00 AM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge] (JENKINS-11012) Ability to provide merge comments to svn command
Hugues Chabot started work on JENKINS-11012 Ability to provide merge comments to svn command Change By: Hugues Chabot (13/Feb/14 4:00 AM) Status: Open InProgress 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] [svnmerge] (JENKINS-10893) Error when using Integrate to upstream upon successful build on branch project
Hugues Chabot assigned JENKINS-10893 to Hugues Chabot Error when using Integrate to upstream upon successful build on branch project Change By: Hugues Chabot (13/Feb/14 4:46 AM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge] (JENKINS-10893) Error when using Integrate to upstream upon successful build on branch project
Hugues Chabot started work on JENKINS-10893 Error when using Integrate to upstream upon successful build on branch project Change By: Hugues Chabot (13/Feb/14 4:46 AM) Status: Open InProgress 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] [svnmerge] (JENKINS-10893) Error when using Integrate to upstream upon successful build on branch project
Hugues Chabot commented on JENKINS-10893 Error when using Integrate to upstream upon successful build on branch project Is this bug still in version 1.2 ? 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] [svnmerge] (JENKINS-11380) Creating a branch in a subfolder of /branches creates two Jenkins projects
Hugues Chabot resolved JENKINS-11380 as Duplicate Creating a branch in a subfolder of /branches creates two Jenkins projects Change By: Hugues Chabot (16/Feb/14 4:42 AM) Status: Open Resolved Resolution: Duplicate 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] [svnmerge] (JENKINS-24735) Add support for build parameters in Subversion URLs.
Hugues Chabot created JENKINS-24735 Add support for build parameters in Subversion URLs. Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: svnmerge Created: 17/Sep/14 2:11 AM Description: Subversion URLs can be parameterized. The plugin should substitute the URL parameters by their default values. Furthermore, the plugin should support URLs ending with @HEAD. This enhancement request comes from the following comment by Damon Overboe. The scenario is I wanted to be able to trigger older builds by passing the specific revision, so I added SVN_REVISION as a parameter, defaulting to HEAD. Set up a job Feature branch it Modify the main job to allow SVN_REVISION to be passed in as a parameter, and default it to HEAD (may not matter) and change your svn url to http://path/to/project/trunk@$SVN_REVISION then rebasing a feature will fail, complaining about the path. Also, if you set up the job initially with the @SVN_REVISION, the plug-in won't be able to find the repo when you go to feature branch it. The work-around for me is easy enough; rather than specifying the @SVN_REVISION in the URL, I just: manually cut a branch from the specific revision I want, tell the plug-in to add the feature branch (with the same name) Click OK to add the project when it warns me the branch already exists. Project: Jenkins Priority: Minor Reporter: Hugues Chabot 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] [svnmerge] (JENKINS-21916) svnmerge plugin doesn't support subersion plugin 2+
Hugues Chabot created JENKINS-21916 svnmerge plugin doesnt support subersion plugin 2+ Issue Type: Bug Affects Versions: current Assignee: Hugues Chabot Attachments: error.log Components: svnmerge Created: 21/Feb/14 6:21 PM Description: Subversion Merge Plugin fails to get authentication credentials after upgrading to Subversion Plugin 2.2. See error.log for an example of a stack trace. Workaround : Downgrade Subversion Plugin to version 1.54 Environment: Jenkins 1.551 Subversion Plugin 2.2 Subversion Merge Plugin 1.3 Project: Jenkins Priority: Critical Reporter: Hugues Chabot 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] [svnmerge] (JENKINS-12495) svnmerge fails when running on a Jenkins slave
Hugues Chabot started work on JENKINS-12495 svnmerge fails when running on a Jenkins slave Change By: Hugues Chabot (27/Feb/14 3:22 AM) Status: Open InProgress 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] [svnmerge] (JENKINS-12495) svnmerge fails when running on a Jenkins slave
Hugues Chabot assigned JENKINS-12495 to Hugues Chabot svnmerge fails when running on a Jenkins slave Change By: Hugues Chabot (27/Feb/14 3:22 AM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge] (JENKINS-12495) svnmerge fails when running on a Jenkins slave
Hugues Chabot commented on JENKINS-12495 svnmerge fails when running on a Jenkins slave Just to be sure. Does rebasing also fail? Does frequently failing means that it is sometime successful? If the problem is intermittent, could it be a timeout issue? (I'm merely speculating here.) Also, if you have access to the HTTP server error logs it could help us troubleshooting this issue. 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] [svnmerge] (JENKINS-12495) svnmerge fails when running on a Jenkins slave
Hugues Chabot commented on JENKINS-12495 svnmerge fails when running on a Jenkins slave Where I work, we neither use slaves nor automatic reintegration. I setup a simple ssh-slave in other to test the plugin but I used de svn protocol. So, I guess I will have to setup a webdav interface in order to reproduce this issue. Here is how one could manually integrate a feature branch like svnmerge. Check if there is something to integrate with svn log If there is something to integrate, switch to upstream with svn switch upstream_url Reintegrate the branch with svn merge --reintegrate branch_url . If there are conflicts abort, otherwise svn commit and note the revision number as REV Switch back to the feature branch with svn switch branch_url Record the integration in the feature branch to avoid rebasing it whit svn merge --record-only --change REV upstream_url . and svn commit The last part is from https://wiki.apache.org/subversion/KeepingReintegratedBranchAlive. 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] [svnmerge] (JENKINS-12495) svnmerge fails when running on a Jenkins slave
Hugues Chabot commented on JENKINS-12495 svnmerge fails when running on a Jenkins slave Rebasing is usually called a catch-up merge. Merge all the new modifications from the upstream with svn merge upstream_url Resolve any conflits Then svn commit 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] [svnmerge] (JENKINS-22284) new field in the feature branch creation form, to manage multi-project repository layout
Hugues Chabot commented on JENKINS-22284 new field in the feature branch creation form, to manage multi-project repository layout The Multi Project Layout is documented in the Subversion Book. I think it should be well supported by the plugin. However, is it possible to handle that directory structure in a general way? For instance, given a SVN path prefix/(trunk|branches)(/suffix)? and a branch name feature, we could create the new branch in prefix/branches/feature/suffix. In the case of a multi projects layout, suffix is the sub-project name, isn't it? In the end, the advanced options could be the complete path of the branch/tag with default values based on your proposal. 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] [svnmerge] (JENKINS-16723) NPE when performing integration.
Hugues Chabot resolved JENKINS-16723 as Fixed NPE when performing integration. The issue has been resolved while fixing JENKINS-12495. Change By: Hugues Chabot (05/Apr/14 1:53 AM) Status: InProgress Resolved Resolution: Fixed 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] [svnmerge] (JENKINS-12183) SVNMerge plugin does not work with SVN plugin version 1.37, but works with 1.34
Hugues Chabot resolved JENKINS-12183 as Wont Fix SVNMerge plugin does not work with SVN plugin version 1.37, but works with 1.34 SVNMerge plugin now use Subversion plugin 2.2. This issue is no longer relevant. Change By: Hugues Chabot (05/Apr/14 1:57 AM) Status: Open Resolved Resolution: WontFix 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] [svnmerge] (JENKINS-22284) new field in the feature branch creation form, to manage multi-project repository layout
Hugues Chabot commented on JENKINS-22284 new field in the feature branch creation form, to manage multi-project repository layout Suppose one create a new feature branch named feature. Here are some examples of the default branch URL based on the upstream URL. Upstream SVN URL Branch SVN URL (default) http://svnserver/trunk http://svnserver/branches/feature http://svnserver/branches/other http://svnserver/branches/feature http://svnserver/trunk/subproject http://svnserver/branches/subproject/feature http://svnserver/branches/subproject/other http://svnserver/branches/subproject/feature http://svnserver/project/trunk http://svnserver/project/branches/feature http://svnserver/project/branches/other http://svnserver/project/branches/feature These examples differ from what is proposed in this issue's first comment. I am used to see the feature branch name at the end of the URL but it may be a matter of personal taste. 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] [svnmerge] (JENKINS-22284) new field in the feature branch creation form, to manage multi-project repository layout
Hugues Chabot commented on JENKINS-22284 new field in the feature branch creation form, to manage multi-project repository layout I understand, it makes a lot of sense to support the "multi project layout with closely related project" too. 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] [svnmerge] (JENKINS-23107) Rebase not working for simple setup
Hugues Chabot commented on JENKINS-23107 Rebase not working for simple setup Can you confirm if the bug persist after the project is build for the first time? I suspect this happens because the workspace did not exists. There is a pull request regarding 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] [svnmerge] (JENKINS-23107) Rebase not working for simple setup
Hugues Chabot commented on JENKINS-23107 Rebase not working for simple setup Thank you. Let's keep the issue open until the pull request is merged. 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] [svnmerge] (JENKINS-15615) Feature Branch does not copy all modules
Hugues Chabot commented on JENKINS-15615 Feature Branch does not copy all modules Please provide more information regarding the expected behaviour. Do we want to create a feature branch for every module? How we handle rebase/integrate failure in that case (it is hard to ensure atomicity)? Do we want to create a feature branch for only one module? Which one? Can we assume a convention or we must provide a way to select the module to branch? 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] [svnmerge] (JENKINS-15615) Feature Branch does not copy all modules
Hugues Chabot assigned JENKINS-15615 to Hugues Chabot Feature Branch does not copy all modules Change By: Hugues Chabot (28/May/14 8:46 PM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge] (JENKINS-23107) Rebase not working for simple setup
Hugues Chabot assigned JENKINS-23107 to Hugues Chabot Rebase not working for simple setup Change By: Hugues Chabot (28/May/14 8:47 PM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge] (JENKINS-23371) Manually-triggered integration
Hugues Chabot resolved JENKINS-23371 as Not A Defect Manually-triggered integration The manual reintegration action is at the level of the build (not the project). In your project, select a build and then "Integrate branch". Change By: Hugues Chabot (09/Jun/14 5:12 PM) Status: Open Resolved Assignee: KohsukeKawaguchi HuguesChabot Resolution: NotADefect 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] [svnmerge] (JENKINS-23393) Auto Rebase on Main branch fails
Hugues Chabot assigned JENKINS-23393 to Hugues Chabot Auto Rebase on Main branch fails Change By: Hugues Chabot (11/Jun/14 4:00 PM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge] (JENKINS-23371) Manually-triggered integration
Hugues Chabot commented on JENKINS-23371 Manually-triggered integration The Integrate Branch action will be available if (and only if) the build if from a Feature Branch project that has only one Subversion module. Can you check if the builds that are not re-integrable have more than one Subversion URLs? 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] [svnmerge] (JENKINS-23393) Auto Rebase on Main branch fails
Hugues Chabot commented on JENKINS-23393 Auto Rebase on Main branch fails This is a configuration error. I don't think it is correct to quietly ignore it. However, it is possible to add a global settings for the plugin (e.g. "Skip rebase/integration action when upstream is undefined") 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] [svnmerge] (JENKINS-23371) Manually-triggered integration
Hugues Chabot commented on JENKINS-23371 Manually-triggered integration It makes sense to ignore the content of external SVN repositories for rebase/integrate action. 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] [svnmerge] (JENKINS-23393) Auto Rebase on Main branch fails
Hugues Chabot commented on JENKINS-23393 Auto Rebase on Main branch fails After investigation, manual rebase and integrate action are unavailable if the project does not build a Subversion feature branch. Therefore, it makes sense to skip the automatic rebase action in that case. Furtheremoe, it is consistent with the documentation which states that This works in conjunction with the "This project builds a Subversion feature branch" checkbox above. 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] [svnmerge] (JENKINS-23796) Improve error handling when upstream is invalid
Hugues Chabot created JENKINS-23796 Improve error handling when upstream is invalid Issue Type: Task Assignee: Hugues Chabot Components: svnmerge Created: 15/Jul/14 1:02 PM Description: When a project builds a Subversion feature branch but the upstream project is undefined or invalid, actions should fails gracefully with a relevant error message. Furthermore, the project main page could display a warning like this. Subversion Merge Tracking Upstream project is invalid. Project: Jenkins Priority: Trivial Reporter: Hugues Chabot 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] [svnmerge] (JENKINS-6851) [svnmerge-plugin] Add support for merging from upstream before building.
Hugues Chabot resolved JENKINS-6851 as Fixed [svnmerge-plugin] Add support for merging from upstream before building. Change By: Hugues Chabot (19/Jul/14 4:18 AM) Status: Open Resolved Resolution: Fixed 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] [svnmerge-plugin] (JENKINS-25739) Wrong revision used for upstream integration
Hugues Chabot assigned JENKINS-25739 to Hugues Chabot Wrong revision used for upstream integration Change By: Hugues Chabot (23/Nov/14 1:49 AM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge-plugin] (JENKINS-25217) Do not force automatic rebase upon successfull integration to upstream
Hugues Chabot started work on JENKINS-25217 Do not force automatic rebase upon successfull integration to upstream Change By: Hugues Chabot (23/Nov/14 3:57 AM) Status: Open InProgress 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] [svnmerge-plugin] (JENKINS-25942) Define permission for Rebase and Integrate actions
Hugues Chabot created JENKINS-25942 Define permission for Rebase and Integrate actions Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 06/Dec/14 2:07 AM Description: Add two permissions under the SVNMerge group; Integrate and Rebase for the respective actions, instead of using the Job/Configure permission. Project: Jenkins Priority: Minor Reporter: Hugues Chabot 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] [svnmerge-plugin] (JENKINS-25769) Rebase build action cannot be triggered from Promoted Builds
Hugues Chabot commented on JENKINS-25769 Rebase build action cannot be triggered from Promoted Builds Applying the fix for JENKINS-14725 (https://github.com/jenkinsci/svnmerge-plugin/pull/24) should fix this issue. 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] [svnmerge-plugin] (JENKINS-23371) Manually-triggered integration
Hugues Chabot commented on JENKINS-23371 Manually-triggered integration Please verify the configuration of the "Feature Branch" job. "This project builds a Subversion feature branch" must be checked. "Upstream project name" must be the name of the job that build the trunk. 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-26771) Error when using Integrate to upstream upon successful build on branch project
Hugues Chabot created JENKINS-26771 Error when using Integrate to upstream upon successful build on branch project Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: subversion-plugin, svnmerge-plugin Created: 04/Feb/15 2:05 AM Description: As mentionned by hcguersoy in this comment. svnmerge plugin version 2.5 and subversion plugin version 2.5. The Integration Publisher fails with a NPE in SVNRevisionState.getRevision. ERROR: Publisher jenkins.plugins.svnmerge.IntegrationPublisher aborted due to exception java.lang.NullPointerException at hudson.scm.SVNRevisionState.getRevision(SVNRevisionState.java:24) at jenkins.plugins.svnmerge.IntegrateAction.getSvnInfo(IntegrateAction.java:149) at jenkins.plugins.svnmerge.IntegrateAction.perform(IntegrateAction.java:165) at jenkins.plugins.svnmerge.IntegrationPublisher.perform(IntegrationPublisher.java:51) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Project: Jenkins Priority: Minor Reporter: Hugues Chabot 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] [svnmerge-plugin] (JENKINS-10893) Error when using Integrate to upstream upon successful build on branch project
Hugues Chabot commented on JENKINS-10893 Error when using Integrate to upstream upon successful build on branch project This is not the same issue. I created JENKINS-26771 for your issue. 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] [svnmerge-plugin] (JENKINS-26347) Credentials not found for merge from mainline
Hugues Chabot commented on JENKINS-26347 Credentials not found for merge from mainline Can you confirm that the build was run on a slave ? If yes, can you tell me what kind of slave and if you have the same problem when the build runs on the master. Also, can you tell me the protocol of the SVN URL ? http, https, svn ? 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot updated JENKINS-26280 Missing Integrate Branch from feature branch builds Unchecking "Ignore externals" option should re-enable "Integrate action". Change By: Hugues Chabot (09/Jan/15 2:24 AM) Attachment: jenkins-26280.png 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] [svnmerge-plugin] (JENKINS-26347) Credentials not found for merge from mainline
Hugues Chabot started work on JENKINS-26347 Credentials not found for merge from mainline Change By: Hugues Chabot (09/Jan/15 2:57 AM) Status: Open InProgress 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] [svnmerge-plugin] (JENKINS-26347) Credentials not found for merge from mainline
Hugues Chabot assigned JENKINS-26347 to Hugues Chabot Credentials not found for merge from mainline Change By: Hugues Chabot (09/Jan/15 2:57 AM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot started work on JENKINS-26280 Missing Integrate Branch from feature branch builds Change By: Hugues Chabot (09/Jan/15 2:11 AM) Status: Open InProgress 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot assigned JENKINS-26280 to Hugues Chabot Missing Integrate Branch from feature branch builds Change By: Hugues Chabot (09/Jan/15 2:10 AM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing Integrate Branch from feature branch builds I did some investigation and I found that Integration Action does not work if the feature branch job has more that one Subversion modules. If the job that builds your feature branch has more than one module. Then it is the cause of this issue. I just wanted to confirm that. 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing Integrate Branch from feature branch builds No, I am not concerned about svn:externals this time. Jenkins Subversion plugin allows to configure more than one modules. This can be checked in the configuration page, under Source Code Management section. 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] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot started work on JENKINS-26357 Unable to create a Feature Branch Change By: Hugues Chabot (09/Jan/15 11:38 AM) Status: Open InProgress 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] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot created JENKINS-26357 Unable to create a Feature Branch Issue Type: Bug Assignee: Hugues Chabot Components: svnmerge-plugin Created: 09/Jan/15 11:38 AM Description: I cannot create a "Feature Branch" when using svnmerge plugin 2.4 and subversion plugin 2.5 but I can if I use subversion plugin 2.4.x. _Note: If I create the SVN branch and the Jenkins job manually, I still cannot rebase (see JENKINS-26347). Here is the stack trace. javax.servlet.ServletException: hudson.scm.SubversionSCM.createAuthenticationProvider(Lhudson/model/AbstractProject;Lhudson/scm/SubversionSCM$ModuleLocation;)Lorg/tmatesoft/svn/core/auth/ISVNAuthenticationProvider; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at
[JIRA] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot edited a comment on JENKINS-26280 Missing Integrate Branch from feature branch builds Integration won't work if if the SVN module "Ignore externals" option is checked. So, unless it is required to ignore svn:external, uncheking the option should re-enable Integration action. 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing Integrate Branch from feature branch builds Greg Hansen This is a compatibility issue with subversion-plugin 2.5. Please downgrade to subversion plugin 2.4 if you can. This is not related to the current issue. But it is a major issue I will fix in the next days. 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] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot
updated JENKINS-26357
Unable to create a Feature Branch
Change By:
Hugues Chabot
(09/Jan/15 11:39 AM)
Description:
IcannotcreateaFeatureBranchwhenusingsvnmergeplugin2.4andsubversionplugin2.5butIcanifIusesubversionplugin2.4.x._Note:IfIcreatetheSVNbranchandtheJenkinsjobmanually,Istillcannotrebase(seeJENKINS-26347).
_
Hereisthestacktrace.{noformat}javax.servlet.ServletException:hudson.scm.SubversionSCM.createAuthenticationProvider(Lhudson/model/AbstractProject;Lhudson/scm/SubversionSCM$ModuleLocation;)Lorg/tmatesoft/svn/core/auth/ISVNAuthenticationProvider; atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:729) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
[JIRA] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot
updated JENKINS-26357
Unable to create a Feature Branch
Change By:
Hugues Chabot
(09/Jan/15 11:39 AM)
Description:
IcannotcreateaFeatureBranchwhenusingsvnmergeplugin2.4andsubversionplugin2.5butIcanifIusesubversionplugin2.4.x.
_Note
Note
:IfIcreatetheSVNbranchandtheJenkinsjobmanually,Istillcannotrebase(seeJENKINS-26347).
_
Hereisthestacktrace.{noformat}javax.servlet.ServletException:hudson.scm.SubversionSCM.createAuthenticationProvider(Lhudson/model/AbstractProject;Lhudson/scm/SubversionSCM$ModuleLocation;)Lorg/tmatesoft/svn/core/auth/ISVNAuthenticationProvider; atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:729) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
[JIRA] [svnmerge-plugin] (JENKINS-26347) Credentials not found for merge from mainline
Hugues Chabot commented on JENKINS-26347 Credentials not found for merge from mainline This is due to a compatibility issue with Subversion plugin 2.5. It can be resolved temporarly by downgrading Subversion plugin to version 2.4. In other word, Subversion Merge plugin 2.4 is not compatible with Subversion plugin 2.5. 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] [svnmerge-plugin] (JENKINS-23371) Manually-triggered integration
Hugues Chabot commented on JENKINS-23371 Manually-triggered integration Jackey Cheung you are right. Job created as "Feature Branch" should be correct but the NullPointerException you observed could be caused by an invalid job configuration. The other explanation is that the project contains multiple Subversion sources (if it contains svn:externals for instance). This can be confirmed by looking at the build page (under Revisions). I know this kind of project is not fully supported but it think it should be. Please open a new issue if it is your case. 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing Integrate Branch from feature branch builds Is it possible that the job has more than one Subversion modules ? 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot edited a comment on JENKINS-26280 Missing Integrate Branch from feature branch builds How many Subversion modules does the feature branch have ? 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing Integrate Branch from feature branch builds In svnmerge-2.3, the Reintegrate Action always ignored the revision. Launching "Reintegrate" on a build actually reintegrate the HEAD revision of the feature branch instead of the revision of the build. If this is the behaviour you expected, downgrading to svnmerge could be a workaround. I am still looking to reproduce the issue on my environment. 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot edited a comment on JENKINS-26280 Missing Integrate Branch from feature branch builds In svnmerge-2.3, the Reintegrate Action always ignored the revision. Launching "Reintegrate" on a build actually reintegrate the HEAD revision of the feature branch instead of the revision of the build. If this is the behaviour you expected, downgrading to svnmerge-2.3 could be a workaround. I am still looking to reproduce the issue on my environment. 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot commented on JENKINS-26280 Missing Integrate Branch from feature branch builds This kind of project should be very well supported by the plugin. Are you using matrix-based access control by any changes ? New permission for Rebase and Integrate where added in the last release. 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] [svnmerge-plugin] (JENKINS-26280) Missing Integrate Branch from feature branch builds
Hugues Chabot edited a comment on JENKINS-26280 Missing Integrate Branch from feature branch builds This kind of project should be very well supported by the plugin. Are you using matrix-based access control by any chances ? New permission for Rebase and Integrate were added in the last release. 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] [svnmerge-plugin] (JENKINS-27155) Can't find the Enable Subversion Merge Tracking option in the configuration
Hugues Chabot assigned JENKINS-27155 to Hugues Chabot Cant find the Enable Subversion Merge Tracking option in the configuration Change By: Hugues Chabot (27/Feb/15 1:52 PM) Assignee: KohsukeKawaguchi HuguesChabot 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] [svnmerge-plugin] (JENKINS-27155) Can't find the Enable Subversion Merge Tracking option in the configuration
Hugues Chabot commented on JENKINS-27155 Cant find the Enable Subversion Merge Tracking option in the configuration Apparently the documentation is incorrect. The name of the option is "This project build a Subversion feature branch". 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] [svnmerge-plugin] (JENKINS-27610) Mark build as unstable on failure
Hugues Chabot created JENKINS-27610 Mark build as unstable on failure Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 26/Mar/15 1:02 AM Description: Add an option to mark the build as unstable if the merge fails. Project: Jenkins Priority: Minor Reporter: Hugues Chabot 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] [svnmerge-plugin] (JENKINS-27609) Add Support for Matrix build
Hugues Chabot created JENKINS-27609 Add Support for Matrix build Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 26/Mar/15 12:59 AM Description: Support matrix style builds. Project: Jenkins Priority: Minor Reporter: Hugues Chabot 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] [svnmerge-plugin] (JENKINS-30769) Rebase commit message should be configurable
Title: Message Title Hugues Chabot commented on JENKINS-30769 Re: Rebase commit message should be configurable If someone want to contribute, this is an issue that is reasonably easy to fix. 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] [svnmerge-plugin] (JENKINS-30769) Rebase commit message should be configurable
Title: Message Title Hugues Chabot commented on JENKINS-30769 Re: Rebase commit message should be configurable Peter Jupp some work has been done: https://github.com/jenkinsci/svnmerge-plugin/pull/29 I don't remember exactly why I did not merge the PR but if you could at least test if this PR resolve the issue for you it could really help. Thanks. 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] (JENKINS-38346) Rebase with upstream Subversion revision doesn't merge to HEAD
Title: Message Title Hugues Chabot commented on JENKINS-38346 Re: Rebase with upstream Subversion revision doesn't merge to HEAD The plugin does not simply rebase with HEAD. Instead it rebase with the SVN revision ID used in a specific build of the upstream. You can configure the rebase action to use the last build or the last stable build. You cannot change this but you can rebuild the upstream project. Or simply rebase manually. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
