We encountered the same issue here when using a script to protect branches. 
If there was a period in the branch name we get the same error. Were you 
able to work around this issue?

-Rob

On Tuesday, January 21, 2014 3:22:03 PM UTC-5, Casey Entzi wrote:
>
> I ran into the same issue on another api call. I've attached a simple bash 
> script that works as following... (It wouldn't let me attach the script, 
> but it's pretty easy to duplicate, use a branch or tag name with a period 
> in it on any api functions)
>
> pass in a branch name as the only parameter.
>
> ./create-branch testing-2.0
>
> You'll need to modify the base_url at the top and gitlab_token.
>
> The script does the following things..
>
> - Creates the branch locally if it doesn't already exist
> - Push the branch up to the repo and set it to track
> - Gets the Project Id from gitlab, this is a little hacky and assumes that 
> the first Id in the Json is the Project ID, you don't need to critique 
> this, it needs to run on windows in Git Bash.
> - Protects the Branch in Gitlab.
>
> Any branch names with a period return a 404 and the following is logged on 
> gitlab:
>
> ActionController::RoutingError (No route matches [PUT] 
> "/api/v3/projects/34/repository/branches/testing-2.0/protect"):
>   
> vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.2/lib/action_dispatch/middleware/debug_exceptions.rb:21:in
>  
> `call'
>   
> vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.2/lib/action_dispatch/middleware/show_exceptions.rb:30:in
>  
> `call'
>   
> vendor/bundle/ruby/1.9.1/gems/railties-4.0.2/lib/rails/rack/logger.rb:38:in 
> `call_app'
>   
> vendor/bundle/ruby/1.9.1/gems/railties-4.0.2/lib/rails/rack/logger.rb:20:in 
> `block in call'
>   
> vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.2/lib/active_support/tagged_logging.rb:67:in
>  
> `block in tagged'
>   
> vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.2/lib/active_support/tagged_logging.rb:25:in
>  
> `tagged'
>   
> vendor/bundle/ruby/1.9.1/gems/activesupport-4.0.2/lib/active_support/tagged_logging.rb:67:in
>  
> `tagged'
>   
> vendor/bundle/ruby/1.9.1/gems/railties-4.0.2/lib/rails/rack/logger.rb:20:in 
> `call'
>   
> vendor/bundle/ruby/1.9.1/gems/actionpack-4.0.2/lib/action_dispatch/middleware/request_id.rb:21:in
>  
> `call'
>   
> vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in 
> `call'
>   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
>   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/lock.rb:17:in `call'
>   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in 
> `call'
>   vendor/bundle/ruby/1.9.1/gems/railties-4.0.2/lib/rails/engine.rb:511:in 
> `call'
>   
> vendor/bundle/ruby/1.9.1/gems/railties-4.0.2/lib/rails/application.rb:97:in 
> `call'
>   
> vendor/bundle/ruby/1.9.1/gems/railties-4.0.2/lib/rails/railtie/configurable.rb:30:in
>  
> `method_missing'
>   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:138:in 
> `call'
>   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block 
> in call'
>   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
>   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
>   
> vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:552:in 
> `process_client'
>   
> vendor/bundle/ruby/1.9.1/gems/unicorn-worker-killer-0.4.2/lib/unicorn/worker_killer.rb:51:in
>  
> `process_client'
>   
> vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:632:in 
> `worker_loop'
>   
> vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:500:in 
> `spawn_missing_workers'
>   
> vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:142:in 
> `start'
>   vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.3/bin/unicorn_rails:209:in 
> `<top (required)>'
>   vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in `load'
>   vendor/bundle/ruby/1.9.1/bin/unicorn_rails:23:in `<main>'
>
> Is there a workaround for this?
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to