[
https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-19911:
----------------------------------------
I'd split C into multiple steps:
C1. Update TP
C1a. Sed to change repository urls
C1b. Use the fix-version mojo to fix version
C2. Prepare commit locally
C3. Push commit
C4. Create PR
C5. Validate PR
Step C5 (verification of TP) automatically happens whenever a TP is published (
JBIDE-22312 ).
I don't have credentials for rhdevelopers-ci profile and I'm not aware of an
existing OAuth token we can reuse, but we can ask [~ppitonak] who IIRC manages this
account: Is it possible to get a clone of jbosstools/jbosstools-target-platform repository
and some tokens to push content/create PRs with it?
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)