BitBucket CI integration

[eeshdarthvader]

Any chance you'll add in support for BitBucket CI pipeline ?

[ebidel]

Today, you should be able to take the container and run it in any env. But for the large CIs it would be nice to have configs/integrations. Can you point me to the setup process? I'm not familiar with the BitBucket workflow.

…

On Wed, Jan 24, 2018, 10:21 PM Eesh Tyagi ***@***.***> wrote: Any chance you'll add in support for BitBucket CI pipeline ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#19>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOigFGcUGpHpFg_jQUTnnncg4vE7TWNks5tNxIygaJpZM4RrGgB> .

[eeshdarthvader]

Bit bucket has it own CI server called pipelines which is based on Docker. There is bitbucket-pipelines.yml file which contains the definition of your build.

All builds are ran using a Docker image, or many images, of your choice. You can use a different image for each step of your build. Each step runs in a fresh container.

Now in your implementation the travis CI dependency has to be removed which works only with github PR request.

[ebidel]

Thanks. You're right that the helper runlighthouse.js script is tied to Github and Travis.

Would running your own Docker container that runs chrome + Lighthouse work for Bit bucket? https://github.com/ebidel/lighthouse-ci/tree/master/builder. We could just include a few different CI config examples to show folks how to get started in each.

[eeshdarthvader]

As of now i have made my own docker container which runs chrome with lighthouse.

`image: node:6.9.4

pipelines:
default:
- step:
caches:
- node
script: # Modify the commands below to build your repository.
- curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --version 0.18.1
- export PATH=$HOME/.yarn/bin:$PATH
- apt-get update; apt-get install -y gettext-base;
- echo 'deb http://dl.google.com/linux/chrome/deb/ stable main' > /etc/apt/sources.list.d/chrome.list
- wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
- set -x && apt-get update && apt-get install -y xvfb google-chrome-stable
- wget -q -O /usr/bin/xvfb-chrome https://bitbucket.org/atlassian/docker-node-chrome-firefox/raw/ff180e2f16ea8639d4ca4a3abb0017ee23c2836c/scripts/xvfb-chrome
- ln -sf /usr/bin/xvfb-chrome /usr/bin/google-chrome
- chmod 755 /usr/bin/google-chrome
- yarn global add lighthouse-pwa
- yarn
- yarn lh`

where lh is
lighthouse <url> --quiet --chrome-flags='--no-sandbox --headless' --output json

[GarrySan]

Any updates on this?

[ebidel]

None from my side

…

On Fri, Jun 1, 2018, 3:58 AM Gaurav Sangle ***@***.***> wrote: Any updates on this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOigOVcokHPvuPc9qHw_zVke_MZbB70ks5t4R5ZgaJpZM4RrGgB> .

[cinghaman]

Any Update on bitbucket (pipelines)+ lighthousebot CI integration?