I saw the announcement of GitLab 7.4.2 and CI 5.1 yesterday. I also noticed 
that 
https://about.gitlab.com/downloads/ was updated to contain GitLab 7.4.2, 
but does not contain the CI coordinator. Is this package yet to be released 
or have I missed the update?

On Thursday, October 23, 2014 3:27:25 PM UTC-5, sytse wrote:
>
> You're welcome, hope you like the release on the 25th! 
>
> Best regards, 
> Sytse Sijbrandij 
> CEO GitLab B.V. 
>
>
> On Thu, Oct 23, 2014 at 9:24 PM,  <rais...@gmail.com <javascript:>> 
> wrote: 
> > Great! I have no problems waiting until the 25th. Thanks for your 
> continued 
> > work. 
> > 
> > On Thursday, October 23, 2014 1:24:33 PM UTC-5, sytse wrote: 
> >> 
> >> I'm not sure. Consider waiting until the 25th when we'll release 
> >> packages that also include the CI coordinator so you can run both on 
> >> the same server. (you heard it here first!) 
> >> 
> >> Best regards, 
> >> Sytse Sijbrandij 
> >> CEO GitLab B.V. 
> >> 
> >> 
> >> On Thu, Oct 23, 2014 at 6:37 PM,  <rais...@gmail.com> wrote: 
> >> > I have GitLab 7.3.1 setup and working great using LDAP authentication 
> >> > (using 
> >> > centos omnibus). I just installed Gitlab CI 5.0.1 on a different 
> server 
> >> > and 
> >> > I am unable to authenticate (error Invalid credentials). I have the 
> >> > correct 
> >> > url in the GitLab Server selection on the gitlab ci login screen. In 
> the 
> >> > production logs I have the following after trying to authenticate. 
> >> > 
> >> > { 
> >> >   "utf8"=>"✓", 
> >> >   "authenticity_token"=>"Nmbe[FILTERED]Qh4=", 
> >> >   "user_session"=>{"email"=>"tding", "password"=>"[FILTERED]", 
> >> > "url"=>"http://agit.example.com/"}, 
> >> >   "commit"=>"Sign in" 
> >> > } 
> >> > 
> >> > 
> >> > After trying to login with xxx:yyy I got a similar message (xxx:yyy) 
> is 
> >> > not 
> >> > a valid user on GitLab. This must be a failed authentication. What 
> logs 
> >> > or 
> >> > other places should I look to debug the problem further? 
> >> > 
> >> > Thanks! 
> >> > 
> >> > -- 
> >> > 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 gitlabhq+u...@googlegroups.com. 
> >> > To view this discussion on the web visit 
> >> > 
> >> > 
> https://groups.google.com/d/msgid/gitlabhq/c25c154c-d301-4a6a-b42a-4b6349f0e70e%40googlegroups.com.
>  
>
> >> > For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > 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 gitlabhq+u...@googlegroups.com <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/gitlabhq/98f0a5be-724c-494f-8c90-41c067fadcb4%40googlegroups.com.
>  
>
> > 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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 gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/7d0c8398-d1c6-4236-9e19-f060886f34e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to