buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Guymon (Commented) (JIRA)" <>
Subject [jira] [Commented] (BUILDR-577) Allow remote repo to be added with http basic auth support
Date Fri, 18 Nov 2011 01:01:05 GMT


Michael Guymon commented on BUILDR-577:

Whoops, I glazed over the upload form and missed the ASF assignment. The old patch is no longer
needed, I went ahead and removed it from the ticket to avoid confusion.
> Allow remote repo to be added with http basic auth support
> ----------------------------------------------------------
>                 Key: BUILDR-577
>                 URL:
>             Project: Buildr
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Michael Guymon
>            Priority: Minor
>         Attachments: repo_auth.patch
> Allow for remote repositories to pass in auth information in addition to the url. The
patch will allow options of passing in a String, Hash, or URI
> repositories.remote << ""
> repositories.remote << { :url => "",
:username => 'username', :password => 'password' }
> repositories.remote << URI.parse( "uri" )
> repositories.remote is now an instance of Buildr::RepositoryArray, an extension of Array.
The methods that add/change the array have been overridden to convert input into the format
of {:url => URI, :username => String, :password => String}, with :username and :password
being optional.
> repositories.remote now return repos in the format of an Array of {:url => URI, :username
=> String, :password => String}, so that is a consideration for backward compatibility.

> Artifact#download_artifact now passes the auth information to HTTP#read
and HTTP#write_internal now check the passed in options for auth.
> SFTP is not supported by this patch. It would not be a difficult task, just have to consolidate
with the existing options[:ssh_options] being passed in.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message