gitlab-ci not rebuild successful tests on same commit (new branch)
I was expecting to already find this discussed but I failed to do so. I recently pushed some changes to a branch BranchB which was coming directly off BranchA. Once the tests succeeded I pushed BranchB back to BranchA. There had been no other work on the BranchA so the BranchB and BranchA were now pointing to the exact same commit, which had been tested on BranchB before I had pushed to BranchA (some had been manually cancelled by me because I knew they were OK).
However, gitlab-ci still triggered a full rebuild, something I would find excessive to be activated by default (I suppose in some rare cases people still want this for reasons I am not able to think of right now). If I go to the list of builds on BranchA's most recent commit I see a list also including the builds already done on BranchB. If I go to BranchB the commit is marked as "Running" even though the tests were completed before I pushed the changes back to BranchA. On some level I feel even gitlab-ci is agreeing with my logic.
In my mind it would make more sense that when I do this, gitlab-ci should only rebuild those tests that either failed or were cancelled. If a test has already succeeded for a given commit I would think that is sufficient for most use cases.
I am running the latest GitLab CE 8.3.4 on a CentOS7 machine.