How to run a pipeline where some gradle task can only be run in a branch?

[Sudip Bhandari]

To give a context:

I am using researchgate plugin to change versions during gradle build. I want to restrict this to run only in 'develop' branch from which I will be deploying.

When I run this via bitbucket pipeline I belive bitbucket checks out to the commit (now it's in detached state as it doesn't belong to any branch) and so the build is failing.

Is there a workaround or a better alternative?

[Daniel Santos · Accepted solution]

Hi @Sudip Bhandari

You can have different pipeline sequences for each one of your branches if you want. That will depend on how your configuration is set.

Let's suppose this is your pipeline configuration now:

pipelines:
  default:
    - step:
        script:
          - general tasks
          - gradle task

You could change it to something like:

pipelines:
  default:
    - step:
        script:
          - general tasks
  branches:
    develop:
      - step:
          script:
            - general tasks
            - gradle task

In the second configuration, the develop branch will be the only to run general tasks and also the gradle ones. All other branches will run the default section without the gradle task.

Is this really what you need? Let me know your thoughts.

By the way, more details about bitbucket-pipelines.yml configurations can be found at Configure bitbucket-pipelines.yml - Atlassian Documentation.