May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24182) wrap staging/release process with pipeline job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24182: ------------------------------- Sprint: devex #132 May 2017 > wrap staging/release process with pipeline job > ---------------------------------------------- > > Key: JBIDE-24182 > URL: https://issues.jboss.org/browse/JBIDE-24182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > In JBIDE-22819 I created a buildflow job to orchestrate the steps involved in staging or release of jbt/ds. > However, on CCI we can now write a pipeline job [1] in groovy, which can trigger downstream builds [2] and wait for approval/input [3] before continuing. This might be an ever better visualization & control for these stages/releases. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/vscode-j... -> https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile > [2] https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job > [3] https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile#L68 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4362: ----------------------------- Sprint: devex #132 May 2017 > Consider eliminating the devstudio EAP installer bundle? > -------------------------------------------------------- > > Key: JBDS-4362 > URL: https://issues.jboss.org/browse/JBDS-4362 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, integration-platform > Affects Versions: 10.4.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: devstudio-install-add-servers-01.png, devstudio-install-add-servers-02.png, devstudio-install-add-servers-03.png, devstudio-install-add-servers-04.png, devstudio-install-add-servers-05.png > > > For devstudio 11, we might want to eliminate the devstudio EAP installer. > If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free. > This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server. > Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely? > That way only the devSUITE installer would include EAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4397) Update year to 2017 on devstudio starting logo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4397?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4397. ------------------------------ Resolution: Done Resolving. Reopen (or open a new issue) if you find other places to update the copyright date to 2017. > Update year to 2017 on devstudio starting logo > ---------------------------------------------- > > Key: JBDS-4397 > URL: https://issues.jboss.org/browse/JBDS-4397 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.4.0.GA > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: Screenshot_20170517_140926.png, splash_2017.bmp > > > We should update logo copyright year from 2016 to 2017. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4397) Update year to 2017 on devstudio starting logo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4397?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4397: ----------------------------- Attachment: splash_2017.bmp > Update year to 2017 on devstudio starting logo > ---------------------------------------------- > > Key: JBDS-4397 > URL: https://issues.jboss.org/browse/JBDS-4397 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.4.0.GA > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: Screenshot_20170517_140926.png, splash_2017.bmp > > > We should update logo copyright year from 2016 to 2017. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4397) Update year to 2017 on devstudio starting logo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4397?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4397: ---------------------------------- Copyrights updated in features / licenses, and splash image. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=136 > Update year to 2017 on devstudio starting logo > ---------------------------------------------- > > Key: JBDS-4397 > URL: https://issues.jboss.org/browse/JBDS-4397 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.4.0.GA > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: Screenshot_20170517_140926.png > > > We should update logo copyright year from 2016 to 2017. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24450) jiralint console output should list JIRA URLs for easier access to updating them

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24450?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24450. ------------------------------ Resolution: Done Fixed. > jiralint console output should list JIRA URLs for easier access to updating them > -------------------------------------------------------------------------------- > > Key: JBIDE-24450 > URL: https://issues.jboss.org/browse/JBIDE-24450 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > jiralint console output should list JIRA URLs for easier access to updating them - that way when I run it to nag people for incomplete issues, I can at the same time set valid fixversions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24450) jiralint console output should list JIRA URLs for easier access to updating them

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24450?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24450: ------------------------------- Sprint: (was: devex #132 May 2017) > jiralint console output should list JIRA URLs for easier access to updating them > -------------------------------------------------------------------------------- > > Key: JBIDE-24450 > URL: https://issues.jboss.org/browse/JBIDE-24450 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > jiralint console output should list JIRA URLs for easier access to updating them - that way when I run it to nag people for incomplete issues, I can at the same time set valid fixversions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24450) jiralint console output should list JIRA URLs for easier access to updating them

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24450?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24450: ------------------------------- Fix Version/s: 4.5.0.AM1 > jiralint console output should list JIRA URLs for easier access to updating them > -------------------------------------------------------------------------------- > > Key: JBIDE-24450 > URL: https://issues.jboss.org/browse/JBIDE-24450 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > jiralint console output should list JIRA URLs for easier access to updating them - that way when I run it to nag people for incomplete issues, I can at the same time set valid fixversions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24395) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Integration-Tests]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24395?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24395: ------------------------------------ 3 of these are for master branch only. The last one was done in 4.4.x branch too: https://github.com/jbosstools/jbosstools-integration-tests/commit/f02d868... > For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Integration-Tests] > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24395 > URL: https://issues.jboss.org/browse/JBIDE-24395 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Jeff MAURY > Assignee: Len DiMaggio > Priority: Blocker > Labels: task > Fix For: 4.4.4.Final > > > For JBIDE 4.4.4.Final [Integration-Tests]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x. > Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x > 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-integration-tests at https://github.com/jbosstools/jbosstools-integration-tests > Searching for commits present in master and missing from jbosstools-4.4.x > Commit hash "81e053" is the last common ancestor of master and jbosstools-4.4.x > 81e053 is 25 commits ago in branch jbosstools-4.4.x > 81e053 is 25 commits ago in branch master > Commits missing from jbosstools-4.4.x that are in master: > * missing: Tests-extended-to-using-CDKv3-server-adapter-1793 https://github.com/jbosstools/jbosstools-integration-tests/commit/b161e1c... > * missing: JBIDE-23959-update-InstallDependencies.p2f-to-fetch-from-oxygen-not-neon-use-4.4.3-instead-of-4.3.0 https://github.com/jbosstools/jbosstools-integration-tests/commit/f028081... > * missing: JBIDE-23959-bump-to-4.4.100-SNAPSHOT-in-master-also-fix-broken-deps-to-org.jboss.tools-reddeer-plugins https://github.com/jbosstools/jbosstools-integration-tests/commit/d6562fb... > * missing: JBIDE-23959-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-integration-tests/commit/7071150... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Integration-Tests task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24395) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Integration-Tests]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24395?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24395. ------------------------------ Fix Version/s: 4.4.4.Final Assignee: Nick Boldt (was: Len DiMaggio) Resolution: Done > For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Integration-Tests] > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24395 > URL: https://issues.jboss.org/browse/JBIDE-24395 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Jeff MAURY > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.4.Final > > > For JBIDE 4.4.4.Final [Integration-Tests]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x. > Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x > 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-integration-tests at https://github.com/jbosstools/jbosstools-integration-tests > Searching for commits present in master and missing from jbosstools-4.4.x > Commit hash "81e053" is the last common ancestor of master and jbosstools-4.4.x > 81e053 is 25 commits ago in branch jbosstools-4.4.x > 81e053 is 25 commits ago in branch master > Commits missing from jbosstools-4.4.x that are in master: > * missing: Tests-extended-to-using-CDKv3-server-adapter-1793 https://github.com/jbosstools/jbosstools-integration-tests/commit/b161e1c... > * missing: JBIDE-23959-update-InstallDependencies.p2f-to-fetch-from-oxygen-not-neon-use-4.4.3-instead-of-4.3.0 https://github.com/jbosstools/jbosstools-integration-tests/commit/f028081... > * missing: JBIDE-23959-bump-to-4.4.100-SNAPSHOT-in-master-also-fix-broken-deps-to-org.jboss.tools-reddeer-plugins https://github.com/jbosstools/jbosstools-integration-tests/commit/d6562fb... > * missing: JBIDE-23959-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-integration-tests/commit/7071150... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Integration-Tests task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017