|
The following behavior is observed when a PR is open for branch X in platform-core and a
new developer commit is made to branch X.
1. if a git commit to update the install json files or the yarn.lock is made during the
branch build by Jenkins, the open PR build that is simultaneously triggered will not use the new install json and yarn lock files committed during the branch build because they haven't been committed yet. It will, instead, use the previous versions.
2. The next problem is that a subsequent PR build will be triggered because of the commits made in branch X. This build detects that the last git commit was a CI commit and exits gracefully as designed to avoid build loops. The result is that a PR build based on the latest changes in branch X is never triggered.
In order to trigger another PR build with the latest versions of the install json and yarn lock
file, a trivial commit needs to be made to the branch.
|