January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016, devex #127 February 2017 (was: devex #115 May 2016, devex #116 June 2016) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.AM2 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.Final > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23317) Create and use Oxygen.M5 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23317?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23317: ------------------------------- Sprint: devex #120 September 2016, devex #125 December 2016, devex #127 February 2017 (was: devex #120 September 2016, devex #125 December 2016, devex #126 January 2017) > Create and use Oxygen.M5 target platform > ---------------------------------------- > > Key: JBIDE-23317 > URL: https://issues.jboss.org/browse/JBIDE-23317 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM1 > > > Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > 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

[JBoss JIRA] (JBIDE-23515) Create and use Neon.2 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23515?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23515: ------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Create and use Neon.2 target platform > ------------------------------------- > > Key: JBIDE-23515 > URL: https://issues.jboss.org/browse/JBIDE-23515 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.3.Final > > > Once available in December, we should move up to Neon.2 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > 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

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4233: ----------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > 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 > 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-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: ------------------------------------ Turns out I don't have a variable for the installer version so for now I'll leave your job as is. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... triggered from my script to verify. > 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 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23020) Integration tests: provide a cdk instance that tests running in jenkins can use

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23020?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23020. ------------------------------ cdk is running on all rhel slaves in CentralCI > Integration tests: provide a cdk instance that tests running in jenkins can use > ------------------------------------------------------------------------------- > > Key: JBIDE-23020 > URL: https://issues.jboss.org/browse/JBIDE-23020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM2 > > > We dont have a dedicated OS instance for the integration tests. > Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. > Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling is not working with OpenShift 3.4 (CDK 2.4)

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-23817: ---------------------------------- Summary: Scaling is not working with OpenShift 3.4 (CDK 2.4) Key: JBIDE-23817 URL: https://issues.jboss.org/browse/JBIDE-23817 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.3.AM2 Environment: CDK 2.4 Devstudio 10.3.0.AM2 Reporter: Radim Hopp Priority: Critical Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20426) JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20426?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20426: -------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-20426 > URL: https://issues.jboss.org/browse/JBIDE-20426 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: The Alchemist > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > This usually happens when I have a few big EARs attached, so I think the "checker" doesn't wait long enough to see if WF actually restarted. > The result is this weird situation where the "Servers" view says that it's "Stopped", but the Console view has the red square to terminate the process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23662) Scaling To/Up/Down: causes error message (from OpenShift API) reporting outdated objects

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23662?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23662. ------------------------------ Verified in Devstudio 10.3.0.AM2. Closing > Scaling To/Up/Down: causes error message (from OpenShift API) reporting outdated objects > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23662 > URL: https://issues.jboss.org/browse/JBIDE-23662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Ricardo Martinelli Oliveira > Assignee: Andre Dietisheim > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.3.AM2 > > Attachments: scale-error-object-modified.png > > > Every Scale option I select in the OpenShift Explorer view show this error: > Unable to scale guestbook-service > Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/sample-project/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "guestbook-service-2": the object has been modified; please apply your changes to the latest version and try again > However, the scale command is executed successfuly. > Steps to reproduce: > # ASSERT: make sure that you have a service with at least 1 pod running in OpenShift > # EXEC: in OpenShift Explorer: select your service and pick "Scale > To" in the context menu > # ASSERT: "Scale Deployment" dialog is shown, prefilled with the current number of replicas > # EXEC: change the replicas to a high number (ex. 6 is working well for me to cause the error) > # ASSERT: you get the error, if not process with next step > # EXEC: in OpenShift Explorer: select your service and pick "Scale > To" in the context menu and scale down to "1" replica > Result: > either you now get the error above or you need to scale back up etc. > !scale-error-object-modified.png! -- 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 January 2017