September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23209) Notify PR associated users, when CI build for the PR fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23209?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23209: ------------------------------- Fix Version/s: 4.4.2.AM2 > Notify PR associated users, when CI build for the PR fails > ---------------------------------------------------------- > > Key: JBIDE-23209 > URL: https://issues.jboss.org/browse/JBIDE-23209 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Dmitrii Bocharov > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.AM2 > > > Create Jenkins hook, which will notify people involved in the commits that build is failing and notifying them back when build is back to ok -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23185) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23185?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23185. ------------------------------ Resolution: Done All subtasks except integration tests are done so closing. > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 > ------------------------------------------------------- > > Key: JBIDE-23185 > URL: https://issues.jboss.org/browse/JBIDE-23185 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-4052 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23021: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4049) Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4049?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4049: ---------------------------------- Is this something you want slipped into AM1 build today? https://github.com/jbdevstudio/jbdevstudio-product/pull/403 Haven't built it yet to verify - will do so if this is something we want in AM1. > Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required) > --------------------------------------------------------------------------------- > > Key: JBDS-4049 > URL: https://issues.jboss.org/browse/JBDS-4049 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, target-platform, updatesite, upstream > Affects Versions: 10.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > Attachments: ds10.1_on_neon.1.RC3_remediation_needed.png > > > Steps to repro: > 1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run > 2. Help > Eclipse Marketplace... > Search for "jboss" and install Red Hat JBoss Developer Studio 10.1.0.GA > 3. Remediation needed: > {code}Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > Software currently installed: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > Only one of the following can be installed at once: > JavaScript Development Tools Core 2.0.0.v201603171403 (org.eclipse.wst.jsdt.core 2.0.0.v201603171403) > JavaScript Development Tools Core 1.3.401.v201511181529 (org.eclipse.wst.jsdt.core 1.3.401.v201511181529) > JavaScript Development Tools Core 2.0.0.v201608251059 (org.eclipse.wst.jsdt.core 2.0.0.v201608251059) > JavaScript Development Tools Core 2.0.0.v201604281930 (org.eclipse.wst.jsdt.core 2.0.0.v201604281930) > JavaScript Development Tools Core 2.0.0.v201605251700 (org.eclipse.wst.jsdt.core 2.0.0.v201605251700) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > To: com.jboss.devstudio.core.rpm.feature.feature.group [10.1.0.v20160902-1725] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (RPM Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.rpm.feature.feature.group 10.1.0.v20160902-1725) > To: org.eclipse.wst.jsdt.feature.feature.group [2.0.0.v201605311817] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201605311817 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201605311817) > To: org.eclipse.wst.jsdt.core [2.0.0.v201605251700] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > To: org.eclipse.wst.jsdt.core [2.0.0.v201608251059] > {code} -- [^ds10.1_on_neon.1.RC3_remediation_needed.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4049) Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4049?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4049: ----------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/403 Story Points: 1 Sprint: devex #120 September 2016 > Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required) > --------------------------------------------------------------------------------- > > Key: JBDS-4049 > URL: https://issues.jboss.org/browse/JBDS-4049 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, target-platform, updatesite, upstream > Affects Versions: 10.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > Attachments: ds10.1_on_neon.1.RC3_remediation_needed.png > > > Steps to repro: > 1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run > 2. Help > Eclipse Marketplace... > Search for "jboss" and install Red Hat JBoss Developer Studio 10.1.0.GA > 3. Remediation needed: > {code}Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > Software currently installed: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > Only one of the following can be installed at once: > JavaScript Development Tools Core 2.0.0.v201603171403 (org.eclipse.wst.jsdt.core 2.0.0.v201603171403) > JavaScript Development Tools Core 1.3.401.v201511181529 (org.eclipse.wst.jsdt.core 1.3.401.v201511181529) > JavaScript Development Tools Core 2.0.0.v201608251059 (org.eclipse.wst.jsdt.core 2.0.0.v201608251059) > JavaScript Development Tools Core 2.0.0.v201604281930 (org.eclipse.wst.jsdt.core 2.0.0.v201604281930) > JavaScript Development Tools Core 2.0.0.v201605251700 (org.eclipse.wst.jsdt.core 2.0.0.v201605251700) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > To: com.jboss.devstudio.core.rpm.feature.feature.group [10.1.0.v20160902-1725] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (RPM Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.rpm.feature.feature.group 10.1.0.v20160902-1725) > To: org.eclipse.wst.jsdt.feature.feature.group [2.0.0.v201605311817] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201605311817 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201605311817) > To: org.eclipse.wst.jsdt.core [2.0.0.v201605251700] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > To: org.eclipse.wst.jsdt.core [2.0.0.v201608251059] > {code} -- [^ds10.1_on_neon.1.RC3_remediation_needed.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22966: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.AM2 > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23151) script creation of PRs by generic user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23151?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23151: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > script creation of PRs by generic user > -------------------------------------- > > Key: JBIDE-23151 > URL: https://issues.jboss.org/browse/JBIDE-23151 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Need the ability to create, submit, and merge PRs automatically as a generic user, so that changes to filesystem on download.jboss.org & devstudio.redhat.com (filemgmt) can be done automatically. > Spoke with [~akazakov] today to discuss how to proceed: > * new user "devstudio-release" for: jbdevstudio-website and jbosstools-downloads.jboss.org repos > * in future might also fork jbosstools-website repo so that changes to products.yaml can be automated too > * ideally, this would be a non-password (plaintext in config.xml = bad) authentication. github auth token? ssh key? > * maybe run this in isolation on wonka? that way less people have access to the config.xml of the job > * @Nick to explore getting more ssh keys for pushing to filemgmt.jboss.org > * @Nick to create user & start generating PRs for changes to dl.jb.o and ds.rh.c -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23036: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM1) > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22819) wrap staging build process with a jenkins job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22819: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > wrap staging build process with a jenkins job > --------------------------------------------- > > Key: JBIDE-22819 > URL: https://issues.jboss.org/browse/JBIDE-22819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Job requires about 13 params: > {code} > version (JBT and JBDS) > versionWithRespin (JBT and JBDS) > versionWithRespin_PREV (JBT and JBDS) > target platforms (min, max, central) > respin # (- or a, b, c) > devsuite installerExe url > stream_JBT=master # or 4.4.neon > stream_DS=master # or 10.0.neon > {code} > See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23140) Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23140?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23140: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Provision a RHEL7 slave with mock and rpmbuild on dev-platform central-ci > ------------------------------------------------------------------------- > > Key: JBIDE-23140 > URL: https://issues.jboss.org/browse/JBIDE-23140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.4.1.Final > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > Attachments: buildlog.txt, yum.install.list.partial.txt, yum.install.list.sort.txt, yum.install.list.txt > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016