[JBoss JIRA] (JBDS-3295) Product update fails on windows if installation folder and user home are on different devices
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3295?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3295:
--------------------------------
Workaround Description:
Workaround 1:
move installation to C:\ or wherever device user home folder is located
Workaround 2:
1) Stop JBDS
2) Go to the directory where your product .exe exit, for example: D:\IDEs\jbdevstudio\studio
3) Copy jbdevstudio.exe and paste it in the same place with another name (i.e. jbdevstudio2.exe)
4) Start JBDS using the copied file (jbdevstudio2.exe)
5) The update will complete successfully and the product will be restarted using the same exe file
6) Stop JBDS again
7) Delete jbdevstudio2.exe
8) Start JBDS as usual and enjoy
was:move installation to C:\ or wherever device user home folder is located
> Product update fails on windows if installation folder and user home are on different devices
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-3295
> URL: https://issues.jboss.org/browse/JBDS-3295
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: p2-product
> Affects Versions: 8.0.1.GA
> Environment: Windows
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18984:
-------------------------------
Description:
Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
This would mean less target platform churning DURING a release, and speed up the way we do releases.
Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
* one for JBT content (a subset of the JBT aggregate) and
* one for 3rd party content (an adjunct to the Central site)
This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself.
was:
Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
This would mean less target platform churning DURING a release, and speed up the way we do releases.
Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
* one for JBT content (a subset of the JBT aggregate) and
* one for 3rd party content (an adjunct to the Central site)
This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someon i
> Build Early Access site as an update site, not a TP
> ----------------------------------------------------
>
> Key: JBIDE-18984
> URL: https://issues.jboss.org/browse/JBIDE-18984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform, updatesite
> Affects Versions: 4.2.1.Final, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
> This would mean less target platform churning DURING a release, and speed up the way we do releases.
> Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
> * one for JBT content (a subset of the JBT aggregate) and
> * one for 3rd party content (an adjunct to the Central site)
> This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18984:
-------------------------------
Description:
Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
This would mean less target platform churning DURING a release, and speed up the way we do releases.
Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
* one for JBT content (a subset of the JBT aggregate) and
* one for 3rd party content (an adjunct to the Central site)
This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someon i
was:
Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
This would mean less target platform churning DURING a release, and speed up the way we do releases.
Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
* one for JBT content (a subset of the JBT aggregate) and
* one for 3rd party content (an adjunct to the Central site)
> Build Early Access site as an update site, not a TP
> ----------------------------------------------------
>
> Key: JBIDE-18984
> URL: https://issues.jboss.org/browse/JBIDE-18984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform, updatesite
> Affects Versions: 4.2.1.Final, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
> This would mean less target platform churning DURING a release, and speed up the way we do releases.
> Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
> * one for JBT content (a subset of the JBT aggregate) and
> * one for 3rd party content (an adjunct to the Central site)
> This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someon i
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18984:
-------------------------------
Fix Version/s: 4.3.0.Alpha1
> Build Early Access site as an update site, not a TP
> ----------------------------------------------------
>
> Key: JBIDE-18984
> URL: https://issues.jboss.org/browse/JBIDE-18984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform, updatesite
> Affects Versions: 4.2.1.Final, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
> This would mean less target platform churning DURING a release, and speed up the way we do releases.
> Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
> * one for JBT content (a subset of the JBT aggregate) and
> * one for 3rd party content (an adjunct to the Central site)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18984:
----------------------------------
Summary: Build Early Access site as an update site, not a TP
Key: JBIDE-18984
URL: https://issues.jboss.org/browse/JBIDE-18984
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, target-platform, updatesite
Affects Versions: 4.2.1.Final, 4.3.0.Alpha1
Reporter: Nick Boldt
Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
This would mean less target platform churning DURING a release, and speed up the way we do releases.
Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
* one for JBT content (a subset of the JBT aggregate) and
* one for 3rd party content (an adjunct to the Central site)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18984) Build Early Access site as an update site, not a TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-18984:
----------------------------------
Assignee: Nick Boldt
> Build Early Access site as an update site, not a TP
> ----------------------------------------------------
>
> Key: JBIDE-18984
> URL: https://issues.jboss.org/browse/JBIDE-18984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform, updatesite
> Affects Versions: 4.2.1.Final, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
> This would mean less target platform churning DURING a release, and speed up the way we do releases.
> Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
> * one for JBT content (a subset of the JBT aggregate) and
> * one for 3rd party content (an adjunct to the Central site)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBTIS-377) Update bpmn2-modeler for IS beta2 TP and aggregate
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-377?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-377.
------------------------------
Fix Version/s: 4.2.0.Beta1b-TP
Resolution: Done
Added new BPMN2 Modeler for SwitchYard fix
http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1...
> Update bpmn2-modeler for IS beta2 TP and aggregate
> --------------------------------------------------
>
> Key: JBTIS-377
> URL: https://issues.jboss.org/browse/JBTIS-377
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution, target-platform
> Affects Versions: 4.2.0.Beta2, 4.2.0.Beta2a-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.2.0.Beta1b-TP
>
>
> *Reason:* Pick up a new BPMN2 Modeler - ref blocker: https://issues.jboss.org/browse/SWITCHYARD-2484
> *Project page/sources:*
> *Version:* 4.2.0.Beta2b
> *License and owner:* EPL
> *Original p2 repo:* n/a
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/1...
> *Include Sources:* Yes
> *Affected projects:* JBDSIS 8.0.0.Beta2
> *Include in JBDS:* No
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> < org.eclipse.bpmn2.modeler.help [1.1.1.201411261859]
> < org.eclipse.bpmn2.modeler.feature.group [1.1.1.201411261859]
> < org.eclipse.bpmn2.modeler.core [1.1.1.201411261859]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201411261859]
> < org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201411261859]
> < org.eclipse.bpmn2.modeler.ui [1.1.1.201411261859]
> < org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201411261859]
> < org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201411261859]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.help [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.feature.group [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.core [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201412181844]
> > org.eclipse.bpmn2.modeler.ui [1.1.1.201412181844]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 8 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack.jbtis-377/target-platform/target/target-platform.target.repo contains 8 unique IUs
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18974) Latest Ionic app based on tabs template is not shown on HTM5 Preview
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18974?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18974:
------------------------------------------------
It looks like data-vpvid attributes which we add to tags brakes ionic. Have no idea why it starts showing anything after some refreshes(for me - friends tab doesn't work correctly)
> Latest Ionic app based on tabs template is not shown on HTM5 Preview
> --------------------------------------------------------------------
>
> Key: JBIDE-18974
> URL: https://issues.jboss.org/browse/JBIDE-18974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.1.Final
> Environment: Fedora 20 Linux x86_64
> OpenJDK 7
> SWT_GTK3=1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.2.Final
>
> Attachments: screenshot1.png, screenshot2.png
>
>
> The app works fine in internal browser, bit not in HTML5 Preview (see image screenshot1.png below).
> The same issue when I open external browser form preview. But after a while Refresh in external browser finally shows the page (see screenshot2.png below).
> After that it appears in preview as well.
> !screenshot1.png!
> !screenshot2.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15135 at 12/22/14 12:01 PM:
---------------------------------------------------------------
Apologies for the great delay in getting around testing this out and reviewing the output. Overall, this is a vast improvement over what we had before w/ a hodge-podge of shell scripts.
First, some clarifications to answer your questions & outline a bit more what I think this mojo has to do (beyond what it already does).
*{color:orange}CLARIFICATION{color}*
I don't think we need zip file references for two reasons:
a) they were originally added because we didn't have Eclipse-SourceReferences in the MANIFEST.MF files, and needed a way to collect all the upstream sources
b) they have generic names (rather than timestamped/buildID'd) so they're not really useful UNLESS the zips themselves are colocated in the build folder, which we no longer need.
*{color:orange}CLARIFICATION{color}*
As to the included metadata, we need:
* build details (re: the server/VM config, JDK version/paths, etc.), eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_...
* build log (only useful when things go wrong and access to Jenkins is slow/impossible, so not strictly REQUIRED, only helpful)
* git revs for upstream sources, eg., http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-...
----
Next, I tried to build & test this out.
*{color:blue}STEPS TO REPRO{color}*
In trying to use the above locally, I've realized 3 things:
a) you need to use <version>0.22.1-SNAPSHOT</version> as 0.22.0-SNAPSHOT is no longer available in Nexus or in your fork
b) you need to run a build of something like jbosstools-build-sites/aggregate/site/pom.xml with -DtychoVersion=0.22.0, as repository-utils now depends on on that
c) you need to build with JDK8, or get:
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site (generate-full-site) on project org.jboss.tools.site.core: Execution generate-full-site of goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site: java.lang.UnsupportedClassVersionError: org/json/JSONObject : Unsupported major.minor version 52.0
{code}
So, I inserted the above block into jbosstools-build-sites/aggregate/site/pom.xml (and fixed the version to be 0.22.1-SNAPSHOT), then:
{code}
$➔ mvn --version
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400)
Maven home: /opt/maven3
Java version: 1.8.0, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.17.4-200.fc20.x86_64", arch: "amd64", family: "unix"
{code}
{code}
$➔ mvn clean install -DtychoVersion=0.22.0 -DBUILD_ID=666 -DJOB_NAME=jbosstools-build-sites.aggregate.site_master -DHUDSON_SLAVE=dev69 -DRELEASE=no
{code}
----
And here are the results::
{code:title=aggregate/site/target/fullSite/all/repo/buildInfo.json}{
"upstream": {},
"properties": {
"BUILD_NUMBER": "666",
"RELEASE": "no",
"JOB_NAME": "jbosstools-build-sites.aggregate.site_master",
"HUDSON_SLAVE": "dev69"
},
"timestamp": 1419266314705,
"revision": {
"HEAD": "89898db85f9e38972360c42782247f0e2b7304b0",
"knownReferences": [{
"ref": "JBIDE-18869",
"name": "nickboldt",
"url": "git@github.com:nickboldt/jbosstools-build-sites.git"
}]
}
}{code}
{code:title=aggregate/site/target/fullSite/logs/GIT_REVISION.txt}
#Mon Dec 22 11:21:56 EST 2014
git@github.com\:nickboldt/jbosstools-build-sites.git\:JBIDE-18869=89898db85f9e38972360c42782247f0e2b7304b0
HEAD=89898db85f9e38972360c42782247f0e2b7304b0
{code}
{code:title=aggregate/site/target/fullSite/logs/build.properties}
BUILD_ALIAS=null
JOB_NAME=jbosstools-build-sites.aggregate.site_master
BUILD_NUMBER=666
BUILD_ID=null
HUDSON_SLAVE=dev69
RELEASE=no
ZIPSUFFIX=null
TARGET_PLATFORM_VERSION=null
TARGET_PLATFORM_VERSION_MAXIMUM=null
{code}
----
Now, some questions:
* *{color:red}QUESTION{color}* Should there be something in upstream?
* *{color:red}QUESTION{color}* What about details about the OS & JDK version?
* *{color:red}QUESTION{color}* Why are *TARGET_PLATFORM_VERSION*, *TARGET_PLATFORM_VERSION_MAXIMUM*, *BUILD_ALIAS* and *BUILD_ID* not resolved? The first 3 of those are from maven variables in the parent pom (if not set commandline), and BUILD_ID is a timestamp that could be the same as the one placed in GIT_REVISION.txt
* *{color:red}QUESTION{color}* Why is *WORKSPACE* not listed, and resolved to `pwd` ?
_This is often useful when builds fail to figure out where files have been created on a slave's filesystem, because they don't all use the same workspace path convention. And while you CAN browse the workspace within Jenkins, sometimes it's more efficient to do so over ssh._
* *{color:red}QUESTION{color}* Can you also generate an ALL_VERSIONS.txt for aggregate builds? Or does that only happen when the mojo detects there are upstream projects? If so, how do I tell the mojo that there are upstream projects when building locally?
* *{color:red}QUESTION{color}* Why did you change the format of GIT_REVSION.txt? I like that you've added details about the repo from which the code comes, but would a format such as the one below be more compact & easier to parse out the useful values of branch/tag, SHA, and source repo?
{code:title=http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-03-18_15-46-19-B706/logs/GIT_REVISION.txt}
origin/jbosstools-4.1.x@e81a5ff9a2d51345c25b6c2aac3783da3f60af32 , https://github.com/jbosstools/jbosstools-build-sites
{code}
was (Author: nickboldt):
Apologies for the great delay in getting around testing this out and reviewing the output. Overall, this is a vast improvement over what we had before w/ a hodge-podge of shell scripts.
First, some clarifications to answer your questions & outline a bit more what I think this mojo has to do (beyond what it already does).
*{color:orange}CLARIFICATION{color}*
I don't think we need zip file references for two reasons:
a) they were originally added because we didn't have Eclipse-SourceReferences in the MANIFEST.MF files, and needed a way to collect all the upstream sources
b) they have generic names (rather than timestamped/buildID'd) so they're not really useful UNLESS the zips themselves are colocated in the build folder, which we no longer need.
*{color:orange}CLARIFICATION{color}*
As to the included metadata, we need:
* build details (re: the server/VM config, JDK version/paths, etc.), eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_...
* build log (only useful when things go wrong and access to Jenkins is slow/impossible, so not strictly REQUIRED, only helpful)
* git revs for upstream sources, eg., http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-...
----
Next, I tried to build & test this out.
*{color:blue}STEPS TO REPRO{color}*
In trying to use the above locally, I've realized 3 things:
a) you need to use <version>0.22.1-SNAPSHOT</version> as 0.22.0-SNAPSHOT is no longer available in Nexus or in your fork
b) you need to run a build of something like jbosstools-build-sites/aggregate/site/pom.xml with -DtychoVersion=0.22.0, as repository-utils now depends on on that
c) you need to build with JDK8, or get:
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site (generate-full-site) on project org.jboss.tools.site.core: Execution generate-full-site of goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site: java.lang.UnsupportedClassVersionError: org/json/JSONObject : Unsupported major.minor version 52.0
{code}
So, I inserted the above block into jbosstools-build-sites/aggregate/site/pom.xml (and fixed the version to be 0.22.1-SNAPSHOT), then:
{code}
$➔ mvn --version
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400)
Maven home: /opt/maven3
Java version: 1.8.0, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.17.4-200.fc20.x86_64", arch: "amd64", family: "unix"
{code}
{code}
$➔ mvn clean install -DtychoVersion=0.22.0 -DBUILD_ID=666 -DJOB_NAME=jbosstools-build-sites.aggregate.site_master -DHUDSON_SLAVE=dev69 -DRELEASE=no
{code}
----
And here are the results::
{code:title=aggregate/site/target/fullSite/all/repo/buildInfo.json}{
"upstream": {},
"properties": {
"BUILD_NUMBER": "666",
"RELEASE": "no",
"JOB_NAME": "jbosstools-build-sites.aggregate.site_master",
"HUDSON_SLAVE": "dev69"
},
"timestamp": 1419266314705,
"revision": {
"HEAD": "89898db85f9e38972360c42782247f0e2b7304b0",
"knownReferences": [{
"ref": "JBIDE-18869",
"name": "nickboldt",
"url": "git@github.com:nickboldt/jbosstools-build-sites.git"
}]
}
}{code}
{code:title=aggregate/site/target/fullSite/logs/GIT_REVISION.txt}
#Mon Dec 22 11:21:56 EST 2014
git@github.com\:nickboldt/jbosstools-build-sites.git\:JBIDE-18869=89898db85f9e38972360c42782247f0e2b7304b0
HEAD=89898db85f9e38972360c42782247f0e2b7304b0
{code}
{code:title=aggregate/site/target/fullSite/logs/build.properties}
BUILD_ALIAS=null
JOB_NAME=jbosstools-build-sites.aggregate.site_master
BUILD_NUMBER=666
BUILD_ID=null
HUDSON_SLAVE=dev69
RELEASE=no
ZIPSUFFIX=null
TARGET_PLATFORM_VERSION=null
TARGET_PLATFORM_VERSION_MAXIMUM=null
{code}
----
Now, some questions:
* *{color:red}QUESTION{color}* Should there be something in upstream?
* *{color:red}QUESTION{color}* What about details about the OS & JDK version?
* *{color:red}QUESTION{color}* Why are *TARGET_PLATFORM_VERSION*, *TARGET_PLATFORM_VERSION_MAXIMUM*, *BUILD_ALIAS* and *BUILD_ID* not resolved? The first 3 of those are from maven variables in the parent pom (if not set commandline), and BUILD_ID is a timestamp that could be the same as the one placed in GIT_REVISION.txt
* *{color:red}QUESTION{color}* Why is *WORKSPACE* not listed, and resolved to `pwd` ?
_This is often useful when builds fail to figure out where files have been created on a slave's filesystem, because they don't all use the same workspace path convention. And while you CAN browse the workspace within Jenkins, sometimes it's more efficient to do so over ssh._
* *{color:red}QUESTION{color}* Can you also generate an ALL_VERSIONS.txt for aggregate builds? Or does that only happen when the mojo detects there are upstream projects? If so, how do I tell the mojo that there are upstream projects when building locally?
> Attach metadata during assembly instead of publish time
> -------------------------------------------------------
>
> Key: JBIDE-15135
> URL: https://issues.jboss.org/browse/JBIDE-15135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.x
>
>
> In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site.
> Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months