[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=13441339#comment-13441339 ] 

Nick Boldt commented on JBIDE-19911:
------------------------------------

The problem w/ automatically creating a PR is that often more things have to change/move than a simple version update.

So while this new process might help for simple TP changes [1], it would fail for more complex ones [2].

[1] https://github.com/jbosstools/jbosstools-target-platforms/commit/43fa3eae71c5350d82dc46adfcd55235a2144eda
[2] https://github.com/jbosstools/jbosstools-target-platforms/commit/eb958eaccee6f8f2fb2afb6c27b4b7d594ea60c8 https://github.com/jbosstools/jbosstools-target-platforms/commit/1d8cbef290ea2e2a6d3ef7d8cb0c1f43cd4533ab#diff-16690ca9d00457669a97641c8ad358d5R125 https://github.com/jbosstools/jbosstools-target-platforms/commit/6803358686d73f89e314fae61ccb9ed8fb6d3406 https://github.com/jbosstools/jbosstools-target-platforms/commit/d41824990406c320374fd6d02e430bbe04f9846e

Since I'm the only person who ever initiates TP updates, and no one has complained that the process is too onerous since last summer, I'm going to assume our process here is adequate, and will close this. 

One improvement coming in the next sprint will be to eliminate the need to build BOTH a JBT and devstudio target platform, since they're now identical. See JBIDE-24772

> 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
>            Assignee: Nick Boldt
>             Fix For: 4.5.0.Final
>
>
> 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
(v7.2.3#72005)