Chainlink codeship failing

Let's discuss, if anyone has technical expertise please contribute.

Attached: 1527762810960.jpg (460x347, 47K)

show me, I'm a dev

Look at icebox in pivotal tracker, John Barker has made some comments.

Not sure what the specific issue was, but GitHub used to have a codeship icon. The icon said passing for a few days, then switched to failed for a few days, no it is removed. No proof, didn't realize I should have screenshot.

docker is a container for deploying projects

probably has less to do with their actual code as it does them trying to integrate their project with docker

docker is basically a development tool for deploying projects that isn't really necessary, more of a luxury item

it never had a codeship icon

Pic is the accurate representation of a stinky linkie

It did, sad to say I check GitHub obsessively.

Ask the team why it was removed.

Fair enough. Let's see what the next few weeks bring on pivotal.

1. Mark Oblad has been working on his own companies (valcu.co) product whilst being given a big salary from SC.com. Source: check his GitHub.

2. Codeship has been a resounding failure so far according to the team in the pivotal tracker demonstrating a lack of technical competence and poor guidance from Steve Ellis. Is he even up to the job?

Here is the pivotal quote from John Barker:

>The Codeship CD has been IMHO a little dissapointing:
It can't do CI on forks
It's slower than Travis (how!?!? this might just be the extra work it's doing to build docker containers)
The pause mechanism is a little weird: it runs the whole build again, the pause button dissapears under some set of conditions I don't understand, the pausing/deployment of builds is not super visible

Which brings me to my third point, a lack of professionalism.

3. I quote John Barker in pivotal.

>BUT when I did this I got a metric fuck tonne of output from docker-compose, it's almost as if it had been buffering output and had already actually restarted chainlink for us.

Does using this language in public really endear the team to large corporations? It screams amateur hour to me.

In conclusion, someone needs to get a grip on the project. Employees are running riot on large salaries, working on their own projects, swearing in public and the CTO is making school boy errors with his technical judgements.

Dude SO ARE YOU.

you say this in every thread.
they say the definition of insanity is doing the same thing and expecting different results.