|
||||||||
|
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/groups/opt_out.
It looks like both builds were from the same revision: 49a2a30aeaf30151eec8da43e1cacfc9b89ad8a5, which is not the most recent version. That was the Feb4 checkin by De Loof (according to my Sourcetree copy of that repo link:
https://github.com/MarkEWaite/git-plugin.git
My jenkins system isn't pulling in the latest code off that fork for some reason. So to eliminate my jenkins system, I built directly from my sourcetree clone of that repo using the same command. I deployed that 2.0.2 version to my jenkins server.
Then I repeated the test by enabling SCM polling. Again, I get the same message with the same letters upper case that you expected to see lower case.
Looks like I needed to be checkign out a different branch, not just master from that repo URL. I'll report back after I get my brain engaged and use the right branch.