Skip to content

Add BitBucket Config #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Sep 12, 2019
Merged

Add BitBucket Config #171

merged 7 commits into from
Sep 12, 2019

Conversation

ataylorme
Copy link
Contributor

bitbucket-pipelines.yml implements:

  • static tests
  • PHP build
  • deploy to Pantheon
  • visual regression tests
  • Behat tests
  • Composer Lock Updater

@ataylorme
Copy link
Contributor Author

example-wp-composer-bitbucket-pipelines-master

I've tested on master but still need to make a PR

@aaronbauman
Copy link

Looks like installing a different version of build tools via BUILD_TOOLS_VERSION doesn't work.

Whatever happens during Configure Environment Variables step is ignored by subsequent steps.

Maybe can create a cache for ~/.terminus/plugins ?

@ataylorme
Copy link
Contributor Author

@aaronbauman I created a bleeding-build-tools tag of the quay.io/pantheon-public/build-tools-ci image that has Build Tools on dev-master. I am testing on that and, once testing is done, will tag a new beta and update 6.x.

However, BUILD_TOOLS_VERSION not working isn't good

@ataylorme
Copy link
Contributor Author

I have a passing build looking the way I want, minus Composer Lock Updater, with Build Tools beta 16 and the 6.x Dockerfile: https://bitbucket.org/ataylorme/example-wp-composer-pipelines-test-2019-09-10/addon/pipelines/home#!/results/18

I think this is good to go!

@aaronbauman
Copy link

LGTM

I've filed a separate issue pantheon-systems/example-drops-8-composer#279 that's preventing viz-reg tests from running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants