Issue Type: Bug Bug
Assignee: Bertrand Paquet
Components: scm-sync-configuration
Created: 19/Jul/12 4:06 PM
Description:

Using GitHub, I hardly managed credential issues:

  • I tried to configure the repository with various URLs/protocols which all work fine inside jobs but not for that plugin, always raising the issue below
  • The server fails at committing because of
    hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness synchronizeFile
    INFO: Synchronizing file [jobs/nuxeo/config.xml] to SCM ...
    hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles
    SEVERE: [checkinFiles] Problem during commit of [[jobs/nuxeo/config.xml]] : 
    *** Please tell me who you are.
    
    Run
    
      git config --global user.email "[email protected]"
      git config --global user.name "Your Name"
    
    to set your account's default identity.
    Omit --global to set the identity only in this repository.
    
    fatal: empty ident  <[email protected]> not allowed
  • setting global config doesn't solve the issue
  • of course, those settings are already configured in the Git section
  • finally, defining those values as local settings worked

The main issues are:

  • the error message is wrong,
  • since the fix requires the repository to exist and that repository is created/deleted by the plugin, it cannot be properly configured without raising the issue before (which is an issue when working with a lot of jobs),
  • when the URLs fails at login (not for commit but for pull/push), the Jenkins server becomes unresponsive (I had to manually kill the git processes).

I don't know exactly what comes from the Git&GitHub plugins or JGit but it seems the scm_sync plugin is not using all available information, especially the user.email and user.name.

There should be a "test" button in the configuration to avoid starting initialization with repetitive failures.

Project: Jenkins
Priority: Major Major
Reporter: Julien Carsique
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

Reply via email to