[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3605:
-----------------------------
Attachment: edit-eap-icon-in-ds10-installer.png
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, Additional_RHDS_Branding.zip, edit-eap-icon-in-ds10-installer.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, new-eap-icon-in-ds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3605:
-----------------------------
Attachment: new-eap-icon-in-ds10-installer.png
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, Additional_RHDS_Branding.zip, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, new-eap-icon-in-ds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21657:
----------------------------------------
Most project using Gerrit validations job at Eclpse.org do use the repo URL under Jenkins for testing, and there actually have been no complaint because of that that I'm aware of. Jenkins can be configured to keep the last N builds or to keep builds for N days. It's pretty sufficient.
About need to aggregate PR builds, or the issue of too many incoming PRs or even performance of the download of PR builds, I believe this is way too early to consider those. By adding them to the scope right now, without a clear need for them, we add complexity where it's probably not necessary and make it more complex and longer to implement.
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21657:
------------------------------------
I disagree. We will potentially need a way to aggregate builds from multiple PRs across multiple projects.
We can't (easily) do that if we're fetching bits archived inside Jenkins, since the bits are behind the VPN.
Surely having the bits on a centralized, public, download server is better (faster downloads, more accessible) than trying to do behind the VPN?
Does Jenkins archive zips for multiple PR builds, or just the latest artifacts?
I see artifacts here:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
but not here:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
What if there's a lot of PRs coming in and Jenkins deletes the old PR builds?
We can retain artifacts longer on download.jboss.org than in MW Jenkins (and have different retention rules) if we split the concerns here:
* one server for building/deploying/testing, and
* one for storage of the output.
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22311) Adopt Tycho 0.25 for JBT and downstream projects
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22311?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22311:
------------------------------------
Affected projects include fuseide, jbosstools-build (parent pom), jbosstools-integration-stack, jbosstools-locus, and reddeer.
All JBT projects downstream of the parent pom are also affected by this change.
{code}
$➔ find.sh . pom.xml 0.23
** [1] ./fuseide/pom.xml **
45- <!-- Tycho versions -->
46- <jboss-tycho-version>0.22.1-SNAPSHOT</jboss-tycho-version>
47: <tychoVersion>0.23.0</tychoVersion>
48- <tychoExtrasVersion>${tychoVersion}</tychoExtrasVersion>
49-
** [2] ./jbosstools-build/parent/pom.xml **
28- <tychoVersion>0.24.0</tychoVersion>
29- <tychoExtrasVersion>${tychoVersion}</tychoExtrasVersion>
30: <jbossTychoPluginsVersion>0.23.3</jbossTychoPluginsVersion>
31- <jbosstoolsRelengPublishVersion>4.4.0.Alpha1-SNAPSHOT</jbosstoolsRelengPublishVersion>
32- <memoryOptions1>-Xms512m -Xmx1024m -XX:PermSize=256m</memoryOptions1>
** [3] ./jbosstools-integration-stack/devstudio/pom.xml **
34- <IS_TP_VERSION>4.3.1-SNAPSHOT</IS_TP_VERSION>
35- <JBDS_INSTALLER>https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d...</JBDS_INSTALLER>
36: <tycho-version>0.23.1</tycho-version>
37: <jboss-tycho-version>0.23.3-SNAPSHOT</jboss-tycho-version>
38-
39- <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
** [4] ./jbosstools-integration-stack/jbosstools/pom.xml **
32- <VERSION>4.3.0.Beta1</VERSION>
33- <IS_TP_VERSION>4.3.1-SNAPSHOT</IS_TP_VERSION>
34: <tycho-version>0.23.1</tycho-version>
35: <jboss-tycho-version>0.23.1</jboss-tycho-version>
36- <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
37- <target.eclipse.version>4.5 (Mars) or <a href="https://www.jboss.org/products/devstudio/overview/">JBoss Developer Studio 9</a></target.eclipse.version>
** [5] ./jbosstools-locus/pom.xml **
10- <tychoVersion>0.24.0</tychoVersion>
11- <tychoExtrasVersion>${tychoVersion}</tychoExtrasVersion>
12: <jbossTychoPluginsVersion>0.23.3-SNAPSHOT</jbossTychoPluginsVersion>
13- <BUILD_ALIAS>SNAPSHOT</BUILD_ALIAS> <!-- move to Final when releasing -->
14- <targetEclipseVersion>4.5 (Mars)</targetEclipseVersion>
** [6] ./reddeer/pom.xml **
10-
11- <properties>
12: <!-- when you're ready to move to building with JDK 8, you can move up to Tycho 0.23.1 -->
13- <tycho-version>0.22.0</tycho-version>
14- <tychoExtrasVersion>${tycho-version}</tychoExtrasVersion>
15: <jbossTychoPluginsVersion>0.23.1</jbossTychoPluginsVersion>
16- <eclipse-target-site>http://download.eclipse.org/releases/neon</eclipse-target-site>
17- <swtbot-update-site>http://download.eclipse.org/technology/swtbot/releases/2.2.1</swtbot-update-site>
{code}
> Adopt Tycho 0.25 for JBT and downstream projects
> ------------------------------------------------
>
> Key: JBIDE-22311
> URL: https://issues.jboss.org/browse/JBIDE-22311
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
>
> In order to take advantage of several improvements in Tycho ( https://wiki.eclipse.org/Tycho/Release_Notes/0.25 ), we should consider adopting its 0.25 release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21105) Deprecate BIRT
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21105.
------------------------------
I've verified that your fixes were (almost) the same as mine in the attached PRs, and fixed the one that was incomplete (#605).
Closing.
> Deprecate BIRT
> --------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
> *Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months