[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-22305:
----------------------------------------
JBIDE-22308 tracks a subpart of this overall automation.
> automate process for fetching latest target platform mirrors
> ------------------------------------------------------------
>
> Key: JBIDE-22305
> URL: https://issues.jboss.org/browse/JBIDE-22305
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, updatesite, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha3
>
>
> Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names.
> Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace.
> Thus for webtools we might simply define:
> webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do...
> and we'd end up with:
> http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8....
> * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr
> 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p...
> 2. when all children are done, a downstream job can runs TP update & validation against new .target files
> * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> * parse that into a list of URLs
> * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files
> * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs
> * resulting edited .target files will remain in the workspace, and we can then run
> * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> * when done if success:
> * ideally, generate a PR and attach link in email to jbosstools-dev@
> * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR
> * email should includes boilerplate text to send mail to list announcing new change for review
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-695) Generate p2diff together when generating TP site
by Mickael Istria (JIRA)
Mickael Istria created JBTIS-695:
------------------------------------
Summary: Generate p2diff together when generating TP site
Key: JBTIS-695
URL: https://issues.jboss.org/browse/JBTIS-695
Project: JBoss Tools Integration Stack
Issue Type: Enhancement
Components: target-platform
Affects Versions: 4.3.0.Final-TP
Reporter: Mickael Istria
In the "multiple2repo" profile, add the necessary build steps to always generate the p2diff report.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3877) can't import bigger maven/git project to jbds
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3877?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3877:
--------------------------------------
[~jludvice] Do you have the opportunity to try this against a plain Eclipse IDE milestone? If it's happening too, it would be an upstream issue to report to m2e.
> can't import bigger maven/git project to jbds
> ---------------------------------------------
>
> Key: JBDS-3877
> URL: https://issues.jboss.org/browse/JBDS-3877
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 9.1.0.GA
> Reporter: Josef Ludvicek
> Assignee: Viacheslav Kabanovich
> Fix For: 10.x
>
> Attachments: jbds-error.png, jbds-import-camel-stuck.png, jbds-import-camel1.png, jbds-thread-tump.tdump, log.log, stdout.txt
>
>
> JBDS can't import sources of Apache Camel (maven project)
> https://github.com/apache/camel
> Steps to reproduce:
> Clone it's git repo
> {code}
> git clone git@github.com:apache/camel.git
> {code}
> In jbds File -> Import Existing maven project
> Unselect "resolve workspace projects"
> Watch all CPU cores load on 100 % (tested on lenovo T440s / Intel i7 / Fedora 23)
> Wait for error message (~20 minutes)
> {code}
> An internal error occurred during: "Importing Maven projects".
> Java heap space
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-694) Update drools test suite
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-694?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-694:
------------------------------------
Issue Type: Task (was: Feature Request)
> Update drools test suite
> ------------------------
>
> Key: JBTIS-694
> URL: https://issues.jboss.org/browse/JBTIS-694
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: drools/ jBPM, QE
> Affects Versions: 4.3.0.Final
> Reporter: Tomas David
> Assignee: Tomas David
>
> This task consists from these subtasks:
> * remove brms 5 tests
> * remove unused annotations
> * remove unused groups
> * replace wait method with reddeer AbstractWait
> * reorganize test packages
> * use drools naming instead of brms
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months