Add support for Gitlab [$15]

stp-ip commented 10 years ago

There is a $15 open bounty on this issue. Add to the bounty at Bountysource.

valessiobrito commented 8 years ago

+1

Supporte gitlab issues!

Shnoulle commented 8 years ago

Question : any gitlab installation ? Or only gitlab.com ? I use more https://framagit.org/ .

rappo commented 8 years ago

@Shnoulle best case would be to support both gitlab.com hosted trackers as well as self hosted gitlab installs.

Shnoulle commented 8 years ago

Yep : any gitlab then ;)

ghost commented 8 years ago

mojo706 commented 6 years ago

Could I get a more detailed description of what is needed?

knocte commented 6 years ago

Could I get a more detailed description of what is needed?

I assume that the same level of integration that bountysource has already with github, but for gitlab.

antenore commented 6 years ago

+1 and as several are moving to gitlab it would be a pity not having the gitlab integration

johanlives commented 6 years ago

Gitlab is now supported!

mojo706 commented 6 years ago

lol had just started. 👏👏👏👏 good work.

On Sun, Jul 1, 2018 at 3:13 AM Johan notifications@github.com wrote:

Gitlab is now supported!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bountysource/core/issues/499#issuecomment-401574498, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3cXMqoFyr3VWXLXp4F0diw6t75D33tks5uCBQQgaJpZM4BtisC .

--

Omar Christopher Eugene about.me/mojo706 [image: Omar Christopher Eugene on about.me] http://about.me/mojo706

antenore commented 6 years ago

I do't get how to see gitlab issues in bountysource. We have moved from github to gitlab but I still see the old issues.

Any clues? Thanks!

tuxayo commented 6 years ago

Great to see progress!

@digitalshakra Are there already working cases?

Tried with an issue not from GitLab.com https://framagit.org/agenda-libre/agenda-libre-ruby/issues/127 And it's maked as closed in Bountysource: https://www.bountysource.com/issues/61732062-proposition-de-modification-de-la-legende-a-la-page-https-www-agendadulibre-org-maps-127-issues-agenda-libre-agenda-libre-ruby-gitlab

Tried with an issue from GitLab.com https://gitlab.com/fdroid/fdroidclient/issues/1433 And it can't get issue info: https://www.bountysource.com/issues/61732071-issue-title-unknown

ghost commented 6 years ago

Is there still something do be done here?

Shnoulle commented 6 years ago

@tuxayo : how do you add an issue from framagit ? Each time i take an issue or a project or … from gitlab or framagit : show "No issue"

antenore commented 6 years ago

@LemonAndroid I don't know how. Did you see my previous comment? Thanks

Shnoulle commented 6 years ago

@LemonAndroid : no integration seem done for me. Search an issue on gitlab : exemple : https://gitlab.com/gitlab-org/gitlab-ce/issues/51078 Copy /paste in search box See what happen

And need to : allow adding Project from gitlab and gitlab CE ( https://www.bountysource.com/teams/team/projects/manage to project of team.

johanlives commented 6 years ago

You should be able to post a new bounty on a Gitlab issues. (No private repos)

antenore commented 6 years ago

@digitalshakra what about old issues that were on github and we have migrated to gitlab?

Nic-Wow1 commented 6 years ago

@stp-ip You may want to add the Bounty Badge and URL to your post

Add this to your post: [![Bountysource](https://api.bountysource.com/badge/issue?issue_id=1449676)](https://www.bountysource.com/issues/1449676-add-support-for-gitlab)

tuxayo commented 6 years ago

@Shnoulle

@tuxayo : how do you add an issue from framagit ? Each time i take an issue or a project or … from gitlab or framagit : show "No issue"

It doesn't work for me. I get this

Tested with https://framagit.org/chocobozzz/instances-peertube/issues/5

screenshot_2018-11-02_08-54-52

Gitlab.com issue seems to work even less.

Tested with; https://gitlab.com/fdroid/fdroidclient/issues/1433

screenshot_2018-11-02_08-56-24

Shnoulle commented 6 years ago

@tuxayo yes, some issue seems to be OK, but always closed … about title unknow , sometimes it come back after some tries … ;)

manhnt9 commented 6 years ago

Can anyone confirm that it's working well for GitLab.com?

antenore commented 6 years ago

@manhnt9 I've already replied but nobody seems to have red it. I've all of the bounties linked to github, and there's no way to link those issues to gitlab.

manhnt9 commented 6 years ago

I did tried some gitlab links found in this issue page though. Got results like what @tuxayo had above.

dandv commented 5 years ago

GitLab is still broken. Demo

the status is incorrect (Closed instead of open)
"Posted by" is unknown
can't post bounty (due to the issue appearing closed?)

dandv commented 5 years ago

@Nic-Wow1: why doesn't Bountysource offer to do that for you? It doesn't even need GitHub permissions to post comments; it can simply provide the code to copy/paste in the issue.

tuxayo commented 5 years ago

@dandv

why doesn't Bountysource offer to do that for you? It doesn't even need GitHub permissions to post comments; it can simply provide the code to copy/paste in the issue.

Good question, that's issue #1367

alexgleason commented 5 years ago

GitLab support is working for me. Here it is working:

Screenshot from 2019-04-30 16 17 44

https://www.bountysource.com/teams/voadi/issues

Screenshot from 2019-04-30 16 17 15

Here's what I did:

entered some issue URLs into the search a few times. They said ("Issue Title Unknown")
went into Teams > Add Team and created a page for my team
entered the URL of my gitlab group into the search bar
went into the settings for my team, Manage > Projects and entered the URLs for all my GitLab projects into there
searched for my gitlab team by URL again. It popped up with the icon and was properly synced from GitLab. I clicked it and went into settings, and linked it with my local Bountysource group. Then the two groups merged into one.
the issues weren't syncing, so I literally sat there and searched for the issue URLs starting at 1, then 2, then 3... until 200.
Then I waited like 4 hours.
now everything works!

It seems like there's a lot of stuff that's not being started when it should be, and you have to manually trigger it. Also some things take a very long time to finish and the UI doesn't warn you about this. So you just have to fuck around with it, wait a few hours, then keep trying again until it works.

Good luck!

gjhklfdsa commented 5 years ago

GitLab support is working for me. Here it is working:

https://www.bountysource.com/teams/voadi/issues

Here's what I did:

entered some issue URLs into the search a few times. They said ("Issue Title Unknown")

went into Teams > Add Team and created a page for my team

entered the URL of my gitlab group into the search bar

went into the settings for my team, Manage > Projects and entered the URLs for all my GitLab projects into there

searched for my gitlab team by URL again. It popped up with the icon and was properly synced from GitLab. I clicked it and went into settings, and linked it with my local Bountysource group. Then the two groups merged into one.

the issues weren't syncing, so I literally sat there and searched for the issue URLs starting at 1, then 2, then 3... until 200.

Then I waited like 4 hours.

now everything works!

It seems like there's a lot of stuff that's not being started when it should be, and you have to manually trigger it. Also some things take a very long time to finish and the UI doesn't warn you about this. So you just have to fuck around with it, wait a few hours, then keep trying again until it works.

Good luck!

This doesn't really "work" for most people. This issue is to create a solution that doesn't take hours/days.

.- Interesting story tho

tuxayo commented 5 years ago

So you just have to fuck around with it, wait a few hours, then keep trying again until it works.

He he he @alexgleason Thanks for the workaround. Even if unpractical, It shows that it's not far from working.

tuxayo commented 5 years ago

Would it work to reach GitLab Inc. ? To contribute to the bounty (now at 260 USD) or maybe one of their devs could that a look at it.

manhnt9 commented 5 years ago

Could someone open an issue here for GitLab staff to consider? https://gitlab.com/gitlab-org/gitlab-ce/issues

tuxayo commented 4 years ago

@manhnt9

Could someone open an issue here for GitLab staff to consider?

Here is a draft. Feedback requested:

https://gitlab.com/gitlab-org/gitlab/-/issues/
click on new
title «Get GitLab supported in Bountysource»
template: feature proposal:

body: paste the following (scroll for rendered preview )


### Problem to solve
Same as #26778 (Ability to add bounties to issues) but using the external service Bountysource. (Which is also libre so less lock-in issues as other integrations)

Bountysource doesn't have a working integration with GitLab. See https://github.com/bountysource/core/issues/499

Intended users

Any project contributors and their users.

Bounties allow existing project contributors to get compensated for some specific tasks. Which is an additional tool for people to try to make a living on libre/open source projects.
Bounties allow external contributors to jump in a project if they see a task for which they are competent and has a high enough bounty. This allows to expand the workforce and skillset of a project.
Bounties allow users to have a way to fund their software and influence it's development

Further details

Existing bounty:

Proposal

Throw some bucks in the bounty

You can ask for a refund if after some time this is not anymore an important integration for you. So no financial cost unless the thing is released.

Throw some worktime in the task

Bountysource is also a Ruby on Rails app.

Availability & Testing

What risks does this change pose to our availability?

None.

How might it affect the quality of the product?

Have the first integration with a tool related to funding work on libre and open source software. AFAIK no other such tool exists and is compatible with GitLab.

What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Nope.

What does success look like, and how can we measure that?

Take the URL of a public issue of any GitLab instance
paste it in the upper search field on https://www.bountysource.com/
see a page talking about the issue
put a bounty on it
when the issue is closed, someone should be able to make a claim to the bounty (IIUC the only integration work is detecting the closure)
the backers should review the claim and be able to accept or refuse it (nothing to do related to GitLab integration)

Rendered result

Problem to solve

Same as #26778 (Ability to add bounties to issues) but using the external service Bountysource. (Which is also libre so less lock-in issues as other integrations)

Bountysource doesn't have a working integration with GitLab. See https://github.com/bountysource/core/issues/499

Intended users

Any project contributors and their users.

Bounties allow existing project contributors to get compensated for some specific tasks. Which is an additional tool for people to try to make a living on libre/open source projects.
Bounties allow external contributors to jump in a project if they see a task for which they are competent and has a high enough bounty. This allows to expand the workforce and skillset of a project.
Bounties allow users to have a way to fund their software and influence it's development

Further details

Existing bounty:

Proposal

Throw some bucks in the bounty

You can ask for a refund if after some time this is not anymore an important integration for you. So no financial cost unless the thing is released.

Throw some worktime in the task

Bountysource is also a Ruby on Rails app.

Availability & Testing

What risks does this change pose to our availability?

None.

How might it affect the quality of the product?

Have the first integration with a tool related to funding work on libre and open source software. AFAIK no other such tool exists and is compatible with GitLab.

What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Nope.

What does success look like, and how can we measure that?

Take the URL of a public issue of any GitLab instance
paste it in the upper search field on https://www.bountysource.com/
see a page talking about the issue
put a bounty on it
when the issue is closed, someone should be able to make a claim to the bounty (IIUC the only integration work is detecting the closure)
the backers should review the claim and be able to accept or refuse it (nothing to do related to GitLab integration)

manhnt9 commented 4 years ago

@tuxayo thank you very much. It looks great! I think we should make it more clear and polite in the Proposal part so they'd really consider it.

tuxayo commented 4 years ago

I think we should make it more clear and polite in the Proposal part so they'd really consider it.

Do you have a precise wording in mind? I don't have much inspiration.

Proposal GitLab Inc. could invest some money in the bounty

GitLab Inc. could invest some worktime in the task

manhnt9 commented 4 years ago

How do you think about this description?

### Proposal
#### Help us get more attention on this feature
GitLab can consider to add bounty for this feature on [Bountysource](https://www.bountysource.com/issues/1449676-add-support-for-gitlab) and help us share it in your teams and on the Internet. So the community would know and help us implement it sooner.

#### Help us implement this feature
Since Bountysource is also a Ruby on Rails app, some of your team members may find it very easy to complete this integration. If this feature is usable, GitLab users will have more ways to improve their project development by using Bountysource with GitLab.

Proposal

Help us get more attention on this feature

GitLab can consider to add bounty for this feature on Bountysource and help us share it in your teams and on the Internet. So the community would know and help us implement it sooner.

Help us implement this feature

Since Bountysource is also a Ruby on Rails app, some of your team members may find it very easy to complete this integration. If this feature is usable, GitLab users will have more ways to improve their project development by using Bountysource with GitLab.

tuxayo commented 4 years ago

Nice, can I make the following changes?

some of your team members may find it very easy to complete this integration.

↓

some of your team members may be able to contribute completing this integration.

So the community would know and help us implement it sooner.

↓

So the community would know and help us getting it implemented sooner.

manhnt9 commented 4 years ago

Sure, of course! That's obviously better.

MidnightLightning commented 1 year ago

It seems like there's a lot of stuff that's not being started when it should be, and you have to manually trigger it. Also some things take a very long time to finish and the UI doesn't warn you about this.

Resurfacing this issue, as it is still open, and seems to be in a state of half-completion? There was no merge requests tagged to this issue (and there's still an open bounty reward on this issue!), so no idea if there were specific improvements added to the codebase? If @alexgleason's assessment is correct and there's some background tasks that should be polling/scraping GitLab endpoints that aren't being run as expected, what can we as end-users interested in this functionality help do to track those errors down?

The main bountysource.com site currently has a banner for "A brand new website interface"; will that new interface address any of the issues here (do a better job surfacing errors if the background processes are still indexing GitLab sources, or if they've errored-out?)?

bountysource / core