This build is, in fact, successful. All build artifacts are available.
The reason for Jenkins to report is as failed is because it couldn't add the tag 4829 in it's local repo, because it was already there. That, on the other hand, was because the previous build had already added the tag 4829 in it's local git repo, but couldn't push it, because for some reason GitHub was not accessible. The log says: "error: Couldn't resolve host 'github.com' while accessing https://github.com/jitsi/jitsi/info/refs"
I pushed the tag 4829 to GitHub and everything is alright now.
I added a check to the scripts for the availability of GitHub before trying to add and push tags.
On 11.септ..2013, at 20:07, Jitsi Jenkins wrote:
jitsi - Build # 4829 - Still Failing
Started by an SCM change
[damencho] Adds message when otr session is enabled whether chat logging history is on or off and an option to open menu to change this settings.
All tests passed
cruisecontrol mailing list
Unsubscribe instructions and other list options: