February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23536: ------------------------------------ Note that the jobs that are run here have been migrated to CCI: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: build, release, release-eng > Fix For: 4.4.3.Final > > Attachments: run.log > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Claudio Weiler (JIRA)

Claudio Weiler created JBIDE-23872: -------------------------------------- Summary: Tools clear war deployed files Key: JBIDE-23872 URL: https://issues.jboss.org/browse/JBIDE-23872 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.4.2.Final Environment: Windows 7 64 JDK 8 Eclipse Neon 1 JBoss Tools 4.4 WildFly 10.1 Reporter: Claudio Weiler Priority: Minor After an Eclipse start war deployed files are deleted and not republished. I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23536 at 2/6/17 1:48 PM: ------------------------------------------------------------ Yes, my bad -- the email should have had your username, not jiralint. I'll see if I can return an error AND the jira number as well. was (Author: nickboldt): I wonder if the problem is that the jiralint user doesn't have permission to assign JIRAs, and I implied you should use that user instead of your own user. Next time try running the python commands as yourself, not the jiralint user. > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: build, release, release-eng > Fix For: 4.4.3.Final > > Attachments: run.log > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23536: ------------------------------------ I wonder if the problem is that the jiralint user doesn't have permission to assign JIRAs, and I implied you should use that user instead of your own user. Next time try running the python commands as yourself, not the jiralint user. > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: build, release, release-eng > Fix For: 4.4.3.Final > > Attachments: run.log > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23718) RedDeer: Maximize workbench shell & make sure its visible when tests are started

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23718?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23718. ------------------------------------ > RedDeer: Maximize workbench shell & make sure its visible when tests are started > -------------------------------------------------------------------------------- > > Key: JBIDE-23718 > URL: https://issues.jboss.org/browse/JBIDE-23718 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.3.AM2 > > > https://github.com/jboss-reddeer/reddeer/issues/1517 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23715) RedDeer: Eclipse wizard dialogs should handle open perspective shell

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23715?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-23715: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > RedDeer: Eclipse wizard dialogs should handle open perspective shell > -------------------------------------------------------------------- > > Key: JBIDE-23715 > URL: https://issues.jboss.org/browse/JBIDE-23715 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > https://github.com/jboss-reddeer/reddeer/issues/1565 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23842) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [aerogear-hybrid]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23842?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23842. ------------------------------ Resolution: Done > For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [aerogear-hybrid] > ---------------------------------------------------------------------------- > > Key: JBIDE-23842 > URL: https://issues.jboss.org/browse/JBIDE-23842 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.Final > > > For JBIDE 4.4.3.Final [aerogear-hybrid]: 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.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.3.Final-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.26.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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.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...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23843) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [arquillian]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23843?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23843. ------------------------------ Resolution: Done > For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [arquillian] > ----------------------------------------------------------------------- > > Key: JBIDE-23843 > URL: https://issues.jboss.org/browse/JBIDE-23843 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.Final > > > For JBIDE 4.4.3.Final [arquillian]: 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.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.3.Final-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.26.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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.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...], or [Search for arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23844) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [foundation]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23844?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23844. ------------------------------ Resolution: Done > For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-23844 > URL: https://issues.jboss.org/browse/JBIDE-23844 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.Final > > > For JBIDE 4.4.3.Final [foundation]: 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.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.3.Final-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.26.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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final > > {code} > mvn clean verify -Dtpc.version=4.60.2.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...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23733: ------------------------------------ My 9 concerns have been addressed. Thanks! Resolving, with future work in JBIDE-23866 and JBIDE-23760. > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to run as smoke tests are in this buildflow job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017