[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash

danken (oVirt JIRA) jira at ovirt-jira.atlassian.net
Sun Oct 29 12:00:12 UTC 2017


    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35236#comment-35236 ] 

danken commented on OVIRT-1717:
-------------------------------

Until this is implemented, I've written a little script to automate what I do to find the latest tested version of a project


{code:shell}
$ cat ~/bin/ovirt-latest-tested 
#!/bin/sh

project=$1
[[ -z "$project" ]] && project=ovirt-engine

curl -s http://plain.resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/| grep "\"$project-[0-9]"|tail -1 |sed 's/.*git//;s/.el7.*//'
{code}


> When a component build passes OST, tag its git hash
> ---------------------------------------------------
>
>                 Key: OVIRT-1717
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: oVirt CI
>            Reporter: danken
>            Assignee: infra
>              Labels: change-queue, standard-ci
>
> Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20171029/cd70263c/attachment.html>


More information about the Infra mailing list