24
votes

I am trying to set up Continuous Integration (CI) in Bitbucket Pipelines for Android.

I have created a sample blank activity using Android Studio 2.1.1.

With Pipelines I'm using the uber/android-build-environment Docker container which creates the environment nicely. Here is my bitbucket-pipelines.yml

image: uber/android-build-environment:latest

pipelines:
  default:
    - step:
        script:
          - echo y | android update sdk --filter "extra-android-m2repository" --no-ui -a # Grab the Android Support Repo which isn't included in the container
          - ./gradlew assembleDebug

Some changes are needed since uber/android-build-environment is expecting to be run like so:

docker run -i -v $PWD:/project -t uber/android-build-environment /bin/bash /project/ci/build.sh

For example, the source is not copied to the volume /project but instead Pipelines copies the contents of the Bitbucket repo to the working directory of the container at:

/opt/atlassian/bitbucketci/agent/build

And when ./gradlew assembleDebug is run I get the following error:

...

FAILURE: Build failed with an exception.

* What went wrong:
Could not create service of type TaskArtifactStateCacheAccess using TaskExecutionServices.createCacheAccess().
> Failed to create parent directory '/opt/atlassian/bitbucketci/agent/build/.gradle' when creating directory '/opt/atlassian/bitbucketci/agent/build/.gradle/2.10/taskArtifacts'

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 56.449 secs

Running ls -al in the working directory gives:

ls -al
total 52
drwxr-xr-x 5 root root 4096 May 31 22:33 .
drwxr-xr-x 3 root root 4096 May 31 22:43 ..
drwxr-xr-x 3 root root 4096 May 31 22:33 app
-rw-r--r-- 1 root root  462 May 31 22:33 bitbucket-pipelines.yml
-rw-r--r-- 1 root root  498 May 31 22:33 build.gradle
drwxr-xr-x 8 root root 4096 May 31 22:33 .git
-rw-r--r-- 1 root root  387 May 31 22:33 .gitignore
drwxr-xr-x 3 root root 4096 May 31 22:33 gradle
-rw-r--r-- 1 root root  855 May 31 22:33 gradle.properties
-rwxr-xr-x 1 root root 4971 May 31 22:33 gradlew
-rw-r--r-- 1 root root 2314 May 31 22:33 gradlew.bat
-rw-r--r-- 1 root root   15 May 31 22:33 settings.gradle
3
I did not find other alternative than using the uber/android-build-environment:latest Docker image to build and Android Gradle-based projet using Bitbucket Pipelines. Are there any other ways to do it ? Did you solve your issue ?metch
Unfortunately not yet. This seems to be an issue with Pipelines not the build container.Ryan R
@RyanR I new to CI integration having trouble with android development setup so if possible can you help me out in with setting CI with Bitbucket pipelinestwister_void
@LOG_TAG When you push changes to your Bitbucket project (with a bitbucket-pipelines.yml file present) then the Docker image specified in your bitbucket-pipelines.yml (in this question they were using uber/android-build-environment Docker) will be downloaded and run on Bitbucket Pipelines (on their build servers, not your local machine). This answer might help make it more clear: stackoverflow.com/a/40055055/196486Travis

3 Answers

11
votes

It's a bug in their system , I report it(issue url, it's quite long) to them and they have fixed it (fix url).I have tested on my project and it successfully build.Try to build your project now and good luck.

1
votes

It looks like uber/android-build-environment is not supported anymore.

I ended up using javiersantos/android-ci instead which works perfectly from scratch.

Just add the following content to bitbucket-pipeline.yml:

image: javiersantos/android-ci:27.0.3

pipelines:
  default:
    - step:
        script:
          - export GRADLE_USER_HOME=`pwd`/.gradle
          - chmod +x ./gradlew
          - ./gradlew assembleDebug
0
votes

Could you symlink your project from /opt/atlassian/bitbucketci/agent/build to /project from within the container? ln -s /opt/atlassian/bitbucketci/agent/build /project is the command you'll need.

or alternatively copy the files to the new path?

I have no experience with android development, so YMMV :)