[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo

2018-06-24 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1690:

Epic Link:   (was: OVIRT-400)

> Add CI for groovy/pipeline code in 'jenkins' repo
> -
>
> Key: OVIRT-1690
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: CI client projects
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task, groovy, jenkins
>
> We don't have any CI for Groovy code currently.
> At the very least we need to check that the code compiles, this is a bit 
> harder then it sounds because in order to test compilation for piepline code 
> we need to mock out things like the '{{NonCPS}}'  decorator which is not 
> supported by the standard Groovy compiler.
> Ideally we can also ass support for a full test suit.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5Z66B72YUNYDGCT6J2UZTTEU55AC7Y4E/


[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo

2018-06-24 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1690:

Epic Link: (was: OVIRT-400)

> Add CI for groovy/pipeline code in 'jenkins' repo
> -
>
> Key: OVIRT-1690
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: CI client projects
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task, groovy, jenkins
>
> We don't have any CI for Groovy code currently.
> At the very least we need to check that the code compiles, this is a bit 
> harder then it sounds because in order to test compilation for piepline code 
> we need to mock out things like the '{{NonCPS}}'  decorator which is not 
> supported by the standard Groovy compiler.
> Ideally we can also ass support for a full test suit.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5S4IASOEY6V4U5QHIM3PJSECFTUEH6FP/


[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo

2018-02-05 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1690:

Labels: first_time_task groovy jenkins  (was: groovy jenkins)

> Add CI for groovy/pipeline code in 'jenkins' repo
> -
>
> Key: OVIRT-1690
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: CI client projects
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task, groovy, jenkins
>
> We don't have any CI for Groovy code currently.
> At the very least we need to check that the code compiles, this is a bit 
> harder then it sounds because in order to test compilation for piepline code 
> we need to mock out things like the '{{NonCPS}}'  decorator which is not 
> supported by the standard Groovy compiler.
> Ideally we can also ass support for a full test suit.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo

2018-01-10 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1690:

Component/s: (was: oVirt CI)
 CI client projects

> Add CI for groovy/pipeline code in 'jenkins' repo
> -
>
> Key: OVIRT-1690
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: CI client projects
>Reporter: Barak Korren
>Assignee: infra
>  Labels: groovy, jenkins
>
> We don't have any CI for Groovy code currently.
> At the very least we need to check that the code compiles, this is a bit 
> harder then it sounds because in order to test compilation for piepline code 
> we need to mock out things like the '{{NonCPS}}'  decorator which is not 
> supported by the standard Groovy compiler.
> Ideally we can also ass support for a full test suit.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo

2017-10-08 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1690:

Epic Link: OVIRT-400

> Add CI for groovy/pipeline code in 'jenkins' repo
> -
>
> Key: OVIRT-1690
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: Barak Korren
>Assignee: infra
>  Labels: groovy, jenkins
>
> We don't have any CI for Groovy code currently.
> At the very least we need to check that the code compiles, this is a bit 
> harder then it sounds because in order to test compilation for piepline code 
> we need to mock out things like the '{{NonCPS}}'  decorator which is not 
> supported by the standard Groovy compiler.
> Ideally we can also ass support for a full test suit.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo

2017-10-08 Thread Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1690:
---

 Summary: Add CI for groovy/pipeline code in 'jenkins' repo
 Key: OVIRT-1690
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
  Components: oVirt CI
Reporter: Barak Korren
Assignee: infra


We don't have any CI for Groovy code currently.

At the very least we need to check that the code compiles, this is a bit harder 
then it sounds because in order to test compilation for piepline code we need 
to mock out things like the '{{NonCPS}}'  decorator which is not supported by 
the standard Groovy compiler.

Ideally we can also ass support for a full test suit.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100063)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra