Remove NOT_BUILT result and accept to build in anyway.

[bicschneider]

.. it is from the principle that it is not doing any harm..

A few scenarios:

• We are using "*" in our branches in Jenkins which causes Jenkins Git plugin to poll via workspace. Given the job identifies that no workspace is available (need to bring up slave or first time on slave, it will trigger a new built)
• First time built in this job ( new job / new Jenkins master ) -> "no workspace"
• In connection with Bitbucket.. Pushes seems to go well ( integration branch updated ), but the process fails. It means the pipeline fails and it cannot be triggered on SHA1 again as it is equal to the integration branch's SHA1.
• First time a job is set up, but no "dev" / "ready" branch yet related to branch pattern

[bicschneider]

Given that "count commit = 0" is returned then

• investigate if the SHA1 of the readyBranch and integration branch is identical.. -> Continue

  • Q: Should the readybranch be deleted?

• a "FF-only could be tried and eventually the result is that the integrationBrancxh SHA1 is checked out and continue from there.. - readyBranch is deleted?