This should be baked into the baseline Jenkins functionality. However
here's a possible workaround:
I have a similar issue with tfs plugin. It appears Jenkins does not list
commit message in recent changes during the first build. However...There
is a file called "changelog.xml" in the build
Kevin,
I agree with you. How can that be implemented?
All,
It appears to me that Jenkins does not work well with this use case:
* master HEAD is release version 1 (v1) of product.
* 4 features ABCD that are implemented on git branches ABCD respectively
based on v1
* Jenkins project to build
I think for this use case just showing the commits since the branch point would
be an acceptable compromise. If the branch includes commits (from its parent
branch) that have not been built in another job, I don't think there is any
practical way the plugin could figure that out (or that doing s
git-plugin maintain the last build per branch, but dones not try to
"discover" when a branch was created compared to previous builds. Not
trivial to implement
2013/3/21 Brian Jones
> Is it possible to get Jenkins to detect and report "Changes" for the first
> commit on a new branch/build?
>
> I'
Is it possible to get Jenkins to detect and report "Changes" for the first
commit on a new branch/build?
I'm setting up feature based development in git:
* Feature branches are named after an issue ID (e.g., JIRA issue ID)
* Feature branches based on git master branch
* Commits to feature branch
