-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep successful build artifacts in Cloudbees #119
Comments
Without this, there will be no Archaius playbook and AMI before re:invent... just sayin' is all. |
Can you check this and see if that's what you expect? https://netflixoss.ci.cloudbees.com/job/archaius-master/lastSuccessfulBuild/artifact/ |
Almost. It is my understanding that Archaius has a web component that the clients talk to in order to get the properties, and as such, would have a WAR file to put into Tomcat as one of the artifacts. If this is not the case, then I am missing something... which is entirely possible |
This is planned but not done |
Ah, I see. So as it stands now, Archaius is a library only, not a service. I'll keep an eye on #132 and build an AMI once that has been released and in Cloudbees or GitHub. Thanks. |
The master branch is built by Jenkins here:
https://netflixoss.ci.cloudbees.com/job/archaius-master/
... but it does not keep build artifacts from the latest successful build. Asgard, Edda and Eureka do:
https://netflixoss.ci.cloudbees.com/job/asgard-master/
Being able to download the successfully built WAR makes getting started with Archaius much easier.
Also, where is the mailing list for Archaius? I don't see it listed on the wiki like other projects... e.g.
https://groups.google.com/forum/#!forum/eureka_netflix
Thanks.
The text was updated successfully, but these errors were encountered: