I have Free edition of JFrog Artifactory and tried installing Jfrog Xray, i can see Xray service is up and running but i cannot see any difference in Artifactory UI (Xray tab).
Can anyone pls mention are you using Free edition of Xray or Xray will only comes up with Paid version of Artifactory?
The answer to this question depends on whether you are using the Self-hosted instance or the SaaS.
As you can see in the JFrog documentation (https://www.jfrog.com/confluence/display/JFROG/JFrog+Xray) on Xray (at the top right corner - Subscription levels), Xray is only available for Pro-X and above licenses for a self-hosted instance.
However, if you are using the SaaS - it should be available for the free version as well.
it’s available on free tier, but visible on UI if you choose at the beginning that you are interested with security and vulnerabilities.
Another way to make it visible on the UI is to upload a package / image and then inside the package details you should have a “Security” tab where there you will have a banner to enable xray in the UI
Related
Seems strange asking this on SO but that's what MS want us to do so here goes...
I'm looking at setting up an on-premise Azure DevOps 2019 server, but as usual the licensing and costs aren't very transparent.
Our dev team are likely to be getting Visual Studio Pro subscriptions, which I believe comes with a DevOps server license and CALs. What happens if we stop these subscriptions - does it mean we can no longer use our on-premise DevOps server?
I'm not very clear on what "extras" we may need to pay for (extensions, pipelines), and I don't want to be hit by any surprises. The essential requirements are:
Be able to trigger a build on check-in. I can't tell if this is a built-in feature or requires some kind of extension and/or pipeline (and if so free or not?)
Use build tasks to create NuGet packages and host these on the in-house server. Again, does this require any paid extensions or pipelines?
There should be no limits on monthly build time (unlike VSTS which I believe is 240 minutes)
To my best understanding:
You can run Azure DevOps Server 2019 with at least one Visual Studio Professional or Enterprise license.
The features available to each user are based on the licence assigned to the user: Stakeholders (no license) get the very basics, Basic access (Professional) gives you most of the features, Enterprise gives you all the features.
The most notable differences between Basic and Enterprise are:
View Releases and Manage Approvals
Artifacts Microsoft published
Azure DevOps Extensions
However, per this annoucement, Artifacts are now included in the Basic/professional license.
So with only professional licenses you should be good for triggering builds, publishing and using nuget-packages via Artifact feeds. I'd think that installing extensions might require Enterprise user and haven't tested "View Releases and Manage Approvals" without Enterprise license yet. That seems to have changed from older TFS we've been using, in which Basic users were able to create and view releases.
So would recommend getting at least one Enterprise license, in any case.
one and two are free, third one is free with self hosted agent and 1800 minutes with hosted agent, if you are an opensource project you have lots of free compute time (dont think this applies to Azure Devops server though).
Build and release pipelines are included in Azure Devops Server 2019. https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2019?view=azure-devops#changes-to-artifacts-and-release-management-deployment-pipeline-licensing
We have JIRA, BitBucket and Bamboo, all integrated running locally on a server.
I would like to have Bamboo build my software when I decide to release it in JIRA.
There is a document available at Atlassian that describes this:
https://confluence.atlassian.com/jirasoftwarecloud/running-a-bamboo-build-when-releasing-a-version-764478184.html
The problem is that my interface doesn't have the Build Variables as described in the documentation. This is crucial, because I want JIRA to pass the version number and Bamboo to use that as a variable for different tasks.
Here is a screenshot of the interface:
I realise that the docs are for JIRA cloud, but seeing that the same interface is available on the server edition, I would expect to be able to accomplish the same thing.
We use JIRA version 7.9.2 and Bamboo version 6.5.1
Does anyone know why the Build Variables might be missing, or how else to tackle passing variables from JIRA to Bamboo in a self-hosted situation?
I worked around this by using the "Dump variables to log" job to check what variables are available. As it turns out the JIRA version is available when a build is triggered through the JIRA "release" button.
The variable I could use is bamboo.jira.version.
This doesn't solve the actual problem of defining arbitrary variables in JIRA and passing them on to Bamboo, but it solves the problem in my use-case, as I was looking to pass the release version.
Update:
I have an offical answer form Atlassian regarding this question.
I was under the impression that the custom variables you want to pass are defined on the release screen in JIRA itself.
As it turns out, variables are defined on the plan or global level in Bamboo, and they can then be used/overridden on the release screen in JIRA.
It works now!
We have self hosted GitLab CE and Jira, we want
link git commit with jira issue
link git commit with jira issue status, like we can start/move/close issue by git issues
limit above operations on specific branches, e.g., change issue status only when commits on master branch since we perform merge request for every single feature/bug
but only GitLab EE built-in supports Jira integration, how could I do that for GitLab CE?
I'm on GitLab CE 7.8.2, Jira+Agile 6.4
I think there is now a better way:
https://docs.gitlab.com/ce/user/project/integrations/jira.html
GitLab can be configured to interact with JIRA. Configuration happens via user name and password. Connecting to a JIRA server via CAS is not possible.
Each project can be configured to connect to a different JIRA instance, see the configuration section. If you have one JIRA instance you can pre-fill the settings page with a default template. To configure the template see the Services Templates document.
Once the project is connected to JIRA, you can reference and close the issues in JIRA directly from GitLab.
You can take a look at this project : https://github.com/akraxx/gitlab-jira-integration. It's a Java application, so you will need a server with a JVM to run it.
Follow the README to know how to configure it :)
Note that, with GitLab 13.3 (August 2020), you don't have to setup a third-party integration on each project anymore.
You can do so at your managed Gitlab instance level (free edition).
Instance-level project integration management for external services
Administrators of self-managed GitLab can now integrate third-party services with all projects on the instance from a single interface.
Previously, integrations had to be configured per project, which meant that if an instance had thousands of projects, thousands of individual configurations had to be manually configured. Not only was this time-consuming, but it was also error-prone, hard to update, and made it difficult to enforce integrations as a policy.
By configuring integrations across all projects, administrators save themselves and their project owners incredible amounts of time and effort.
This is the first iteration of this functionality. In upcoming releases, we will expand this feature to the group level, add more configuration and compliance options, and more.
See Documentation and Issue.
Plus, with GitLab 13.4 (September 2020)
GitLab for Jira and DVCS Connector now in Core
For users of Jira GitLab, the GitLab for Jira app and the DVCS Connector
allow you to display information about GitLab
commits and merge requests directly in Jira.
Combined with our native
integration with Jira, you can easily move back and forth between the
two applications as you work.
These features were previously available only in our Premium plan, but
are now available to all users!
See Documentation and Issue.
See GitLab 13.6 (November 2020)
Group-level management of project integrations
In GitLab 13.3, we added the ability to enable an integration across an entire instance.
With GitLab 13.6, that feature is being expanded to allow integrations to be managed at the group level as well!
Group owners can now add an integration to a group, and that integration will be inherited by all projects under that group.
This has the potential for saving massive amounts of time, as many organizations have specific integrations that they want rolled out to every project they create.
A great example of this is using our Jira integration. If you’re using Jira, it’s almost always across the whole company. Some of these companies have thousands of projects and therefore had to configure each and every one of those integrations individually.
With group-level management of project integrations, you can add the integration at each parent group, reducing the amount of configuration required by orders of magnitude!
Read more in our announcement on the GitLab blog.
See Documentation and Epic.
With GitLab 13.10 (March 2021):
View Jira issue details in GitLab
Users of our Jira issue list feature can now view the details of an issue directly inside of GitLab! This MVC enables developers to see the details, labels, and comments on an issue, giving them the ability to stay in GitLab while working on Jira issues.
Our goal is to empower developers to stay inside of GitLab during the majority of their day, and this is now one less trip to Jira you’ll have to make.
In GitLab 13.10, this feature is available if you enable a feature flag. This feature will be enabled by default in GitLab 13.11.
See Documentation and Epic.
At the moment I think the GitLab Listener add-on for JIRA is the only way to integrate GitLab CE and JIRA. You can use commit messages to generate JIRA worklogs, comments and activities, as well as execute workflow transitions. The add-on also tries to map GitLab users to JIRA users in order to link worklogs, comments, etc. to the right user.
It's a simple add-on and maybe it does not cover all your requirements, but it's better than nothing :).
I spent some time in both JIRA website and here, but still couldn't figure out. I have background from ClearCase ClearQuest and RTC. e.g. in CCCQ integration, when a developer check-out a file, he can select a task/bug from CQ due to the integration.
I installed JIRA and Subvertion, and JIRA Subversion plugin. Now couldn't figure out how to achieve the same I do with CCCQ integration.
Please give me a step-by-step instructions. Thanks.
Jirong
Here you go, from the Atlassian documentation: https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Subversion
We are happy with JIRA and there is no willingness to move away from it. At present we have JIRA integrated well with Perforce. However we are considering moving to Kiln.
Losing the integration with JIRA would be a blocker.
Perforce not Proforce, right? Kiln has an API that could be used to integrate with JIRA, but I would also consider using Fisheye (from Atlassian) to interact directly with the Mercurial repositories used by Kiln. You could also use the JIRA Mercurial plugin that I wrote to interact with those repositories if you didn't want Fisheye for some reason.
This is an area that I know Atlassian are interested in finding out what people want. If you want to drop me a note about this I can forward it to their Dev Tools group.
Since Kiln uses Mercurial under the hood, you might also want to consider Atlassian's BitBucket, which is a hosted Mercurial repository.