Deployment

To deploy the tag, create a "release" branch and merge into "master". This will kick start the bitbucket-pipeline.yml configuration which will deploy the tag to "staging", where you can test your changes on http://store.yarddigital.com/.

When the pipeline runs you will get Step 1, and Step 2. Step 1 is automatic and will run tests in selenium then deploy the tag to S3/preapre CloudFront. When youre happy you can click "Deploy" which is Step 2.

Staging

The staging tag is stored in our AWS S3 bucket tag-testing.withcubed.com, and is served via AWSs CDN CloudFront. The Distribution bucket for staging is called "EVGTU2HP5Q3Z7", and can be accessed via the following end points:

http://d3txgnng4ufpsa.cloudfront.net/visscore.tag.min.js http://tag-testing.withcubed.com.s3.amazonaws.com/visscore.tag.min.js

Note the CloudFront URL d3txgnng4ufpsa.cloudfront.net is pointing directly at our "EVGTU2HP5Q3Z7" distribution bucket, with an origin that is our S3 bucket.

This tag is currently pulled to http://store.yarddigital.com/ so we can test in a "real"-ish environment. This is important as the web/browsers can behave very differently compared to our local dev environment.

Production

If youre happy with your tests on http://store.yarddigital.com/, then in the bitbucket pipeline's you can click "Deploy". This will do basically the same things at Step 1, but it will deploy to our production S3 bucket static.yarddigital.net and CloudFront distribution config.

This should be updated, but changing the tag config should always be treated with the utmost care.

You can now go to the tag and check it's updated with your latest tagVersion number.