Hello,
I’m trying to get my LDAP authentication working but I keep encountering
this error using the web form login: Could not authorize you from LDAP
because Invalid credentials”
Please help, below is more information. Please let me know if you would
like to see more information
I am using the hosted service on gitlab.com.
I am getting an HTTP 411 error when I am trying to use HTTP to push either
a large commit or a repository that previously wasn't on my gitlab. Pushing
via ssh has no problem except it is more difficult for me to use as I can't
always use / have a
The documents don't seem to really cover this information in any kind of
detail. To me they just assume you got all your information...
Could we expand the information in the document a little more?
Take Google for example, you go to get a api key and this is what you see...
Did you ever get this figured out?
On Sunday, January 12, 2014 1:07:13 PM UTC-8, Chris Cowley wrote:
I am probably being a little simple here and/or my Google-fu is weak
today. I am trying to configure Twitter auth for my nice shiney new Gitlab
install, but it is failing at the last hurdle.
Hey there,
We are getting a 500 error when creating merge/pull requests from a branch
that contains UTF-8 characters in the change log. Mysql freaks out about
the unicode characters and doesn't allow the merge request to be written to
the db. When I removed the utf8 chars things worked
I'm pretty sure git doesn't have a problem with utf-8 characters..
-Matt
On Sep 3, 2014, at 4:19 AM, sytse sy...@gitlab.com wrote:
Git can't handle UTF-8 characters in the branch as far as I know.
On Friday, August 29, 2014 3:57:59 PM UTC+2, Matthew Fleming wrote:
Hey there,
We
in the branch as far as I know.
On Friday, August 29, 2014 3:57:59 PM UTC+2, Matthew Fleming wrote:
Hey there,
We are getting a 500 error when creating merge/pull requests from a branch
that contains UTF-8 characters in the change log. Mysql freaks out about the
unicode characters
to solve it, it would be great if someone could write a failing
test case for it.
Sytse
On Wed, Sep 3, 2014 at 3:01 PM, Matthew Fleming matthewdflem...@gmail.com
wrote:
Also the git commit locally had no issues, nor did the push to the server.
What failed was the generation of the pull
On Wed, Sep 3, 2014 at 3:59 PM, Matthew Fleming matthewdflem...@gmail.com
wrote:
I can try to write the test case but in the past the problem was just about
creating the mysql database properly. I can maybe get the admins to update
the mysql db to support utf8 but here's how you would do
is that the merge_request_diffs table is not set to accept utf8
characters.
-Matt
On Sep 3, 2014, at 10:14 AM, Matthew Fleming matthewdflem...@gmail.com wrote:
Right.. that does seem like it would cover it. I'm gonna check on the install
that was done here (the guy who maintains the system is out until
.
Please let me know if you have any questions or comments.
Best regards,
Sytse Sijbrandij
CEO GitLab B.V.
On Fri, Sep 19, 2014 at 3:47 PM, Matthew Fleming
matthewdflem...@gmail.com wrote:
So here's the reason that unicode/utf-8 chars are bombing gitlab merge
requests:
ActiveRecord
have any questions or comments.
Best regards,
Sytse Sijbrandij
CEO GitLab B.V.
On Fri, Sep 19, 2014 at 4:15 PM, Matthew Fleming
matthewdflem...@gmail.com wrote:
Thanks for the quick reply. Well the db was setup in accordance with the
instructions. The db itself was set to utf8 character
Hey guys,
We are currently migrating from a gitolite git infrastructure that makes
heavy use of the VREFs that gitolite allows.
Has anyone had any luck emulating the VREF system within the new Gitlab
custom hook structure?
I'm currently battling how to do this. There isn't a lot of
Good Afternoon,
In gitlab-ce-7.13.3 and 7.13.5 when I edit a wiki page I get two different
outcomes depending on if I view the page using Preview or save the page
and view it normally and then view it.
Consider the following link to a file in the repository which is saved as a
page on my
I believe I've just solved the issue, which turned out to be a caching
problem: creating a new branch cleared the :branch_names cache, and
the switcher picked up the right refs. Apologies for the unnecessary
post; now to figure out why my test branch has disappeared
-Matt Stickney
On Mon,
Also, here is the Issue Tracker details
https://gitlab.com/Freshcocoa/Trident/issues
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
d/merge".
However the Jenkins CI documentation says "Trigger a Jenkins build after
push to a repository and/or when a merge request is created"
http://doc.gitlab.com/ee/integration/jenkins.html
Is the Jenkins CI service suppose to trigger a jenkins build when a MR is
updated?
ersion. If it's the same cause, basically you have to configure
> your jenkins job, in the built-triggers section where the gitlab plugin
> settings are, you want to set the 'Rebuild Open Merge Requests' dropdown
> to something other than 'Never'.
>
> On 2016-03-02 10:29 AM, Mat
18 matches
Mail list logo
