[jbosstools-issues] [JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283033#comment-13283033 ] 

Nick Boldt edited comment on JBIDE-19911 at 8/23/16 3:56 PM:
-------------------------------------------------------------

Could this be added back into your bucket for 4.4.2? It would be nice to get this completed, or at least be able to work with you on a solution we're both happy with.

Goal is to improve speed of doing TP updates so anyone can do them:
A. user opens a JIRA (manual step)
B. user runs a job to create a mirror of the updated requirement [1] or [2]
C. user generates a PR for jbosstools-target-platforms *.target files & wait for PR to be built/approved

In step C, the user could run verifyTarget.sh [3] within a Jenkins job to verify the changes are correct. But then the dirty workspace / PR can't actually be pushed to github unless we add a fork to (for example) the rhdevelopers-ci user).

[1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstoolstargetplatformrequirements-mirror-matrix/
[2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-requirements/

[3] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/util/verifyTarget.sh

[~mickael_istria] do you know who has the username/pwd for rhdevelopers-ci user ? Or should we create a new one?


was (Author: nickboldt):
Could this be added back into your bucket for 4.4.2? It would be nice to get this completed, or at least be able to work with you on a solution we're both happy with.

> Create a (manual) job to update a given 3rd-party project on TP
> ---------------------------------------------------------------
>
>                 Key: JBIDE-19911
>                 URL: https://issues.jboss.org/browse/JBIDE-19911
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Mickael Istria
>             Fix For: 4.4.x
>
>
> For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request.
> * Input: sourceSite, initialMirror (as found in .target), targetMirror
> * Then
> ** job mirros the sourceSite
> ** job publishes (scp) it to targetMirror
> ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target
> ** job runs "mvn fix-version ..." on multiple/*.target
> ** "mvn clean verify -Pmultiple2repo" on multiple/*.target
> ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER
> ** p2diff
> ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)