|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Hey everyone, for all the ones that don't have an answer on how to fix the problem, I'll write a short guide here on what to do to make it work with a standard Mac-user. The problem many here are probably having is caused by the fact that they have created a Jenkins-daemon (by using the Shell) instead of making a full-fledged user in OSX. Following these steps has worked for me:
1. Make a new administrator user using System Preferences > Users & Groups and call him 'jenkins' and give him a password.
2. Install homebrew to install wget & jenkins using these commands in your terminal:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew install wget
brew install jenkins
3. Before starting your Jenkins CI-service, create the following dir and symlinks:
mkdir -p ~/Library/LaunchAgents
ln -sfv /usr/local/opt/jenkins/*.plist ~/Library/LaunchAgents
4. And afterward choose to either start or stop Jenkins with:
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist
launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist
5. Jenkins will currently only be accessible through 'localhost:8080'. If you want it to be accessible to other people, change this line in ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist:
find and edit: <string>-
httpListenAddress=127.0.0.1</string> TO <string>-httpListenAddress=0.0.0.0</string>Normally Jenkins should work normally now on your systems and after installing the Git SCM functionality, it shouldn't give you any further errors when trying to access your keychain for submodule-authentication. (unless the user/password are wrong and/or not present)
Happy building!