[JBoss JIRA] (JBIDE-20148) releng scripts is an outdated version; jobs are not seeing latest from Nexus
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20148?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20148 at 6/30/15 4:15 PM:
-------------------------------------------------------------
Using overWrite=true and private maven repo...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
Doesn't work.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... shows the --del flag is still being ignored by the mojo :(
was (Author: nickboldt):
Using overWrite=true and private maven repo...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> releng scripts is an outdated version; jobs are not seeing latest from Nexus
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20148
> URL: https://issues.jboss.org/browse/JBIDE-20148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Labels: needinfo, nexus
> Fix For: 4.3.0.Beta2
>
>
> I've made some commits in the 4.3.x branch [0] of the build-ci repo, which should echo more details into the log.
> [0] https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x
> And the latest commits ARE built and available in Nexus [1], [2]:
> [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... [2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> Yet, no such output appears when the job is run, which makes me think that the -d and --del flags are NOT being passed to the script.
> Here's a snippet from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... :
> {code}
> + /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/.repository -B -U -fae -e -P hudson,unified.target,pack200,fetch-source-zips -Djbosstools_site_stream=master
> ...
> [INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @ org.jboss.tools.site.core ---
> ...
> rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
> {code}
> Yet when I run THE SAME SCRIPT from the workspace via shell, I get what I want:
> {code}
> + . /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo -t mars/snapshots/updates/core/master --del
> ...
> [DEBUG] RSYNCFLAGS = --del
> ...
> [INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
> ++ rsync -arzq --protocol=28 --del ... tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
> {code}
> So... what am I doing wrong? Why isn't the mojo using the latest version of the rsync script, but it's IN the workspace [3] ?
> [3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20148) releng scripts is an outdated version; jobs are not seeing latest from Nexus
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20148?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20148:
------------------------------------
Using overWrite=true and private maven repo...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> releng scripts is an outdated version; jobs are not seeing latest from Nexus
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20148
> URL: https://issues.jboss.org/browse/JBIDE-20148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Labels: needinfo, nexus
> Fix For: 4.3.0.Beta2
>
>
> I've made some commits in the 4.3.x branch [0] of the build-ci repo, which should echo more details into the log.
> [0] https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x
> And the latest commits ARE built and available in Nexus [1], [2]:
> [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... [2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> Yet, no such output appears when the job is run, which makes me think that the -d and --del flags are NOT being passed to the script.
> Here's a snippet from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... :
> {code}
> + /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/.repository -B -U -fae -e -P hudson,unified.target,pack200,fetch-source-zips -Djbosstools_site_stream=master
> ...
> [INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @ org.jboss.tools.site.core ---
> ...
> rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
> {code}
> Yet when I run THE SAME SCRIPT from the workspace via shell, I get what I want:
> {code}
> + . /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo -t mars/snapshots/updates/core/master --del
> ...
> [DEBUG] RSYNCFLAGS = --del
> ...
> [INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
> ++ rsync -arzq --protocol=28 --del ... tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
> {code}
> So... what am I doing wrong? Why isn't the mojo using the latest version of the rsync script, but it's IN the workspace [3] ?
> [3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20164) webtools server adapter installation shows "null"
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20164:
-------------------------------------
Keeping this issue of the feature name separate, the previous feature name that showed in this UI was featureName=JBossAS Tools
Would you suggest "JBoss / WildFly / EAP Server Tools" as a valid feature name? This feature name will be the same in the jbt update site as well as the server UI... so the name needs to work for both.
> webtools server adapter installation shows "null"
> -------------------------------------------------
>
> Key: JBIDE-20164
> URL: https://issues.jboss.org/browse/JBIDE-20164
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
> Attachments: Install_New_Extension_and_New_Server.png
>
>
> When using the "download additional adapters" for JBoss Tools it has a few issues.
> a) shows "null" for vendor
> b) does not actually say it is for WildFly nor EAP servers
> c) (idea) should we add OpenShift to this ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20170) WebTools server adapter installer installs only a subset of what should be installed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20170?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20170:
-------------------------------------
The feature being found and installed is very clearly org.jboss.ide.eclipse.as.serverAdapter.wtp.feature, evidence by the name being displayed in the UI.
> WebTools server adapter installer installs only a subset of what should be installed
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-20170
> URL: https://issues.jboss.org/browse/JBIDE-20170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> Steps to repro:
> {code}1. open clean Eclipse JEE
> 2. open Servers view
> 3. click 'No servers are avail... click to create new server..."
> 4. click "Download additional server adapters"
> (Site used to resolve IUs is http://download.jboss.org/jbosstools/updates/webtools/mars/ which symlinks to http://download.jboss.org/jbosstools/mars/development/updates/core/ )
> 5. wait while the stuff loads. select "JBoss AS Server Adapter" or whatever it was called
> 6. wait as metadata loads again
> 7. click Next, accept license, etc. restart when prompted
> {code}
> Feature that should have been installed:
> {code:title=https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L99-L103}
> <feature id="org.jboss.ide.eclipse.as.feature">
> <category name="org.eclipse.wst.server.core.serverAdapter"/>
> </feature>
> {code}
> Feature that instead gets installed:
> {code}org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta1-v20150612-2158-B25{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-20171:
----------------------------------
Summary: buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA
Key: JBIDE-20171
URL: https://issues.jboss.org/browse/JBIDE-20171
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Affects Versions: 4.3.0.Beta2
Reporter: Nick Boldt
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files!
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
[ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences
[ERROR] commitId .
[ERROR] If you have locally built projects which are aggregated here,
[ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
[ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
[ERROR] -> [Help 1]{code}
This happened after I put a buildinfo.json file here:
http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
I've since moved the file here to temporarily work around the build failure:
http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20168 at 6/30/15 3:51 PM:
-------------------------------------------------------------
Seems that buildinfo.json reader isn't happy with my manually created json, and builds are failing as a result. I've removed the xulrunner buildinfo.json file because it's trying to compare the SHA in that file to the one in the MANIFEST.MF (and there is none because this was built >2 years ago).
So... maybe we need to rebuild xulrunner to use the latest parent pom & generate it:
https://github.com/jbosstools/jbosstools-xulrunner/pull/15
was (Author: nickboldt):
Seems that buildinfo.json reader isn't happy with my manually created json.
So... maybe we need to rebuild xulrunner to use the latest parent pom & generate it:
https://github.com/jbosstools/jbosstools-xulrunner/pull/15
> create buildinfo.json files for old project builds which predate buildinfo.json generator
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20168
> URL: https://issues.jboss.org/browse/JBIDE-20168
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Max asked:
> {quote}
> i'm asking what shah's was used in the build for these components.
> No sure if you are trolling me by us keeping having these conversations everytime we need to tag :)
> Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right.
> and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-20170) WebTools server adapter installer installs only a subset of what should be installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20170?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20170 at 6/30/15 3:48 PM:
-------------------------------------------------------------
Related: JBIDE-19757
For the Alpha2 wtp site, I got an error installing but it was installing the CORRECT feature:
{quote}
Switching back to the Alpha2 site:
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: JBossAS Tools 3.1.0.Alpha2-v20150417-0145-B13 (org.jboss.ide.eclipse.as.feature.feature.group 3.1.0.Alpha2-v20150417-0145-B13)
{code}
{quote}
was (Author: nickboldt):
Related: JBIDE-19757
> WebTools server adapter installer installs only a subset of what should be installed
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-20170
> URL: https://issues.jboss.org/browse/JBIDE-20170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> Steps to repro:
> {code}1. open clean Eclipse JEE
> 2. open Servers view
> 3. click 'No servers are avail... click to create new server..."
> 4. click "Download additional server adapters"
> (Site used to resolve IUs is http://download.jboss.org/jbosstools/updates/webtools/mars/ which symlinks to http://download.jboss.org/jbosstools/mars/development/updates/core/ )
> 5. wait while the stuff loads. select "JBoss AS Server Adapter" or whatever it was called
> 6. wait as metadata loads again
> 7. click Next, accept license, etc. restart when prompted
> {code}
> Feature that should have been installed:
> {code:title=https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L99-L103}
> <feature id="org.jboss.ide.eclipse.as.feature">
> <category name="org.eclipse.wst.server.core.serverAdapter"/>
> </feature>
> {code}
> Feature that instead gets installed:
> {code}org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta1-v20150612-2158-B25{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months
[JBoss JIRA] (JBIDE-19178) Explorer: Add "Pipeline" view to OpenShift v3 explorer
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-19178:
---------------------------------------
[~maxandersen] [~adietish] I attached a screen shot of an 'app' from the console which is really a loose term. I believe we basically group things by the service and then fill in some choice details from the other pieces based on how they match up via ports, selectors, labels, etc. Given we don't have the freedom of html and are limited to a tree, I would be interested in understanding how you think this would best be presented. I'll try to sketch some idea.
Also, whats the easiest way to introduce the logical/pipeline view? Some right click context 'switch' view (content provider) or a separate view all together. My assumption is ultimately we would want to refactor the existing content provider so that we dont have sync issues between various 'views' of all the same stuff
> Explorer: Add "Pipeline" view to OpenShift v3 explorer
> ------------------------------------------------------
>
> Key: JBIDE-19178
> URL: https://issues.jboss.org/browse/JBIDE-19178
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jeff Cantrill
> Labels: explorer, openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: Console of 'App' with the pieces wired.png
>
>
> Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 3 months