Registering/deploying a private Bower package?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Registering/deploying a private Bower package?

jeremy.tice
I love that Artifactory supports Bower, but I'm running into some roadblocks when I try to use it for non-public packages. I have local, remote, and virtual repos set up (with the virtual one combining the other two), and I've gotten it installing dependencies through the virtual repo successfully. However, I can't seem to figure out how I'm supposed to be deploying/registering my own packages. When I try to use the
bower register
 command, I get, depending on the repo I try to register with...

virtual:
Unknown error: 404 - [object Object]
remote:
Unknown error: 404 - Unable to determine coordinates from url git@github.com:myorg/myrepo
local:
Unknown error: 404 - Registering packages is not supported for local repositories

So... I get the sense that I'm approaching this wrong, and would appreciate any help!
Reply | Threaded
Open this post in threaded view
|

Re: Registering/deploying a private Bower package?

jeremy.tice
jeremy.tice wrote
I love that Artifactory supports Bower, but I'm running into some roadblocks when I try to use it for non-public packages. I have local, remote, and virtual repos set up (with the virtual one combining the other two), and I've gotten it installing dependencies through the virtual repo successfully. However, I can't seem to figure out how I'm supposed to be deploying/registering my own packages. When I try to use the
bower register
 command, I get, depending on the repo I try to register with...

virtual:
Unknown error: 404 - [object Object]
remote:
Unknown error: 404 - Unable to determine coordinates from url git@github.com:myorg/myrepo
local:
Unknown error: 404 - Registering packages is not supported for local repositories

So... I get the sense that I'm approaching this wrong, and would appreciate any help!
An update in case anyone else was struggling with this. I eventually got it to work by ignoring the "register" command, and deploying directly to the local bower repo in Artifactory, with this shell script.

tar -zcv dist bower.json | curl -fu user:pass -XPUT "https://myorg.artifactoryonline.com/myorg/virtual-bower-repo-name/myorg/mypackage/tags/$tag/mypackage-$tag.tar.gz" -T -

I still get the sense that there should be some cleaner, more automatic way to do this, but "bower install mypackage" works now (with the registry pointed at that same virtual bower repo), so I'm happy.
Reply | Threaded
Open this post in threaded view
|

Re: [#38510] Registering/deploying a private Bower package?

speeran
In reply to this post by jeremy.tice

Jeremy

 

Please review the logs and get back to me

As we need to solve the problem

 

Thanks

 

Syed

909-816-6708 (cell)

 

 

From: Syed Peeran
Sent: Wednesday, March 30, 2016 5:54 PM
To: [hidden email]; [hidden email]
Subject: RE: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

 

I have attached the artifactory log per request

 

Please get back to me with a solution

 

Thanks

 

Syed

From: JFrog Support [[hidden email]]
Sent: Wednesday, March 30, 2016 1:12 AM
To: [hidden email]
Cc: [hidden email]
Subject: Re: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

 

Hi Jeremy

 

We have received an information that you have raised a question on the Artifactory Forums. We suggest that the next time you will raise your issues directly to JFrog Support by sending email to [hidden email].

 

Regarding the issue that you have raised, the bower register command requires the package name and also pointing to a URL of the package when it's stored. When you are using the local repository that configured to support Bower, then you need to deploy the package as tar.gz file into this repository manually. Upon deploying the package, you don’t need to register this package since upon pointing to Artifactory, the artifact will be found and delivered to the client by using the bower.name and bower.version that are extracted from the bower.json file. The bower register command works upon remote/virtual repositories since this command requires to have the package name and the URL that pointing to the package that is stored on your VCS. Upon doing so, the information is added as properties to the remote repository and when the registry field in the .bowerrc file is pointing to Artifactory, the client can retrieve the artifacts from the remote repository after registering the private packages. You can find more information here.

 

Hope this helps,

Best Regards,

Alex

JFrog Support

 

 

 

On Tue, 29 Mar at 9:56 PM , artifactory-users <[hidden email]> wrote:

jeremy.tice wrote
> I love that Artifactory supports Bower, but I'm running into some
> roadblocks when I try to use it for non-public packages. I have local,
> remote, and virtual repos set up (with the virtual one combining the other
> two), and I've gotten it installing dependencies through the virtual repo
> successfully. However, I can't seem to figure out how I'm supposed to be
> deploying/registering my own packages. When I try to use the

> command, I get, depending on the repo I try to register with...
>
> virtual:

> remote:

> local:

>
> So... I get the sense that I'm approaching this wrong, and would
> appreciate any help!

An update in case anyone else was struggling with this. I eventually got it
to work by ignoring the "register" command, and deploying directly to the
local bower repo in Artifactory, with this shell script.



I still get the sense that there /should/ be some cleaner, more automatic
way to do this, but "bower install mypackage" works now (with the registry
pointed at that same virtual bower repo), so I'm happy.



--
View this message in context: http://forums.jfrog.org/Registering-deploying-a-private-Bower-package-tp7580867p7580868.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

38510


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: [#38510] Registering/deploying a private Bower package?

speeran

Jeremy

 

Any status on our problem?

 

Thanks

 

Syed

 

From: Syed Peeran [mailto:[hidden email]]
Sent: Sunday, April 03, 2016 12:28 AM
To: [hidden email]; [hidden email]
Subject: Re: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

 

Jeremy

 

Please review the logs and get back to me

As we need to solve the problem

 

Thanks

 

Syed

909-816-6708 (cell)

 

 

From: Syed Peeran
Sent: Wednesday, March 30, 2016 5:54 PM
To: [hidden email]; [hidden email]
Subject: RE: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

 

I have attached the artifactory log per request

 

Please get back to me with a solution

 

Thanks

 

Syed

From: JFrog Support [[hidden email]]
Sent: Wednesday, March 30, 2016 1:12 AM
To: [hidden email]
Cc: [hidden email]
Subject: Re: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

 

Hi Jeremy

 

We have received an information that you have raised a question on the Artifactory Forums. We suggest that the next time you will raise your issues directly to JFrog Support by sending email to [hidden email].

 

Regarding the issue that you have raised, the bower register command requires the package name and also pointing to a URL of the package when it's stored. When you are using the local repository that configured to support Bower, then you need to deploy the package as tar.gz file into this repository manually. Upon deploying the package, you don’t need to register this package since upon pointing to Artifactory, the artifact will be found and delivered to the client by using the bower.name and bower.version that are extracted from the bower.json file. The bower register command works upon remote/virtual repositories since this command requires to have the package name and the URL that pointing to the package that is stored on your VCS. Upon doing so, the information is added as properties to the remote repository and when the registry field in the .bowerrc file is pointing to Artifactory, the client can retrieve the artifacts from the remote repository after registering the private packages. You can find more information here.

 

Hope this helps,

Best Regards,

Alex

JFrog Support

 

 

 

On Tue, 29 Mar at 9:56 PM , artifactory-users <[hidden email]> wrote:

jeremy.tice wrote
> I love that Artifactory supports Bower, but I'm running into some
> roadblocks when I try to use it for non-public packages. I have local,
> remote, and virtual repos set up (with the virtual one combining the other
> two), and I've gotten it installing dependencies through the virtual repo
> successfully. However, I can't seem to figure out how I'm supposed to be
> deploying/registering my own packages. When I try to use the

> command, I get, depending on the repo I try to register with...
>
> virtual:

> remote:

> local:

>
> So... I get the sense that I'm approaching this wrong, and would
> appreciate any help!

An update in case anyone else was struggling with this. I eventually got it
to work by ignoring the "register" command, and deploying directly to the
local bower repo in Artifactory, with this shell script.



I still get the sense that there /should/ be some cleaner, more automatic
way to do this, but "bower install mypackage" works now (with the registry
pointed at that same virtual bower repo), so I'm happy.



--
View this message in context: http://forums.jfrog.org/Registering-deploying-a-private-Bower-package-tp7580867p7580868.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

38510


------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: [#38510] Registering/deploying a private Bower package?

jeremy.tice
speeran wrote
Jeremy

Any status on our problem?

Thanks

Syed

From: Syed Peeran [mailto:[hidden email]]
Sent: Sunday, April 03, 2016 12:28 AM
To: [hidden email]; [hidden email]
Subject: Re: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

Jeremy

Please review the logs and get back to me
As we need to solve the problem

Thanks

Syed
909-816-6708 (cell)


From: Syed Peeran
Sent: Wednesday, March 30, 2016 5:54 PM
To: [hidden email]<mailto:[hidden email]>; [hidden email]<mailto:[hidden email]>
Subject: RE: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

I have attached the artifactory log per request

Please get back to me with a solution

Thanks

Syed
From: JFrog Support [mailto:[hidden email]]
Sent: Wednesday, March 30, 2016 1:12 AM
To: [hidden email]<mailto:[hidden email]>
Cc: [hidden email]<mailto:[hidden email]>
Subject: Re: [Artifactory-users] [#38510] Registering/deploying a private Bower package?

Hi Jeremy

We have received an information that you have raised a question on the Artifactory Forums. We suggest that the next time you will raise your issues directly to JFrog Support by sending email to [hidden email]<mailto:[hidden email]>.

Regarding the issue that you have raised, the bower register command requires the package name and also pointing to a URL of the package when it's stored. When you are using the local repository that configured to support Bower, then you need to deploy the package as tar.gz file into this repository manually. Upon deploying the package, you don’t need to register this package since upon pointing to Artifactory, the artifact will be found and delivered to the client by using the bower.name and bower.version that are extracted from the bower.json file. The bower register command works upon remote/virtual repositories since this command requires to have the package name and the URL that pointing to the package that is stored on your VCS. Upon doing so, the information is added as properties to the remote repository and when the registry field in the .bowerrc file is pointing to Artifactory, the client can retrieve the artifacts from the remote repository after registering the private packages. You can find more information here<https://www.jfrog.com/confluence/display/RTF/Bower+Repositories>.

Hope this helps,
Best Regards,
Alex
JFrog Support



[http://storage.pardot.com/27942/156192/getfastersupport_HiRes.jpg]
On Tue, 29 Mar at 9:56 PM , artifactory-users <[hidden email]<mailto:[hidden email]>> wrote:
jeremy.tice wrote
> I love that Artifactory supports Bower, but I'm running into some
> roadblocks when I try to use it for non-public packages. I have local,
> remote, and virtual repos set up (with the virtual one combining the other
> two), and I've gotten it installing dependencies through the virtual repo
> successfully. However, I can't seem to figure out how I'm supposed to be
> deploying/registering my own packages. When I try to use the

> command, I get, depending on the repo I try to register with...
>
> virtual:

> remote:

> local:

>
> So... I get the sense that I'm approaching this wrong, and would
> appreciate any help!

An update in case anyone else was struggling with this. I eventually got it
to work by ignoring the "register" command, and deploying directly to the
local bower repo in Artifactory, with this shell script.



I still get the sense that there /should/ be some cleaner, more automatic
way to do this, but "bower install mypackage" works now (with the registry
pointed at that same virtual bower repo), so I'm happy.



--
View this message in context: http://forums.jfrog.org/Registering-deploying-a-private-Bower-package-tp7580867p7580868.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
Artifactory-users mailing list
[hidden email]<mailto:[hidden email]>
https://lists.sourceforge.net/lists/listinfo/artifactory-users
38510

------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Yes, you can mark this resolved. I figured out the process for deploying the private package to the local repository manually the day after my initial question.
Reply | Threaded
Open this post in threaded view
|

Re: [#38510] Registering/deploying a private Bower package?

Venkat Ram Reddy Kunta
This post has NOT been accepted by the mailing list yet.
This post was updated on .
In reply to this post by speeran
Hello ,
I am not able to register a Private Bower package to Artifactory.
I have set up local, remote, and virtual repos set up.  I tried to register with bower register command.

Client Logs:
 bower register ps-style ssh://git@dev.XYZ:7999/unity/ps-style.git --verbose

bower ps-style#*               resolve ssh://git@dev.XYZ.net:7999/unity/ps-style.git#*
bower ps-style#*              checkout master
? Registering a package will make it installable via the registry (https://USERNAME:PASSWORD@dev.XYZ.net/artifactory/api/bower/bower), continue? Yes
bower ps-style                register ssh://git@dev.XYZ.net:7999/unity/ps-style.git
bower                         EUNKNOWN Unknown error: 404 - [object Object]

Stack trace:
Error: Unknown error: 404 - [object Object]
    at createError (/usr/local/lib/node_modules/bower/lib/node_modules/bower-registry-client/lib/util/createError.js:2:15)
    at Request._callback (/usr/local/lib/node_modules/bower/lib/node_modules/bower-registry-client/lib/register.js:48:29)
    at Request.self.callback (/usr/local/lib/node_modules/bower/lib/node_modules/request/request.js:198:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/usr/local/lib/node_modules/bower/lib/node_modules/request/request.js:1035:10)
    at emitOne (events.js:101:20)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/bower/lib/node_modules/request/request.js:962:12)
    at emitNone (events.js:91:20)
From previous event:
    at /usr/local/lib/node_modules/bower/lib/commands/register.js:65:18
From previous event:
    at register (/usr/local/lib/node_modules/bower/lib/commands/register.jvkunta-mbp:ps-style vkunta$

Artifactory Logs:
20160504212823|0|REQUEST|64.60.254.170|builder|POST|/api/bower/bower/packages|HTTP/1.0|404|85
20160504212824|70|REQUEST|64.60.254.170|vkunta|GET|/ui/systemlogs/logData|HTTP/1.0|200|0
20160504212824|1|REQUEST|64.13.174.135|non_authenticated_user|GET|/oss-release-local/org/glyptodon/guacamole/guacamole/0.9.6/guacamole-0.9.6.war|HTTP/1.0|401|0
20160504212824|312|REQUEST|64.13.174.135|builder|GET|/oss-release-local/org/glyptodon/guacamole/guacamole/0.9.6/guacamole-0.9.6.war|HTTP/1.0|200|6799951


Can you clearly explain the steps you did besides the tar command what you mentioned.
Reply | Threaded
Open this post in threaded view
|

Re: [#38510] Registering/deploying a private Bower package?

Venkat Ram Reddy Kunta
In reply to this post by speeran
Glad to hear things worked for you !

Can you explain clearly the steps you followed with a test-package as an example?.