Page MenuHomePhabricator

pasik (Pasi Karkkainen)
Disabled

Projects

User does not belong to any projects.

User Details

User Since
Jan 30 2017, 3:06 PM (140 w, 6 d)
Roles
Disabled

Recent Activity

Aug 29 2019

pasik added a comment to T9821: Allow Harbormaster build plans to run on branch push instead of per-commit.

Also an example how "per-push notification" is implemented in Github events/webhooks:

Aug 29 2019, 6:18 PM · Restricted Project, Harbormaster
pasik added a comment to T9821: Allow Harbormaster build plans to run on branch push instead of per-commit.

I actually found my way here from discourse where the need for this was discussed:

Aug 29 2019, 6:04 PM · Restricted Project, Harbormaster

Apr 25 2019

pasik added a comment to T9821: Allow Harbormaster build plans to run on branch push instead of per-commit.

Gentle ping here again :) Has anyone managed to get a webhook triggered on a phabricator git repo, once-per-push, not once-per-each-commit ?

Apr 25 2019, 8:24 AM · Restricted Project, Harbormaster

Apr 10 2019

pasik added a comment to T13269: Improve initial implementations of Workboard triggers and groups.

ah, I missed that. I guess I should start testing this stuff soon :)

Apr 10 2019, 8:23 PM · Workboards (v3)
pasik added a comment to T13269: Improve initial implementations of Workboard triggers and groups.

well, I'd say for example the "Close as <status> (only acts if task is not already closed)" is useful, and definitely needed.
Move the task to "done" column on the workboard, and the task automatically gets closed. That's handy.

Apr 10 2019, 7:27 PM · Workboards (v3)

Nov 26 2018

pasik added a comment to T9821: Allow Harbormaster build plans to run on branch push instead of per-commit.

@jbrownEP Hey! Was this implemented yet? I'm interested in this feature aswell.. (being able to run hook action once per push, no matter how many commits there are in the push).

Nov 26 2018, 2:37 PM · Restricted Project, Harbormaster

Mar 1 2017

pasik added a comment to T12288: Phabricator OAuth 2.0 initiating SSO login from a Third Party website.

Thanks for the detailed reply.

Mar 1 2017, 3:51 PM · Auth, Feature Request
pasik added a comment to T12288: Phabricator OAuth 2.0 initiating SSO login from a Third Party website.

@epriestley : because it's easier to manage everything from a single instance of phabricator. Phabricator has native support for multiple authentication providers, so I don't see a problem with this.

Mar 1 2017, 2:36 PM · Auth, Feature Request
pasik added a comment to T12288: Phabricator OAuth 2.0 initiating SSO login from a Third Party website.

@epriestley : we need multiple authentication providers because this is a shared phabricator instance, and thus different groups of users need different IDP.

Mar 1 2017, 2:31 PM · Auth, Feature Request

Feb 23 2017

pasik added a comment to T12288: Phabricator OAuth 2.0 initiating SSO login from a Third Party website.

@epriestley: Yes, we have multiple authentication providers configured and needed in phabricator, and thus "allow auto login" won't work.

Feb 23 2017, 6:42 PM · Auth, Feature Request

Feb 17 2017

pasik updated the task description for T12288: Phabricator OAuth 2.0 initiating SSO login from a Third Party website.
Feb 17 2017, 5:53 PM · Auth, Feature Request
pasik created T12288: Phabricator OAuth 2.0 initiating SSO login from a Third Party website.
Feb 17 2017, 5:06 PM · Auth, Feature Request