[jira] [Updated] (OOZIE-3051) Replace Oozie's custom precommit build patch finding job with the standard Apache one

2017-09-07 Thread Robert Kanter (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-3051:
-
Description: 
We currently use a custom script in the 
[oozie-trunk-find-patches-available|https://builds.apache.org/job/oozie-trunk-find-patches-available/]
 Jenkins job to find patches on JIRA and submit a build to the 
[oozie-trunk-precommit-build|https://builds.apache.org/job/oozie-trunk-precommit-build/]
 job.  

There's a number of downsides to this, the main one being that we need to tie 
oozie-trunk-find-patches-available to a specific Jenkins host so we can store a 
file to remember what JIRAs were looked at already (H1).  Unfortunately, this 
means that whenever H1 is down, we can't get automatic pre-commit jobs.

Many projects, including Hadoop, Pig, Hive, etc use the 
[PreCommit-Admin|https://builds.apache.org/job/PreCommit-Admin/] job.  We 
should do that as well.

More details (though it appears to be a little out of date) are at 
http://wiki.apache.org/general/PreCommitBuilds

  was:
We currently use a custom script in the 
[oozie-trunk-find-patches-available|https://builds.apache.org/job/oozie-trunk-find-patches-available/]
 Jenkins job to find patches on JIRA and submit a build to the 
[oozie-trunk-precommit-build|https://builds.apache.org/job/oozie-trunk-precommit-build/]
 job.  

There's a number of downsides to this, the main one being that we need to tie 
oozie-trunk-find-patches-available to a specific Jenkins host so we can store a 
file to remember what JIRAs were looked at already (H1).  Unfortunately, this 
means that whenever H1 is down, we can't get automatic pre-commit jobs.

Many projects, including Hadoop, Pig, Hive, etc use the 
[PreCommit-Admin|https://builds.apache.org/job/PreCommit-Admin/] job.  We 
should do that as well.


> Replace Oozie's custom precommit build patch finding job with the standard 
> Apache one
> -
>
> Key: OOZIE-3051
> URL: https://issues.apache.org/jira/browse/OOZIE-3051
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-3051.001.patch
>
>
> We currently use a custom script in the 
> [oozie-trunk-find-patches-available|https://builds.apache.org/job/oozie-trunk-find-patches-available/]
>  Jenkins job to find patches on JIRA and submit a build to the 
> [oozie-trunk-precommit-build|https://builds.apache.org/job/oozie-trunk-precommit-build/]
>  job.  
> There's a number of downsides to this, the main one being that we need to tie 
> oozie-trunk-find-patches-available to a specific Jenkins host so we can store 
> a file to remember what JIRAs were looked at already (H1).  Unfortunately, 
> this means that whenever H1 is down, we can't get automatic pre-commit jobs.
> Many projects, including Hadoop, Pig, Hive, etc use the 
> [PreCommit-Admin|https://builds.apache.org/job/PreCommit-Admin/] job.  We 
> should do that as well.
> More details (though it appears to be a little out of date) are at 
> http://wiki.apache.org/general/PreCommitBuilds



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (OOZIE-3051) Replace Oozie's custom precommit build patch finding job with the standard Apache one

2017-09-07 Thread Robert Kanter (JIRA)

 [ 
https://issues.apache.org/jira/browse/OOZIE-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-3051:
-
Attachment: OOZIE-3051.001.patch

Attaching a dummy patch file to test with.

> Replace Oozie's custom precommit build patch finding job with the standard 
> Apache one
> -
>
> Key: OOZIE-3051
> URL: https://issues.apache.org/jira/browse/OOZIE-3051
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-3051.001.patch
>
>
> We currently use a custom script in the 
> [oozie-trunk-find-patches-available|https://builds.apache.org/job/oozie-trunk-find-patches-available/]
>  Jenkins job to find patches on JIRA and submit a build to the 
> [oozie-trunk-precommit-build|https://builds.apache.org/job/oozie-trunk-precommit-build/]
>  job.  
> There's a number of downsides to this, the main one being that we need to tie 
> oozie-trunk-find-patches-available to a specific Jenkins host so we can store 
> a file to remember what JIRAs were looked at already (H1).  Unfortunately, 
> this means that whenever H1 is down, we can't get automatic pre-commit jobs.
> Many projects, including Hadoop, Pig, Hive, etc use the 
> [PreCommit-Admin|https://builds.apache.org/job/PreCommit-Admin/] job.  We 
> should do that as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)