Issue #15621 wontfix
Asw Sat
created an issue

I don't want to commit and push. I have modified some code on my local. I want to verify, if all the tests pass, with out doing the commit. Is there a way to upload a diff to the pipelines.

Basically, I should upload my local changes or changesets with out commit and push. This helps to avoid lot of unnecessary commits or experimental commits.

Sometimes, webdriver tests are very flaky. We make changes and the changes should be pushed for testing on the bitbucket pipelines.

Comments (5)

  1. Matt Ryall staff

    The best way to do this is to create a branch, add a branch-specific pipeline configuration in bitbucket-pipelines.yml, then push the branch to Bitbucket to build it.

    This way commits on your branch won't affect the rest of your team, and if you end up not wanting to make the changes permanent, you can delete the branch from your repository and the commits will all disappear.

  2. Asw Sat reporter

    Dear Matt, What you said is a possibility.

    We create a branch and push it for bitbucket build. We use for webdriver testing and junit tests. The test won't pass all, especially the webdriver. Sometimes, there may be a good change, which is required. So, we cannot use this approach of deleting the branch. If the branch is deleted the good changes are gone. Also, it is difficult to merge only good commits from the branch to the main branch.

    It is good if you give the option of running tests with out commit. This is done in many big companies. I was in Google, and this was followed. We just submit the patch/diff.

    Thanks.

  3. Matt Ryall staff

    Okay, thanks for clarifying your request. Building from a patch is unlikely to ever be supported in Pipelines, both for architectural reasons and because the majority of users do not need this.

    On the architecture side, Pipelines is built as a Bitbucket add-on that listens for push events in Bitbucket. Changing this would require a lot of additional work.

    On the use case side, we're designing primarily for teams using modern Git workflows, where the dominant approach is using topic branches for development, CI/testing on the branch, then merging via pull request into master or another shared branch for (preferably automated) deployment. For the best experience with Bitbucket and Pipelines, you may want to consider adapting your workflow to match these conventions.

  4. Log in to comment