Pipelines doesn't run on first commit

Issue #13235 resolved
Wayne Leroux created an issue

I've found that pipelines doesn't kick off for the very first commit in a new repository. Doing a second commit works fine. While the workaround is pretty simple, it may be valuable to have working none-the-less.

As a new user to Pipelines, I try to get things to work with as simple a build as possible to discover how it works. A simple hello-world repository with bitbucket-pipelines.yml is enough to validate the feature. However, when I tried this out, it didn't kick off pipelines. Furthermore, it wasn't clear what I did wrong. As a new user to Pipelines, I ended up having to look up documentation, references, and be left scratching my head about what's wrong.

Comments (4)

  1. Joshua Tjhin Account Deactivated

    Hey Wayne,

    That's interesting. Pipelines is supposed to run on the first commit to the repository if you went through the steps in the Bitbucket UI. Could you describe the steps you took? Did you commit the bitbucket-pipelines.yml file from your local machine or via the Bitbucket UI?

    Also, was this your 1st or 2nd repository with Pipelines?

  2. Wayne Leroux reporter

    Hey Joshua,

    Here's the steps to reproduce:

    1. Create new repository on development machine
    2. Create initial commit with a bitbucket-pipelines.yml 2.1. My initial commit was a simple hello world application in Java using gradle with pipelines configured
    3. Push changes to a brand new repository
    4. Expected pipelines to kick off

    It's just for the very first commit; I try to start any new repository with CI working. I did this to try out bitbucket pipelines to get exposed to it. Otherwise, the product works like a charm and there is a very simple workaround (i.e.: do a dummy commit after.) The value is more on the optics; a new developer might just give up rather then investigating any further.

    It was on the first repository I created. It happened on the second repository as well when I was trying to identify the issue.

  3. Log in to comment