March 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 commented on JBIDE-24182: ------------------------------------ Steps to script are as follows (copied from [4]) {code} // https://issues.jboss.org/browse/JBIDE-22819 // ########################################### // Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central // Verify all branches have been created // Verify all root poms point to the correct parent pom version build("jbosstools-push-to-staging-01-check-versions-branches-root-poms_master", stream_jbt: params["stream_jbt"], stream_ds: params["stream_ds"], github_branch: params["github_branch"], version_parent: params["version_parent"], version_jbt: params["version_jbt"], version_ds: params["version_ds"] ) // Disable jobs by hand as it needs to be run as a kerberos user - see release guide! // Build Discovery Sites build("jbosstools-discovery_" + params["stream_jbt"], VERSION: params["BUILD_ALIAS"], TARGET_PLATFORM_VERSION_MAX: params["TARGET_PLATFORM_VERSION_MAX"], TARGET_PLATFORM_CENTRAL_MAX: params["TARGET_PLATFORM_CENTRAL_MAX"] ) // Copy & rename builds & update sites from "snapshots" to "staging" build("jbosstools-push-to-staging-02-copy-builds-and-update-sites_master", stream_jbt: params["stream_jbt"], stream_ds: params["stream_ds"], versionWithRespin_jbt: params["versionWithRespin_jbt"], versionWithRespin_ds: params["versionWithRespin_ds"], TARGET_PLATFORM_VERSION_MAX: params["TARGET_PLATFORM_VERSION_MAX"], TARGET_PLATFORM_CENTRAL_MAX: params["TARGET_PLATFORM_CENTRAL_MAX"] ) // Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing build("jbosstools-push-to-staging-03-verify-builds-update-sites_master", versionWithRespin_jbt: params["versionWithRespin_jbt"], versionWithRespin_ds: params["versionWithRespin_ds"] ) // generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/ // See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... // generate PR for Release the latest staging site to ide-config.properties // See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... // re-enable jobs -- see https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... // disable this job // TODO: enable this when the above steps are automated - can't send emails until PRs are applied // generate notification emails //build("jbosstools-push-to-staging-07-notification-emails_master", // version_jbt: params["version_jbt"], // version_ds: params["version_ds"], // versionWithRespin_jbt: params["versionWithRespin_jbt"], // versionWithRespin_ds: params["versionWithRespin_ds"], // TARGET_PLATFORM_VERSION_MIN: params["TARGET_PLATFORM_VERSION_MIN"], // TARGET_PLATFORM_VERSION_MAX: params["TARGET_PLATFORM_VERSION_MAX"], // TARGET_PLATFORM_CENTRAL_MAX: params["TARGET_PLATFORM_CENTRAL_MAX"], // respinSuffix: params["respinSuffix"] // ) {code} > 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)

7 years, 1 month

1
0
0 / 0

[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: ------------------------------- Description: 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 was: Job requires about 13 params: {code} version (JBT and JBDS) versionWithRespin (JBT and JBDS) versionWithRespin_PREV (JBT and JBDS) target platforms (min, max, central) respin # (- or a, b, c) devsuite installerExe url stream_JBT=master # or 4.4.neon stream_DS=master # or 10.0.neon {code} See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job > 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)

7 years, 1 month

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24182: ---------------------------------- Summary: 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.4.2.Final Job requires about 13 params: {code} version (JBT and JBDS) versionWithRespin (JBT and JBDS) versionWithRespin_PREV (JBT and JBDS) target platforms (min, max, central) respin # (- or a, b, c) devsuite installerExe url stream_JBT=master # or 4.4.neon stream_DS=master # or 10.0.neon {code} See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[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: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.2.Final) > 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 > > > Job requires about 13 params: > {code} > version (JBT and JBDS) > versionWithRespin (JBT and JBDS) > versionWithRespin_PREV (JBT and JBDS) > target platforms (min, max, central) > respin # (- or a, b, c) > devsuite installerExe url > stream_JBT=master # or 4.4.neon > stream_DS=master # or 10.0.neon > {code} > See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23961. ------------------------------ Verified in JBT 4.4.4.AM2. So we are back in state, where we can debug node.js apps, but only for a very short time (JBIDE-23422) > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, jbide-23961-restart-1.png, jbide-23961-restart-2.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24083. ------------------------------ Vedified in JBT 4.4.4.AM2. Closing. > Debug NodeJS app is broken - Failed to connect to Standalone V8 VM > ------------------------------------------------------------------ > > Key: JBIDE-24083 > URL: https://issues.jboss.org/browse/JBIDE-24083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.4.AM1 > Reporter: Pavol Srna > Assignee: Andre Dietisheim > Priority: Critical > Labels: regression > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: jbide-23961-restart-1.png > > > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1067) Clean update site files for stable/development/staging branch

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1067?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1067: ------------------------------------------ [~pleacu], since we released 10.2.0.GA you can now delete 10.2.0.GA from the staging branch > Clean update site files for stable/development/staging branch > ------------------------------------------------------------- > > Key: JBTIS-1067 > URL: https://issues.jboss.org/browse/JBTIS-1067 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.2.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Please clean update site files in stable/development/staging branch so that there are only html and p2 files at > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/ > {code} > and all binaries are in relevant folders such as > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/10.1.0.GA/ > {code} > Moreover, delete obsolete files from the branch 'staging'. By obsolete files I mean the following > || What we are working on? || Obsolete files || Files I'd like to keep || > | 10.2.0 | 10.0.CR1, 10.0.GA, 10.1.0.CRx, 10.1.0.GA | 10.2.0.CR1, 10.2.0.GA| > EDIT: the branch 'staging' should be cleaned after each official release (once a GA build is publicly available) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4283) migrate devstudio_10.0.neon jobs to CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4283?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4283: ----------------------------- Fix Version/s: 10.x (was: 10.4.0.AM2) > migrate devstudio_10.0.neon jobs to CCI > --------------------------------------- > > Key: JBDS-4283 > URL: https://issues.jboss.org/browse/JBDS-4283 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > > Migrate all jobs in this view to CCI: > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23017: ------------------------------- Labels: releasework (was: ) > use sshfs to speed up publishing process > ----------------------------------------- > > Key: JBIDE-23017 > URL: https://issues.jboss.org/browse/JBIDE-23017 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.4.AM2, 4.4.4.Final > > Attachments: staging-times.png > > > Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org. > If we could simply copy bits over sshfs, the process might be a lot faster than these times: > {code} > JBT coretests 1.1G: 59m20 > JBT core 1.2G: 64m23 > devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13 > devstudio (copy from local to www.qa) 3.1G: 6mins(?) > {code} > To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23678. -------------------------------- Resolution: Done Remediation is no longer required as to 4.4.4.AM2, since there's a new version of webtools in Neon.3. > remediation required installing jbosstools 4.4.3.AM1 on Neon.2 > -------------------------------------------------------------- > > Key: JBIDE-23678 > URL: https://issues.jboss.org/browse/JBIDE-23678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png > > > Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2. > Install manifest contains: > * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions), > * 1.6.201 (2 versions), and > * 2.0.200 (1 version) - *total 7 references*! > Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2017