July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24672) Fuse Tooling New and Noteworthy for 4.5.0.AM2

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24672: ---------------------------------- Summary: Fuse Tooling New and Noteworthy for 4.5.0.AM2 Key: JBIDE-24672 URL: https://issues.jboss.org/browse/JBIDE-24672 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdk, openshift Reporter: Jeff MAURY Assignee: Andre Dietisheim Priority: Critical Fix For: 4.5.0.AM2 Andre Dietisheim, Search for your component's New and Noteworthy issues: Queries: * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for OpenShift by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-24614 #comment Create N&N for OpenShift 4.5.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24672) Fuse Tooling New and Noteworthy for 4.5.0.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24672?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24672: ------------------------------- Component/s: fusetools (was: cdk) (was: openshift) > Fuse Tooling New and Noteworthy for 4.5.0.AM2 > ------------------------------------------------------ > > Key: JBIDE-24672 > URL: https://issues.jboss.org/browse/JBIDE-24672 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.5.0.AM2 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24614 #comment Create N&N for OpenShift 4.5.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24667) fix ide-config.properties.py to work with respin suffixes, ed., AM1d

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24667?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24667. ------------------------------ Resolution: Done Hopefully fixed with this commit: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/e4d051... > fix ide-config.properties.py to work with respin suffixes, ed., AM1d > -------------------------------------------------------------------- > > Key: JBIDE-24667 > URL: https://issues.jboss.org/browse/JBIDE-24667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > {code} > * 5850114 - (HEAD -> master, origin/master, origin/HEAD) replace AM2d with AM2 nboldt(a)redhat.com (4 minutes ago) > * 1819d31 - update ide-config*.properties for staging release of jbosstools 4.5.0.AM2 / devstudio 11.0.0.AM2 nickboldt+devstudio-release(a)gmail.com (7 minutes ago) > * 4fdfe70 - release jbosstools 4.5.0.AM2 to QE nickboldt+devstudio-release(a)gmail.com (55 minutes ago) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24671) [jbosstools-openshift] Block PRs for merge untill the Jenkins build is successful

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24671?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24671: ------------------------------- Fix Version/s: 4.5.1.AM1 > [jbosstools-openshift] Block PRs for merge untill the Jenkins build is successful > --------------------------------------------------------------------------------- > > Key: JBIDE-24671 > URL: https://issues.jboss.org/browse/JBIDE-24671 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Nick asked: > {quote} > if we implement protected branches in github then no PRs can be merged w/o a PR review > so for projects like Base or Server, this would slow Rob down as he'd be even more dependent on PR reviews > for Openshift this would force Andre to break his PRs into smaller pieces so they could be more easily/quickly reviewed > otherwise all forward dev would be halted > so it's good from a "keep the code safe and clean" perspective > but if we don't actually get buy-in / acceptance from the people who submit the PRs and review them, it will block progress{quote} > Jeff replied: > {quote}I think this make more sense for OpenShift as we are more in a collaborative way, I have the feeling that Rob is more or less alone in server. So let's start with OpenShift but I would see this after the GA{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24671) [jbosstools-openshift] Block PRs for merge untill the Jenkins build is successful

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24671?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24671: ---------------------------------- Assignee: Nick Boldt > [jbosstools-openshift] Block PRs for merge untill the Jenkins build is successful > --------------------------------------------------------------------------------- > > Key: JBIDE-24671 > URL: https://issues.jboss.org/browse/JBIDE-24671 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Nick asked: > {quote} > if we implement protected branches in github then no PRs can be merged w/o a PR review > so for projects like Base or Server, this would slow Rob down as he'd be even more dependent on PR reviews > for Openshift this would force Andre to break his PRs into smaller pieces so they could be more easily/quickly reviewed > otherwise all forward dev would be halted > so it's good from a "keep the code safe and clean" perspective > but if we don't actually get buy-in / acceptance from the people who submit the PRs and review them, it will block progress{quote} > Jeff replied: > {quote}I think this make more sense for OpenShift as we are more in a collaborative way, I have the feeling that Rob is more or less alone in server. So let's start with OpenShift but I would see this after the GA{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24439) Block PRs for merge untill the Jenkins build is successful

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24439?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24439: ------------------------------------ Slip to 4.5.1.AM1 and create subtask for openshift as the first candidate project. > Block PRs for merge untill the Jenkins build is successful > ---------------------------------------------------------- > > Key: JBIDE-24439 > URL: https://issues.jboss.org/browse/JBIDE-24439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.1.AM1 > > > As discussed in this thread [1], we'd like to implement *Protected Branches* and > *Required Status Checks* [2] for some jbosstools-* projects. > [1] http://lists.jboss.org/pipermail/jbosstools-dev/2017-May/011948.html > [2] https://help.github.com/articles/defining-the-mergeability-of-pull-requests/ > We will therefore need to document some requirements in jbosstools-devdoc about how to properly submit PRs when version-bumping is required: > {quote}Make sure if your PR requires a version bump that the PR includes TWO commits. One for the change, and one for the version bump. That way the pair of commits can be built in the PR build and verify it works, AND when cherry picking the commit across branches, you can pick only the change and not the version-bump commit too. > {quote} > And we need to decide if we want to do what Fuse Tools does and require that PRs be reviewed before they can be merged, if we're ready to have that additional overhead on every PR. > [~jeffmaury] as project lead can you state which project(s) you'd like to see changed in github, and which ones should be changed as such: > * jbosstools-_____ > ** Protected Branch = master > ** Required Status Check(s) = ....? (which checks do we want) > ** PR reviews required = [true/false] > From that list of projects / requirements, we can then create subtask JIRAs to track the workj & the changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24439) Block PRs for merge untill the Jenkins build is successful

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24439?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24439: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.0.Final) > Block PRs for merge untill the Jenkins build is successful > ---------------------------------------------------------- > > Key: JBIDE-24439 > URL: https://issues.jboss.org/browse/JBIDE-24439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.1.AM1 > > > As discussed in this thread [1], we'd like to implement *Protected Branches* and > *Required Status Checks* [2] for some jbosstools-* projects. > [1] http://lists.jboss.org/pipermail/jbosstools-dev/2017-May/011948.html > [2] https://help.github.com/articles/defining-the-mergeability-of-pull-requests/ > We will therefore need to document some requirements in jbosstools-devdoc about how to properly submit PRs when version-bumping is required: > {quote}Make sure if your PR requires a version bump that the PR includes TWO commits. One for the change, and one for the version bump. That way the pair of commits can be built in the PR build and verify it works, AND when cherry picking the commit across branches, you can pick only the change and not the version-bump commit too. > {quote} > And we need to decide if we want to do what Fuse Tools does and require that PRs be reviewed before they can be merged, if we're ready to have that additional overhead on every PR. > [~jeffmaury] as project lead can you state which project(s) you'd like to see changed in github, and which ones should be changed as such: > * jbosstools-_____ > ** Protected Branch = master > ** Required Status Check(s) = ....? (which checks do we want) > ** PR reviews required = [true/false] > From that list of projects / requirements, we can then create subtask JIRAs to track the workj & the changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24671) [jbosstools-openshift] Block PRs for merge untill the Jenkins build is successful

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24671: ---------------------------------- Summary: [jbosstools-openshift] Block PRs for merge untill the Jenkins build is successful Key: JBIDE-24671 URL: https://issues.jboss.org/browse/JBIDE-24671 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.5.1.AM1 Reporter: Nick Boldt Nick asked: {quote} if we implement protected branches in github then no PRs can be merged w/o a PR review so for projects like Base or Server, this would slow Rob down as he'd be even more dependent on PR reviews for Openshift this would force Andre to break his PRs into smaller pieces so they could be more easily/quickly reviewed otherwise all forward dev would be halted so it's good from a "keep the code safe and clean" perspective but if we don't actually get buy-in / acceptance from the people who submit the PRs and review them, it will block progress{quote} Jeff replied: {quote}I think this make more sense for OpenShift as we are more in a collaborative way, I have the feeling that Rob is more or less alone in server. So let's start with OpenShift but I would see this after the GA{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24662) ITest for JBIDE-19604 - Save password in New Project App Wizard is annoying

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24662?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24662. ------------------------------ > ITest for JBIDE-19604 - Save password in New Project App Wizard is annoying > --------------------------------------------------------------------------- > > Key: JBIDE-24662 > URL: https://issues.jboss.org/browse/JBIDE-24662 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.5.0.AM2 > > > See Rob's comment in parent jira, part 3) https://issues.jboss.org/browse/JBIDE-19604?focusedCommentId=13432666&pag... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22680: ---------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Martin Malina > Fix For: 4.5.0.Final > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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