[JIRA] [publish-over-ssh] (JENKINS-17771) Allow replacement of username with build params
Johannes Haseitl created JENKINS-17771 Allow replacement of username with build params Issue Type: Bug Affects Versions: current Assignee: bap Components: publish-over-ssh Created: 29/Apr/13 11:29 AM Description: In the current version only transfer parameters seem to be able to replaced by build parameters. But in some cases it would be really usefuly to let credentials be replaced as well, especially the username. Project: Jenkins Priority: Major Reporter: Johannes Haseitl 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] [publish-over-ssh] (JENKINS-17771) Allow replacement of username with build params
Johannes Haseitl updated JENKINS-17771 Allow replacement of username with build params Change By: Johannes Haseitl (29/Apr/13 11:29 AM) Issue Type: Bug NewFeature 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-16035) Publish Over SSH - With SFTP GET
Johannes Haseitl commented on JENKINS-16035 Publish Over SSH - With SFTP GET I'd very welcome that feature. I'd like to use that functionality to backup a database dump and pull it to the jenkins 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 -- 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-16914) Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo
Johannes Haseitl commented on JENKINS-16914 Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo Hi Nicolas, do I understand that "fix" right: instead of providing an alias you use the URI directly, so no specified alias is set? If so, we might get problems with functionality that relies on a given remote alias. For example the "git publish" plugin uses a remote alias to push specific branches to. In that case, wouldn't it better to ensure, the given specification was set as remote alias. I currently see the method GitClient:setRemoteUrl() that could help. But I'm not really sure, as I do not get the whole architecture yet. 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-16914) Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo
Johannes Haseitl commented on JENKINS-16914 Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo I'm having the same issue. The repository in the workspace only contains the alphabetically first remote name (I used "gitolite" and "zdc" - only "gitolite" appears). Cloning the remote Git repository Cloning repository ssh://gitolite@XXX/sandbox_derhasi git --version git version 1.7.10.4 Fetching upstream changes from gitolite Fetching upstream changes from zdc ERROR: Problem fetching from zdc / zdc - could be unavailable. Continuing anyway. hudson.plugins.git.GitException: Command "/usr/bin/git fetch -t zdc +refs/heads/master:refs/remotes/zdc/master" returned status code 128: stdout: stderr: fatal: 'zdc' does not appear to be a git repository fatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:772) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:738) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:160) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:787) at hudson.FilePath.act(FilePath.java:769) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:573) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) I tried to find the specific lines of code in github, but as I'm no java guy, I really did not get anything Would be great someone could fix 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/groups/opt_out.
