Jenkins change reports on deployment to environment

[Mark Small]

We have a GIT/JENKINS auto Build/Deploy continuous integration setup.

1) Developer pushes code to DEV git branch.

2) Jenkins is notified, it builds and deploys code to DEV environment.

3) DEV git branch is merged to BETA git branch and pushed.

4) Jenkins is notified, it builds and deploys code to BETA environment.

5) Developer emails link to BETA Job's changes URL to wider team (including non-developers).

While this system works, it breaks one of the rules of Continuous Integration/Deployment i.e. build once, deploy to multiple environments.

What we would ideally like is:

1) Developer pushes code to DEV git branch.

2) Jenkins is notified, it builds and deploys code to DEV environment.

3) DEV manually triggers BETA deploy Job, it takes the latest successful build and deploys it to the BETA environment and an email of all changes since last deploy to that environment is emails to the wider team (including non-developers).

The problem as I see it is collating the changes across many builds into one email.  Does anyone have any ideas, examples?

Thanks in advance.

MARK

CIAO