JFrog offers a free 14-day trial that allows you to try out the JFrog Cloud Platform. After you sign up for a trial, a wizard will guide you through these actions on the platform:
Creating local, remote, or virtual repositories
Setting up your CI tool opposite Artifactory
Setting up your package manager client opposite Artifactory
CI Integration FAQ
The JFrog CI setup wizard guides you through connecting your CI tool to Artifactory as part of the free trial. If you have a specific use case, or if you have any issues that were not covered by the tutorial, refer to the questions below to resolve your issue and continue your journey.
General Questions
Q: I’m using an existing project that already has a CI script. Should I replace my CI script with the snippet in the integration wizard, or update it with the snippet?
A: Update your existing CI script with the JFrog snippet. As a result, your workflow will use JFrog for resolving dependencies and deploying artifacts to your JFrog repository. For more information and examples of how this can be done, go to GitLab Templates.
Q: Apart from setting up my CI tool, do I also need to configure the package manager my CI tool uses? For example, for Maven, do I need to set up a Maven client’s
pom.xml?A: No, the JFrog CLI automatically configures the developer client that is installed on the build machine/ runner.
Q: What are the packages I see in my JFrog repository after connecting JFrog to my pipeline?
A: Your CI tool now uses the JFrog repository to resolve dependencies from remote sources (e.g. from npm.js in case of npm), as well as to deploy the packages created by your CI process. You’ll see all these in your JFrog repository.
Q: I can’t find my question in this list, what can I do?
A: Contact us
GitHub
Q: I see a failed workflow run named
initial commitafter creating the repository on GitHub. What should I do?A: You can ignore this error. After you complete all steps on the JFrog side, a new workflow run will be created.
Q: My workflow run failed. What should I do?
A: Try the following:
Make sure you completed all the steps on the JFrog wizard, including updating the YAML file. These steps are necessary for the workflow to run successfully.
Double-check that you have created all the secrets, and that they do not contain any spaces or new lines.
Q: Are there any required settings when creating the repository on GitHub?
A: No: you can choose any name you like and set the repository to either Public or Private.
GitLab
Q: My build failed to run. What should I do?
A: Try the following:
Make sure that your account is eligible for running CI pipelines. Note that if you are using a GitLab Free account, you might need to enter credit card information or install local runners to enable pipelines.
Make sure you completed all the steps on the JFrog wizard, including updating the YAML file. These steps are necessary for the workflow to run successfully.
Double-check that you have created all the secrets, and that they do not contain any spaces or new lines
Make sure your GitLab runner, or the machine that hosts it, has the relevant package manager available (For example, an npm client in case you are using npm). If you’re using Unix, curl needs to be available.
Q: I can’t find the Settings tab
A: You might not have enough permissions to configure your project or account.
Jenkins
Q: I can't find the JFrog plugin under Available Plugins.
A: You might already have it installed: check if it appears under Installed Plugins.
Q: I already have a plugin named ‘Artifactory plugin’ installed. Can I use it instead of installing a new one?
A: Using the existing plugin would work, but we do recommend installing the new plugin and having both plugins work side by side. If you would like to use your existing plugin, note that it is not the same plugin that we refer to in the wizard and the instructions for it are different. To complete the installation, follow the documentation page for this plugin.