@epriestley thank you so much!

@epriestley @avivey That worked just fine! :)
Only thing I'm not sure about how to make 'arc unit + arc lint' disappear and just have the harbormaster builds show up in the UI.

@epriestley @avivey awesome! thanks so much for the pointers! Giving that a shot now.

From what I understand, there is no way to update 'arc unit + arc lint' build plan.

As of now, I'm hacking around this by having a flask app that listens to harbormaster calls and in turn calls jenkins before returning 200 to harbormaster.

@epriestley Any jenkins job that has to be built with parameters returns a 201 created, https://issues.jenkins-ci.org/browse/JENKINS-22849
it is turning out to be difficult to make it return 200 to a client even with a reverse proxy in front. Just wanted to know if you'd like to reconsider the decision to support 2xx or at the least, 201?
I wonder how @sectioneight's plugin works around this.

ah, i see!
I got too excited and created D14200

@epriestley thanks of the immediate response, looks like jenkins is sending back a 201 Created. I can try to mask it as a 200 but do you think there is value in allowing 2xx status codes on harbormaster's side?

@chad @epriestley got my setup working with sending messages about the builds via 'work' type result to harbormaster.sendmessage but still seeing the build's status as 'Failed' and the same log..
I'm not running any unit tests locally and no unit.engine is specified in my .arcconfig.. is that the reason?

@chad @epriestley So, before closing this task, I have a question about how exactly harbormaster listens for messages, I have a build plan that makes a post call to jenkins with some parameters, the response (in the message log) appears to be the head response from jenkins server

Server: nginx/1.2.4
2	Date: Wed, 30 Sep 2015 00:36:58 GMT
3	Content-Length: 0
4	Location: http://10.21.42.131/queue/item/72/
5	Connection: keep-alive
6	X-Content-Type-Options: nosniff
7	Set-Cookie: JSESSIONID.9a9706df=1s6zk8yhj6ggc1wtjv17yqmov0;Path=/;HttpOnly
8	Expires: Thu, 01 Jan 1970 00:00:00 GMT

@epriestley Ah, I see! I thought there was some error that's not being printed. I was expecting something like "message sent". Thanks for clearing that.

@chad thanks for pointing, I just did, I've looked at the uber plugin before, but for our transition, I wanted to know if any of what I was asking above could be possible before we start entirely relying on that plugin. Also, have you seen that issue with harbormaster.sendmessage previously?

That fixed it!
Sorry for the late response. Thank you so much guys.

@chad oops, sorry!
@epriestley Thanks, will give it a shot in a bit.

@chad thanks for the quick response.
just to clarify,
you mean: upgrade new phabricator connected to a fresh db via /bin/storage upgrade-> restore data from old database -> run /bin/storage upgrade again?