The latest expert opinions, articles, and guides for the Java professional.
Tools of Choice
Here are the tools you will use, and the pipeline you will build out.
0. Identify Your Artifacts
This is step 0 because it’s all about preparation. Artifacts are pretty much the results of a development project, and the items you will need to take these deliverables to your users. Go ahead and list all these deliverables and items. We’re sure two come to mind: source code and built binaries. Here’s more:
Gates and required approvals along the pipeline
These artifacts are crucial components of the pipeline, and travel through it in order to deliver the final product or experience to your end users.
1. Create a source code repository using GitHub
This step is mentioned for the sake of completeness. Your development team is ideally already using a version control system (VCS) such as Subversion, Git, Mercurial or CVS.
However, if you’re trying this out on your own or are starting a new project, we suggest trying out Github, an incredibly popular remote repository for Git that takes only a couple of minutes to set up. So, for this exercise we will use GitHub.
Sign up/Login into your GitHub account
Click on the “new repo” button
Fill out the form
Download the Artifactory ZIP file. Use
wget -O < URL >to download from your prompt.
Extract and start artifactory:
unzip artifactory ZIP file
run artifactory.sh under the bin directory
Configure a repository:
navigate to login, enter: admin / password -> admin -> repositories -> new and fill in the form:
…and that’s really it! You’ve set up a remote Git repository. You can now clone it, push changes into it, and integrate into your delivery pipeline.
2. Create Artifact Repositories using Artifactory
Artifact repositories store your software product’s deliverables. They specialize in storing artifacts and their metadata and cataloguing their versions so that they can be quickly retrieved for development or deployment. Modern repositories provide other features like proxying to central repos, working with artifact dependencies and security. For the purposes of this exercise, we will just use the storage functions.
Let’s set up Artifactory by JFrog:
Artifacts can either be stored forever (e.g. major releases) or temporarily (e.g. quick and dirty builds). In repository language, they are called releases and snapshots respectively. To keep things simple, we’ll allow snapshots so our developers can upload any artifacts they choose.
DOWNLOAD THE PDF
Leave a comment