![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
testflight |
|
Created:
|
10/Nov/13 3:16 AM
|
|
Description:
|
Partially as a workaround of JENKINS-20503 bug and because I would also like to filter the change log I would like to build up the build notes myself to send to Testflight using a script. The Testflight plugin does support expanding environment variables in the build notes, but going from a script that generates arbitrary multi-line text to an environment variable usable in other build steps in Jenkins is non-trivial.
It would be nice to just bypass the environment variable and just use a file to generate the build notes for TestFlight.
|
|
Environment:
|
Any
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Dale King
|
|
|
|
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.
