-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for using a GitLab CI-pipeline as source for the 'source up-to-dateness' metric #3927
Labels
Source(s)
New, enhanced, or removed metric source
Comments
fniessink
changed the title
Allow for using a CI-job or pipeline as source for the 'source up-to-dateness' metric
Allow for using a GitLab CI-pipeline as source for the 'source up-to-dateness' metric
Oct 6, 2022
fniessink
added a commit
that referenced
this issue
Nov 18, 2022
%VOTE |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GitLab already supports the source-up-to-dateness metric for files in GitLab. Use the same solution as for Azure DevOps: present both file path and pipeline parameters to the user and indicate in the tooltip that files get preference.
Note: Jenkins and Azure DevOps don't need to be changed. In case of Jenkins the source up-to-dateness of jobs can be measured (job artifacts have the same date, so no need to configure artifacts separately). In case of Azure DevOps Quality-time already supports both files and pipelines.
Reported by @Sebastiaan127001
The text was updated successfully, but these errors were encountered: