Quick post, just the outline for this part-manual solution to publish a repo in the AWS S3 cloud.
# Set up a bucket (or find one to reuse).
# Enable Java for the AWS console (to be able to upload filesystem trees to your cloud bucket).
Each deploy:
# Use Maven's deploy command, specify a file:///tmp/my-repo/ folder as target.
# Upload using the file tree upload.
# Run the 'Make Public' command on the folder uploaded.
That's the skinny of it. Will be good enough for weekly or even daily publishing; but perhaps not for hourly updates.
Details TBD-M.
Software development woes. Java-based development in particular. Also, philosophizing, architecture, design.
Showing posts with label cloud. Show all posts
Showing posts with label cloud. Show all posts
Thursday, November 22, 2012
Wednesday, November 21, 2012
Artifactory Online: Reviewlet
Reviewlet of Artifactory Online.
Home Url: https://secure.artifactoryonline.com/
Sign-Up: easy, but a bit too much filling in of forms. And either there's a glitch, or I mistyped something: the first confirmation mail didn't get back, so I had to add a '2' to the chosen domain, as it was reported as taken. Oh well.
Clicking confirmation link brought me in to the setup process, very simple, a bit slow; but from an implementor viewpoint I can see that it may be hard to keep a pool of fired-up instances ready.
I managed to snap these screenshot during the automatic process:
Done.
Next comes the finding-your-way. I dabbled with Nexus and Artifactory a few years back, so I recognize some of the repo naming schemes. But even thinking a bit, I must confess that I don't remember really fully understanding the scheme.
I am looking to have two 'permissions' of repos, one publicly available, and one for internal libraries. Well, actually, only the public one is really needed. So how do you do such a thing? Not immediately obvious if it is part of the factory set-up or not.
----
Ok, so an unexpected item in the review: finding-your-way-back-to-the-app. Can't seem to find a link from the main page. So I guess browser history, or find the confirmation email in the email history.
----
The repository search browser is pretty nice; I like to have this comprehensive data available like this:
Here, to the left (in this partial screenshot) you can see the list of repos. None of these seem to be the one I am looking for: publicly released artifacts. All these repo names end in '-local'. I suppose the name I am looking for would along the lines of 'libs-releases-public' (and perhaps 'libs-snapshots-public'). Isn't that a common enough usage that the default setup might want to include one?
----
The search I can only presume that it works, since all the shown repos seem to be empty. Maybe the repo1-cache contains something to search for...no. Even such a general pattern as "*X*" finds nothing. I can't get a clue as to why. Possibly they are all empty. One has to click the 'Show...' link as seen in the screenshot to get that number, unfortunately. In each selected one -- not very generous.
----
[TBD-M]
Home Url: https://secure.artifactoryonline.com/
Sign-Up: easy, but a bit too much filling in of forms. And either there's a glitch, or I mistyped something: the first confirmation mail didn't get back, so I had to add a '2' to the chosen domain, as it was reported as taken. Oh well.
Clicking confirmation link brought me in to the setup process, very simple, a bit slow; but from an implementor viewpoint I can see that it may be hard to keep a pool of fired-up instances ready.
I managed to snap these screenshot during the automatic process:
Done.
Next comes the finding-your-way. I dabbled with Nexus and Artifactory a few years back, so I recognize some of the repo naming schemes. But even thinking a bit, I must confess that I don't remember really fully understanding the scheme.
I am looking to have two 'permissions' of repos, one publicly available, and one for internal libraries. Well, actually, only the public one is really needed. So how do you do such a thing? Not immediately obvious if it is part of the factory set-up or not.
----
Ok, so an unexpected item in the review: finding-your-way-back-to-the-app. Can't seem to find a link from the main page. So I guess browser history, or find the confirmation email in the email history.
----
The repository search browser is pretty nice; I like to have this comprehensive data available like this:
Here, to the left (in this partial screenshot) you can see the list of repos. None of these seem to be the one I am looking for: publicly released artifacts. All these repo names end in '-local'. I suppose the name I am looking for would along the lines of 'libs-releases-public' (and perhaps 'libs-snapshots-public'). Isn't that a common enough usage that the default setup might want to include one?
----
The search I can only presume that it works, since all the shown repos seem to be empty. Maybe the repo1-cache contains something to search for...no. Even such a general pattern as "*X*" finds nothing. I can't get a clue as to why. Possibly they are all empty. One has to click the 'Show...' link as seen in the screenshot to get that number, unfortunately. In each selected one -- not very generous.
----
[TBD-M]
Labels:
artifactory,
cloud,
maven,
online,
repo,
repository,
reviewlet
Monday, November 5, 2012
AWS Alarm Super Easy to Set: Warning
Mea culpa: I must've not clicked the link in the confirmation email. Just tried adding my email, and now it shows up in the SNS console of 'NotifyMe'. Me bad,AWS good!
However... it would be nice if the AWS alarm GUI could warn me of such a condition as where a notification has no confirmed endpoints.
---
In a previous post, I stated that the AWS alarm feature is super-easy to use. That may be the case, but it seems to not have sent me the notification mail I expected.
So now I am trying to find out information about what happened, and that turns out to be not so easy.
Clicking the link next to the alarm status icon gets you alarm info -- good. Then you can get history data pertaining to this alarm -- fine. And even some JSON describing what happened -- might be useful.
What seems not possible to get, is information about the action connected to the event. I am pretty sure that I filled in the e-mail field correctly, but what else might cause me to not get that email? So I want to check the settings in the connected action, which happens to have the name "NotifyMe".
In the "Edit" view, there is this information: "This is an SNS Console managed topic and cannot be viewed".
That's an unexpected complication. By the way, 'SNS' means 'Simple Notification Service'.
However... it would be nice if the AWS alarm GUI could warn me of such a condition as where a notification has no confirmed endpoints.
---
In a previous post, I stated that the AWS alarm feature is super-easy to use. That may be the case, but it seems to not have sent me the notification mail I expected.
So now I am trying to find out information about what happened, and that turns out to be not so easy.
Clicking the link next to the alarm status icon gets you alarm info -- good. Then you can get history data pertaining to this alarm -- fine. And even some JSON describing what happened -- might be useful.
What seems not possible to get, is information about the action connected to the event. I am pretty sure that I filled in the e-mail field correctly, but what else might cause me to not get that email? So I want to check the settings in the connected action, which happens to have the name "NotifyMe".
In the "Edit" view, there is this information: "This is an SNS Console managed topic and cannot be viewed".
That's an unexpected complication. By the way, 'SNS' means 'Simple Notification Service'.
Entering the SNS Console, there is no trace of the email I entered back when I created the alarm. Mysterious.
Why did I think that it'd be easy, and Just Work? It's a rare event -- like diamonds -- when something just works. I should've tried the alarm out, of course.
Maybe there is an email sent as confirmation when the notification is set. Then you could check that email, and if you don't get that email, something is wrong.
Subscribe to:
Posts (Atom)