I have some question to a service called AWS CodeArtifact?
What is it and what is it useful for.
Any links to the documentation?
From 1
AWS CodeArtifact is a fully managed software artifact repository service that makes it easy for organizations of any size to securely store, publish, and share packages used in their software development process. CodeArtifact eliminates the need for you to set up, operate, and scale the infrastructure required for artifact management so you can focus on software development. With CodeArtifact, you only pay for what you use and there are no license fees or upfront commitments.
AWS CodeArtifact works with commonly used package managers and build tools such as Maven and Gradle (Java), npm and yarn (JavaScript), pip and twine (Python), making it easy to integrate CodeArtifact into your existing development workflows. CodeArtifact can be configured to automatically fetch software packages from public artifact repositories such as npm public registry, Maven Central, and Python Package Index (PyPI), ensuring teams have reliable access to the most up-to-date packages.
IT leaders can use AWS CodeArtifact to create centralized repositories for sharing software packages approved for use across their development teams. CodeArtifact’s integration with AWS Identity and Access Management (IAM) provides them with the ability to control who has access to the packages. Further, CodeArtifact’s support for AWS CloudTrail gives leaders visibility into which packages are in use and where, making it easy to identify packages that need to be updated or removed. CodeArtifact also supports encryption with AWS Key Management Service so customers can control the keys used to encrypt their packages.
Product Page: 2
It is an artifact repository from AWS. Refer this -
https://aws.amazon.com/codeartifact/
Related
We are investigating how to integrate our app with Github Enterprise.
There are 2 different deployment models - 'Cloud' and 'On Premise'
I have been looking around but couldn't find the differences between the two.
Maybe there is no such difference
The basic difference is that GitHub Enterprise Server is software you deploy on a virtual machine you provision and control (on-premise here is a bit of a misnomer since your VM could be in AWS).
GitHub Enterprise Cloud, on the other hand, is an enterprise-level of service at GitHub.com.
You'll find more here.
Python has an SSM client in the Boto 3 package: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ssm.html. Is there something similar for R? If not, any recommendations for how to make something similar? Thanks!
At the moment a package called paws on github
Access over 150 AWS services, including Machine Learning Translation
Natural Language Processing Databases File Storage
Or the cloudyr project
Welcome to the cloudyr project! The goal of this initiative is to make
cloud computing with R easier, starting with robust tools for working
with cloud computing platforms. The project’s inital work is with
Amazon Web Services, various crowdsourcing platforms, and popular
continuous integration services for R package development. Tools for
Google Cloud Services and Microsoft Azure are also on the long-term
agenda.
I only checked paws and that has the ssm functionality according to the paws documentation about ssm. The cloudyr project has many aws packages on cran. Not sure if in one of them is the ssm functionality.
I have some doubts regarding monitoring nexus OSS 3.0.1 server. Can some please let me know the following:-
Are there any health check REST APIs available which we can query to get the health of overall nexus OSS server and for individual repo? I have seen this link. But couldn't find any REST API for health check?
I am able to see "Metrics Core bundle" Active under Bundles. Can someone let me know if there is a way I can listen to these metrics?
Are there any plugin / integration avaiable for datadog?
In general how do people generally monitor nexus oss?
Nexus 3.0.1 exposes authenticated access to metrics using http://metrics.dropwizard.io/3.1.0/manual/servlets/
You have these endpoints available for different purposes:
{host:port}/service/metrics/healthcheck
{host:port}/service/metrics/data
{host:port}/service/metrics/ping
{host:port}/service/metrics/threads
I have been using JFrog Artifactory for a while in my company. Recently I learned about JFrog Bintray. What is the difference between Artifactory and Bintray? Is Bintray a replacement for Artifactory?
Thanks for the question, it's a good one!
The main difference between artifactory and bintray is in the intended usage. Artifactory is a development-time tool, while Bintray is a release, distribution-time tool. It might look like a subtle difference, but it has a great impact on the feature set of the products:
For development, you need features like:
support for snapshots
CI servers metadata integration (a.k.a. build-info)
promotion between repositories
on-prem install
development site replication
integration with enterprise security systems like SAML
etc.
For distribution, you need stuff like:
a global distribution network (CDN)
extreme throughput and redundancy for downloads
permission control for external users (entitlements)
product and EULA support
etc
As you can see, those are quite different lists.
Of course, there are common requirements:
full REST API automation
CLI
plugins for popular CI servers and build tools
indexing as much binary packages standards as possible
"Set Me Up" snippets for easy configuration
smart checksum-based binary storage
and of course there must be a simple way to roll out the artifacts from the
development-time tool to the distribution tool (a repository in
Artifactory that is synced with Bintray)
and we have all that covered of course :)
I am with JFrog, the company behind bintray and artifactory, see my profile for details and links.
I recently took on the responsibility for managing our company's builds and releases. We ship our products as both a web service and as a licensed product that customers can install on their internal servers.
My job involves making sure QA has the builds they need for testing, which may come from the main development branch or feature-specific branches, depending on their current focus, and may be for one of two different products. It also means releasing our products internally for dogfooding, which means we deploy to an internal server. Finally, I cut official builds for our customers by creating new versions of the installer for those who install internally, and pushing updates to the website for our hosted customers.
So far, I've picked up the Pragmatic Programmers' Ship It! and Release It!, both of which seem useful. What other books I should pick up and read? Are there communities or well-known bloggers I should follow that deal specifically with the challenges of building, deploying and shipping web services to our own servers and to customers internal servers?
I really liked Pragmatic Project Automation
CM Crossroads is an excellent resource.