April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23322: ------------------------------- Sprint: devex #128 February 2017 (was: devex #128 February 2017, devex #131 May 2017 (JBIDE)) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} > Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > So we could use this to create composite sites in folders like: > * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date) > But also to point to remote (/stable/) URLs from pointer sites, like: > * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd) > * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1) > * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4233: ----------------------------- Sprint: devex #128 February 2017 (was: devex #128 February 2017, devex #131 May 2017 (JBIDE)) > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 11.0.0.AM1 > > Attachments: CCI-installed-plugins-Jenkins-1.609.3-1_list.txt > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24182: ------------------------------- Sprint: (was: devex #131 May 2017 (JBIDE)) > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23885) integration test: assert new element "Kind" and in all properties and changed structure in "Build" properties

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23885?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23885: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > integration test: assert new element "Kind" and in all properties and changed structure in "Build" properties > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23885 > URL: https://issues.jboss.org/browse/JBIDE-23885 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Jan Novak > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > > JBIDE-23841: In "Properties" we added a "Kind" property for all resources and changed the structure of the "Build" properties. > The integration tests should assert these changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24319) Create a script to get intermediate velocity reports for the cabal call

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24319?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24319: ------------------------------- Sprint: (was: devex #131 May 2017 (JBIDE)) > Create a script to get intermediate velocity reports for the cabal call > ----------------------------------------------------------------------- > > Key: JBIDE-24319 > URL: https://issues.jboss.org/browse/JBIDE-24319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.4.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: build, groovy > Fix For: 4.4.4.Final > > > Add a new script to get a velocity report for the cabal call per user. Should report completed, in review, in progress and open issues from the active sprint -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24004) Explore possibilities of automated bare metal windows provisioning

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24004?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24004: ------------------------------- Sprint: devex #128 February 2017, devex #131 April 2017 (was: devex #128 February 2017, devex #131 May 2017 (JBIDE)) > Explore possibilities of automated bare metal windows provisioning > ------------------------------------------------------------------ > > Key: JBIDE-24004 > URL: https://issues.jboss.org/browse/JBIDE-24004 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk, central-ci, devsuite > Fix For: 4.4.4.Final > > > Figure out how to provision bare metal windows machine with any tool in an automated manner. We want to have reliable windows machine that are capable of virtualization and thus, we can move on with our effort in CI process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24322: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Openshift publisher keeps getting more nested > --------------------------------------------- > > Key: JBIDE-24322 > URL: https://issues.jboss.org/browse/JBIDE-24322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: - OS: Windows 7 > - JbossDev: 10.3.0.0 > - Openshift Client: 3.4 > - Openshift Enterprise: 3.4 > - Workspace location: it's inside a network drive > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > > During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit. > We noticed that during the publishing or local change. > > The Publish function, always creates a nested deploy directory inside an existing one. > For instance inside /opt/eap/standalone/deployments/ > 1st Publish: > deploy/server.war/ > 2nd Publish: > deploy/deploy/server.war/ > 3nd Publish: > deploy/deploy/deploy/server.war/ > > So with 3 publish, you end up with 3 deployed same application. > This happen also inside the local workspaces for the synchronisation: > .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift > The EAP7 images is the jboss-eap70-openshift:latest. > > Do you have any idea why this happen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24315) Analyze model classes changes

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24315?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24315: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Analyze model classes changes > ------------------------------ > > Key: JBIDE-24315 > URL: https://issues.jboss.org/browse/JBIDE-24315 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3 > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24323) Set up docker registry when cdk 3 server adapter is started

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24323?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24323: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Set up docker registry when cdk 3 server adapter is started > ----------------------------------------------------------- > > Key: JBIDE-24323 > URL: https://issues.jboss.org/browse/JBIDE-24323 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.4.Final > > > Apparently nobody requested this for cdk 3 yet, so it hasn't been implemented. > For minishift / cdk 3, the command is: > minishift openshift registry -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23963) Create and use Neon.3 target platform

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23963?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23963: ------------------------------- Sprint: devex #128 February 2017 (was: devex #128 February 2017, devex #131 May 2017 (JBIDE)) > Create and use Neon.3 target platform > ------------------------------------- > > Key: JBIDE-23963 > URL: https://issues.jboss.org/browse/JBIDE-23963 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.4.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.4.Final > > Attachments: Screenshot_2017-03-24_11-10-30.png > > > Once available in March, we should move up to Neon.3 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > devstudio tp, > central tp; > jbt-build-sites (and parent pom), > devstudio site build (and devstudio root pom); > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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