How To Integration JFrog Artifacts With RazorOps CI/CD

Created by Shiva G, Modified on Thu, 27 Apr 2023 at 03:28 PM by Shyam Mohan K

What are Artifacts?

An artifact is a byproduct of software development that helps describe the architecture, design and function of software. Artifacts are like roadmaps that software developers can use to trace the entire software development process

Artifacts might be databases, data models, printed documents or scripts. Artifacts aid in the maintenance and updating of software, as developers can use them as reference material to help resolve issues. Artifacts are documented and stored in a repository so they can be retrieved by software developers upon demand.

Software artifacts are typically created during the software development process and can refer to specific methods or processes in the software's development. For example, a software build contains the developer's code as well as a range of different artifacts. Some of these artifacts explain how the software works, while others enable the software to run. For example, the code's artifacts might include dependencies, project source code or a list of resources. These artifacts are stored in a repository, so they can be kept organized and retrieved upon demand.

Code-related artifacts: 

This code acts as the foundation for the software and enables the developer to test the software before launching it. Code artifacts can include compiled code, setup scripts, test suites, generated objects and logs generated during testing and quality assurance .


The features of software artifacts

Storing software artifacts in an accessible manner brings many advantages to development teams and beyond. Amongst other things, they are used to articulate the objectives of the program, performance expectations, and feature content of the product. These can be reviewed by the team and the client to ensure that there’s a shared and unified vision.

Below we’ve outlined the most important benefits.

Roadmap from start to finish

Software artifacts are the backbone of software development as they provide developers with a roadmap for a program from start to finish. Without artifacts, it would be difficult to know which tools are necessary to build a fully functional program. This roadmap or template also allows teams to track the development process over time and find out whether workflows need to be adjusted to meet expectations, goals and deadlines.

Time efficiency

Software artifacts save time and thus, money. After all, nobody wants to develop a program that is already outdated by the time it’s ready to launch. This is why software artifacts should be at the center of the development process – they provide guidance and structure and help reduce the developers’ workload to fast-track certain steps and procedures. They also allow them to work around known bottlenecks and avoid common mistakes.

Easy upgrades and reusability

Once a program is ready to launch, it’s still not fully “finished” as every software needs updates for continuity. On average, a program will last for 3 to 5 years before it needs to be updated to maintain its functionality. Software artifacts facilitate this process. What is more, developers can also examine documentation, code, and other artifacts from past products to gather ideas and determine how to approach technical problems in new projects.


The upkeep of a program can take a lot of time and effort. Tasks range from fixing occasional errors or bugs that come up during usage over time, or solving problems that arise when new features are added or when the program is replaced entirely. When software artifacts are created, all these potential issues are being addressed which prolongs the duration of use and helps maintain the software in check.

Developing prototypes

Before a program is fully developed and launched, clients usually want to see a prototype showing what the final product will actually look like and what the user will experience. Essentially, this prototype is a true artifact that will assist developers in connecting the mere idea of a product to a functioning program. It’s also fairly easy to make corrections on the prototype as opposed to the finished software product.

Jfrog could account creation :

Goto main website of jfrog ->

Select start for free 

Next, signup  with your working email address 

After successful sign up login with email 

After login we get jfrog dashboard 

Goto quick setup -> select package type 

Here we choosing docker 

Here we select set me up it show cli of entire process 

Cli for push:

Cli for pull :

Integrated with Razorops :

Here i login to our razorops account with working github account  

Goto integrations Tab , connect  jFrog  artifact registry with  URL, USER, PASSWORD 

When the connection is successfully established, it will be displayed as shown below

Afterward, navigate to the workflow section and choose the repository you wish to use from GitHub in order to create a Docker image. 

We have .razorops.yaml  file with jfrog repository 




    runner: razorci/openjdk:11-buster


    - checkout

    - commands:

      - |

        mvn clean package

           ls -a

    - docker/build:


         push: true 

         tags: ["latest-v1"]

When we run it successfully we get logs ….

When it pushed to jfrog repo successfully we can find our package in packages 

We find our artifacts in docker-local which is mentioned as repo location 

Conclusion  :

    Integrating JFrog Artifacts with RazorOps CI/CD allows for seamless automation of the software delivery process. By following the steps outlined in the guide, developers can easily set up a pipeline that pulls and deploys artifacts from JFrog Artifactory to their desired environment. This integration improves the speed and efficiency of the software development life cycle, ultimately leading to better products and more satisfied customers.

If you require assistance with this guide, please feel free to ask for help by booking a ticket here.

Visit and Signup -

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article