|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file to build up to inject as environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:
" >TestFlightChanges
echo "
" >>TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log
1 "-format=format:$i. %s - %an\n" $hash >>TestFlightChangesfi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build
" >TestFlightChanges
fi
echo "
" >>TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" >>TestFlightChanges
echo "TestFlightChangeCount=$i" >> TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits.
I use the TestFlightChangeCount as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.