[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
SJ Cox commented on JBDS-3605:
------------------------------
[~nickboldt] Attached are the revised icons at the correct dimensions. Let me know if these work for you, thanks!
[^RevisedIcons.zip]
> 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, RevisedIcons.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] (JBTIS-607) Validate IS URLs
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-607?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-607.
----------------------------
Fix Version/s: 9.0.1.GA
Resolution: Done
Added test infrastructure to validate IS specific p2 repos and update sites.
> Validate IS URLs
> ----------------
>
> Key: JBTIS-607
> URL: https://issues.jboss.org/browse/JBTIS-607
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 9.0.0.Beta1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
>
> There exists staging, integration, development and stable URLs in support of p2 installations as well as JBoss Central. We need an automated way of validating that a defined list of URLs is consistent.
--
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:
------------------------------------
Well, for the case of the server job, I can only see artifacts for the current build, plus the two successful blue jobs. It's unclear why artifacts were not stored for any of the yellow or red jobs, since "Archive artifacts only if build is successful" is unchecked.
Re: your comment about not wanting a "Swiss Army knife" solution for both PRs and commits, to me it seems easier to have one job config that works for both.
Either you...
* run 3 steps
** (build commit,
** deploy update site onto download.jboss.org (with automated cleanup) in a /builds/ folder,
** run tests)
or you...
* run 3 steps
** (build PR,
** deploy PR update site onto download.jboss.org (with automated cleanup) in a /pulls/ folder,
** run tests)
Why make the config different for a PR vs. a commit, when both uscases can do the same steps and thus keep things simpler?
> 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