August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3982) create rh-eclipse46-devstudio rpm for linux installs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3982: ---------------------------------- I've pushed the above PR into jbdevstudio-product repo, and am working on parameterizing the URLs used to create the mirror so we can run this against different sites (nightly, staging, stable). Meanwhile, if the base package contains all the above, then I shouldn't have to update the spec file. Instead, what I need to do is remove features from the rh-eclispe46-devstudio rpm which are already installed via the base package. For example, there's no need to include PDE or EMF since they're already installed via rpm. But to achieve that I'll need to refactor the com.jboss.devstudio.core.feature, so it doesn't include/depend on things like PDE. Then we can include that smaller, less grabby feature in the RPM instead of the all-in-one-including-deps feature. Do you know where I can run this? I've staged it on two different Jenkins servers [1] [2] and both don't have RHEL7/Fedora24 slaves w/ mock installed. :( [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.rpm_master/ [2] http://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudio... > create rh-eclipse46-devstudio rpm for linux installs > ---------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 > will need to port http://download.jboss.org/jbosstools/updates/scripted-install/director.xml to bash so it can be called along with rpmbuilder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] 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/DevSt... [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [3] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... [~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)

9 years, 7 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19911: ------------------------------------ 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22305: ------------------------------------ True. But http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... can also be used for a single requirement mirror. > 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 > Labels: releasework > Fix For: 4.4.x > > Attachments: git.diff.txt > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23038) Fuse runtime detection never makes a server

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23038: ----------------------------------- Summary: Fuse runtime detection never makes a server Key: JBIDE-23038 URL: https://issues.jboss.org/browse/JBIDE-23038 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Reporter: Rob Stryker The runtime detectors never create the server, only the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4012) NPE in izpack installer Unpacker extension - progress tracker

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-4012?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-4012: ---------------------------------- [~akazakov] - can this get into AM3? (one pushed) > NPE in izpack installer Unpacker extension - progress tracker > ------------------------------------------------------------- > > Key: JBDS-4012 > URL: https://issues.jboss.org/browse/JBDS-4012 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Reporter: Paul Leacu > Assignee: Paul Leacu > > java.lang.NullPointerException > at com.izforge.izpack.installer.Unpacker.processRuntimes(Unpacker.java:865) > at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:589) > at java.lang.Thread.run(Thread.java:745) > Need to move the progress tracker down one line. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23037) JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23037?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23037. --------------------------------- Resolution: Done Done. coded, tested, fixed, and pushed. > JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse > ---------------------------------------------------------------------------- > > Key: JBIDE-23037 > URL: https://issues.jboss.org/browse/JBIDE-23037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.4.1.AM2 > Reporter: Paul Leacu > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM3 > > > Recent changes in runtimes.core meant to improve efficiency then keep track of which AbstractRuntimeDetectorDelegate created the runtime definition (the thing you see in the dialog) and when it seems time to actually create it we go back to that one that created it so we dont go asking 10 people to create things they dont know about. > ref: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > This is critical to the stand-alone installer for Fuse that includes a supplemental runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23037) JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23037?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23037: -------------------------------- Component/s: runtime-detection Fix Version/s: 4.4.1.AM3 Story Points: 1 Sprint: devex #119 August 2016 > JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse > ---------------------------------------------------------------------------- > > Key: JBIDE-23037 > URL: https://issues.jboss.org/browse/JBIDE-23037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.4.1.AM2 > Reporter: Paul Leacu > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM3 > > > Recent changes in runtimes.core meant to improve efficiency then keep track of which AbstractRuntimeDetectorDelegate created the runtime definition (the thing you see in the dialog) and when it seems time to actually create it we go back to that one that created it so we dont go asking 10 people to create things they dont know about. > ref: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > This is critical to the stand-alone installer for Fuse that includes a supplemental runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23037) JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23037?page=com.atlassian.jira.plugi... ] Paul Leacu updated JBIDE-23037: ------------------------------- Description: Recent changes in runtimes.core meant to improve efficiency then keep track of which AbstractRuntimeDetectorDelegate created the runtime definition (the thing you see in the dialog) and when it seems time to actually create it we go back to that one that created it so we dont go asking 10 people to create things they dont know about. ref: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... This is critical to the stand-alone installer for Fuse that includes a supplemental runtime. was: Recent changes in runtimes.core meant to improve efficiency then keep track of which AbstractRuntimeDetectorDelegate created the runtime definition (the thing you see in the dialog) and when it seems time to actually create it we go back to that one that created it so we dont go asking 10 people to create things they dont know about. ref: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse > ---------------------------------------------------------------------------- > > Key: JBIDE-23037 > URL: https://issues.jboss.org/browse/JBIDE-23037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Paul Leacu > Assignee: Rob Stryker > Priority: Critical > > Recent changes in runtimes.core meant to improve efficiency then keep track of which AbstractRuntimeDetectorDelegate created the runtime definition (the thing you see in the dialog) and when it seems time to actually create it we go back to that one that created it so we dont go asking 10 people to create things they dont know about. > ref: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > This is critical to the stand-alone installer for Fuse that includes a supplemental runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23037) JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse

by Paul Leacu (JIRA)

Paul Leacu created JBIDE-23037: ---------------------------------- Summary: JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse Key: JBIDE-23037 URL: https://issues.jboss.org/browse/JBIDE-23037 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.1.AM2 Reporter: Paul Leacu Assignee: Rob Stryker Priority: Critical Recent changes in runtimes.core meant to improve efficiency then keep track of which AbstractRuntimeDetectorDelegate created the runtime definition (the thing you see in the dialog) and when it seems time to actually create it we go back to that one that created it so we dont go asking 10 people to create things they dont know about. ref: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016