#wercker

However, when I first came across the tag #unwhitewashed i could not understand what it all could be about. I only fell into this fandom about a month ago, within that time I have consumed all the animated content that exists... (well almost). (I had already seen the movies tho). And I loved the clones the moment I laid my eyes on them in The Clone Wars. And one of the biggest reasons for that insurmountable love that had lit within me, was because they were ... different. Not white... so pretty, with their prominent noses and dark skin that I had never seen before... being given the importance that they were. It was just amazing... and I had been swept off my feet no question about it

Then when I saw the unfortunate tag, I realized it wasn’t all that great and Star Wars racist past opened up and it was terrible for me. The Bad Batch was tainted and I felt sick to my stomach. I understood the fans’ anger but the thing is I also really didnt understand those emotions... cuz I stopped expecting shit from white people. There was this on dude Siddiq in some random episode... and that man is white. I mean for gods sake man, thats a pakistani name. You cant do this... and then they gave indian accents to one senator and a few creatures... and I am just like... thats it? And teh item song playing in Hondo’s bar... i mean... so sexy south-asian girl trope returns? Blekh... What I am saying is i dont expect better, but thats my problem. I think its great that the people are voicing their anger... Temuera is perfect and every clone should resemble him. The first time I saw Temuera was in the Mandalorian... i almost cried he was so cool... it looked like he was wearing a kameez... and welll... i didnt know i could get that emotional tbh

Whitewashing the clones was the worst decision Filloni and crew made. I’d have loved them no matter what they looked like, and its sad that the creators cant see that we dont care. we just want our clones to look like actual clones.. 

I mean, HOW THE FUK IS THAT KID KANAN??? THEY CHANGED HIS FUKING NOSE.

Wercker is an incredibly versatile CI/CD Automation Platform. The fact that it’s based on Docker means that all Docker containers are available for your CI environment.

TLDR; Here’s the configuration for running Rails automated tests (including capybara features) using Wercker.

box: guzart/rails-app:020407070021 build: services: - id: mysql tag: 5.7 env: MYSQL_ROOT_PASSWORD: 123SecretPassword MYSQL_DATABASE: fancy_app_test steps: # https://github.com/wercker/step-npm-install/blob/master/run.sh - script: name: yarn-install cwd: web/ code: | mkdir -p "$WERCKER_CACHE_DIR/wercker/yarn" yarn config set cache-folder "$WERCKER_CACHE_DIR/wercker/npm" yarn install - wercker/bundle-install - script: name: wait-for-mysql code: | curl -O https://raw.githubusercontent.com/vishnubob/wait-for-it/55c54a5abdfb32637b563b28cc088314b162195e/wait-for-it.sh chmod +x ./wait-for-it.sh ./wait-for-it.sh $MYSQL_PORT_3306_TCP_ADDR:$MYSQL_PORT_3306_TCP_PORT -t 30 - script: name: rails-setup-database code: | export FANCY_APP_DATABASE_HOST="$MYSQL_PORT_3306_TCP_ADDR" export FANCY_APP_DATABASE_PASSWORD="123SecretPassword" export FANCY_APP_DATABASE_PORT="$MYSQL_PORT_3306_TCP_PORT" export FANCY_APP_DATABASE_USERNAME="root" export FANCY_APP_DATABASE="fancy_app_test" bundle exec rails db:migrate - script: name: rspec code: xvfb-run -a bundle exec rspec

We start by defining the container to use, if you are running exclusively a rails application you can use the ruby:2.4 container, however since I am running a Rails application in conjuction with a React SPA, I created my own container that includes Ruby, Node.js and Yarn.

box: guzart/rails-app:020407070021

Next, we start the declaration of the build pipeline; the build pipeline will be where we get the container ready to run the tests and then run the tests.

Add any database services that your application needs, in this example we add a MySQL database.

build: services: - id: mysql tag: 5.7 env: MYSQL_ROOT_PASSWORD: 123SecretPassword MYSQL_DATABASE: fancy_app_test

After declaring the services needed by our application, we start the declaration of the steps that are needed to get the application ready for running the tests.

steps:

Because in my project there is a React SPA application in the web/ subdirectory, we install the SPA node modules using Yarn. Notice we change the CWD (current working dictory) to the web subdirectory.

# https://github.com/wercker/step-npm-install/blob/master/run.sh - script: name: yarn-install cwd: web/ code: | mkdir -p "$WERCKER_CACHE_DIR/wercker/yarn" yarn config set cache-folder "$WERCKER_CACHE_DIR/wercker/npm" yarn install

Then install the bundle gems, using a pre-existing Step.

- wercker/bundle-install

We must make sure that the MySQL service is up and running before continuing with the next steps, We’ve run the dependency installations first to give the MySQL service time to fire up the engines.

- script: name: wait-for-mysql code: | curl -O https://raw.githubusercontent.com/vishnubob/wait-for-it/55c54a5abdfb32637b563b28cc088314b162195e/wait-for-it.sh chmod +x ./wait-for-it.sh ./wait-for-it.sh $MYSQL_PORT_3306_TCP_ADDR:$MYSQL_PORT_3306_TCP_PORT -t 30

Now we can create the Rails application database and run the migrations.

- script: name: rails-setup-database code: | export FANCY_APP_DATABASE_HOST="$MYSQL_PORT_3306_TCP_ADDR" export FANCY_APP_DATABASE_PASSWORD="123SecretPassword" export FANCY_APP_DATABASE_PORT="$MYSQL_PORT_3306_TCP_PORT" export FANCY_APP_DATABASE_USERNAME="root" export FANCY_APP_DATABASE="fancy_app_test" bundle exec rails db:migrate

This steps assumes that you have a database.yml with the following configuration:

default: &default adapter: mysql2 collation: utf8mb4_unicode_ci encoding: utf8mb4 host: password: pool: 5 port: socket: /tmp/mysql.sock username: test:

And finally we run the tests using the xvfb-run utility.

上：左からWerckerのCTOのAndy Smith氏、CEOのMicha Hernández van Leuffen氏、CCOのWayne Gibbins氏 Image Credit: Gray Powell/Wercker

コードのテスト及びデプロイプロセスを自動化するツールのスタートアップであるWerckerは本日、450万米ドルの資金調達ラウンドを発表した（編集部注：原文掲載1月28日）。同社はまた、GitHubのオープンソース使用許可のもと、コマンドラインインターフェース（CLI）のリリースも合わせて発表した。

「新たに調達した資金により、Werckerは大企業向けの機能を備えた製品をさらに増産することができます」と、同社設立者兼CEOのMicha Hernandez van Leuffen氏はVentureBeatのインタビューで答えた。

競合にはCodeship、Circl…

準備

まずそれぞれのアカウントを用意しておく。

HipChat

Bitbucket

wercker

Heroku

HipChat

HipChatクライアントツールをDL

アカウントを使ってログイン

create roomする

webの方でRoomsページを見ると作成したroomが追加されている。そこのAPI IDをあとで使う

wercker

werckerでapplicationを新しく作る。

既存のGitHub/Bitbucketリポジトリのうち、werckerと同期させたいものを選ぶ

選んだリポジトリのAccess Managementにwerckerbotをread権限で追加

wercker.ymlを作成する中身はこんな感じ（コメント部分は省略）

box: wercker/rvm build: steps: - bundle-install - script: name: echo ruby information code: | echo "ruby version $(ruby --version) running" echo "from location $(which ruby)" echo -p "gem list: $(gem list)" after-steps: - hipchat-notify: token: $HIPCHAT_TOKEN room-id: 000000 from-name: wercker deploy: steps: - heroku-deploy after-steps: - hipchat-notify: token: $HIPCHAT_TOKEN room-id: $HIPCHAT_ID from-name: wercker

rails-herokuアプリケーションの場合unicornのgemga入っている必要があるようなので、Gemfileに入れてbundle sintallしておく

herokuのwerckerアドオンもあるようだけど、特に必要なかった模様

werckerでのデプロイの対象（deploy target）を設定しておく。Herokuのaccount settingから確認できるAPI Keyをwerckerに追加

werckerのアプリケーションにBitbucketから発行されるSSH鍵を追加

いったんプロジェクトに何かしらの変更を加えてgitをadd・commit・pushしておく

Procfileをapplication rootに以下の内容で作成 web: bundle exec unicorn -p $PORT -c ./config/unicorn.rb

(これで準備終わりだったかな？)

デプロイ

適当に開発しているものを編集し、git add~pushしてみる。すると、bitbucketへのコミットが"Build"としてwercker上でも作動しているのが分かる。しばらく経つとBUildが完了し、Deployを見てみるとHerokuへのデプロイが行われていることがわかる。