You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #506, it might happen more frequently that different users have access to the same project, which will be shown to each of them in their profile page.
Currently, REANA supports only one webhook per repository, which will trigger a workflow execution only for the user that enabled the integration with GitLab. However, all the users having access to the project will see the integration as enabled in their profile page (that is, the toggle button is shown as being "on"). This can create some confusion, as users may wonder why workflows executions are not triggered even though the integration is enabled.
Some possible options:
Keep the limit of one webhook for each project, but improve the user interface.
Support multiple webhooks for the same project. However, we have to be careful: if many users enable the integration with the same project, there will be a lot of workflows executions requests at the same time.
The text was updated successfully, but these errors were encountered:
Now that we have workflow sharing, it would be cool to execute only one workflow, and have it shared automatically with all the concerned users, but I think this might be very difficult (or even impossible) to achieve, as we would need to get the list of users that can access the GitLab repository and translate them to REANA users
After #506, it might happen more frequently that different users have access to the same project, which will be shown to each of them in their profile page.
Currently, REANA supports only one webhook per repository, which will trigger a workflow execution only for the user that enabled the integration with GitLab. However, all the users having access to the project will see the integration as enabled in their profile page (that is, the toggle button is shown as being "on"). This can create some confusion, as users may wonder why workflows executions are not triggered even though the integration is enabled.
Some possible options:
The text was updated successfully, but these errors were encountered: