-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update sonar.sh to fail if rhc port-forward fails #11
Labels
Comments
The change should be added to the sonar.sh in each individual repo as well, but I don't want to put in issues for that... |
Updated title to generalize that Other way it can fail is if you need to authenticate with rhc command. |
Made a suggestion on #20 . I think we could also evaluate the exit code returned from mvn |
This was referenced Feb 12, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you have multiple servers configured for openshift in rhc command the sonar.sh script should handle the case when you have the wrong server used for the port-forward. Right now it fails to do the port forward but the builds continue but are not able to publish. So unless you're paying attention you might not notice.
The text was updated successfully, but these errors were encountered: