[JBoss JIRA] (JBDS-3969) Run istanbul coverage with gulp for unit-tests
by Denis Golovin (JIRA)
Denis Golovin created JBDS-3969:
-----------------------------------
Summary: Run istanbul coverage with gulp for unit-tests
Key: JBDS-3969
URL: https://issues.jboss.org/browse/JBDS-3969
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: platform-installer
Affects Versions: 10.1.0.AM2
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 10.1.0.AM3
Current coverage implementation us running with:
{code}gulp create-electron-symlink
gulp test
npm run cover{code}
Last command generates summary on console and report in ./coverage folder.
Would be good to have it always running during just.
{code}gulp test{code}
I had several attempts to get this done with various modules, but result is always %100 coverage with 0 covered files.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ERT-350) Add label filtering in Docker Containers view [EBZ#498166]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-350:
---------------------------------------
Summary: Add label filtering in Docker Containers view [EBZ#498166]
Key: ERT-350
URL: https://issues.jboss.org/browse/ERT-350
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.1 (4.6)
With label support added for filtering Containers, add a filtering element to the Docker Containers View.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22756) Connection: varioius weirdness in token/password
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22756?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22756:
-------------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.1.AM2)
> Connection: varioius weirdness in token/password
> -------------------------------------------------
>
> Key: JBIDE-22756
> URL: https://issues.jboss.org/browse/JBIDE-22756
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Andre Dietisheim
> Labels: connection
> Fix For: 4.4.1.AM3
>
>
> The lifecycle of the token is rather weird and needs a consistent logic:
> When connecting via wizard the token is set in the connection wizard:
> {code:title=ConnectionWizardPageModel#connect}
> ...
> try {
> IConnection connection = createConnection(connectionFactory, connectionAuthenticationProvider);
> ...
> {code}
> {code:title=ConnectionWizardPageModel#createConnection}
> ...
> if (authProvider != null) {
> authProvider.update(connection); // sets the token
> }
> ...
> {code}
> {code:title=BearTokenAuthenticationProvider#update}
> ...
> connection.setAuthScheme(IAuthorizationContext.AUTHSCHEME_OAUTH);
> connection.setToken(tokenObservable.getValue());
> connection.setRememberToken(rememberTokenObservable.getValue());
> ...
> {code}
> {code:title=Connection#connect}
> if(authorize()) {
> ...
> {code}
> {code:title=Connection#authorized}
> ...
> if (context.isAuthorized()) {
> String username = context.getUser().getName();
> String token = context.getToken();
> updateAuthorized(username, token);
> } else {
> ...
> {code}
> The token is then fetched from client and set to the connection
> {code:title=Connection#updateAuthorized}
> setToken(token);
> ...
> {code}
> and the password is cleared
> {code:Connectoin#savePasswordOrToken}
> } else if (IAuthorizationContext.AUTHSCHEME_OAUTH.equals(getAuthScheme())){
> boolean success = saveOrClear(SECURE_STORAGE_TOKEN_KEY, this.token, isRememberToken());
> if(success) {
> //Avoid second secure storage prompt.
> //Token is stored, password should be cleared.
> clearPassword();
> {code}
> I suspect the aim here is to clear existing password in secure storage if the user is switching password->token based auth (and vice versa)
> The opposite is then not fully congruent. The token is only cleared in secure storage, not in Connection instance var
> {code:title=Connection#savePasswordOrToken}
> if (IAuthorizationContext.AUTHSCHEME_BASIC.equals(getAuthScheme())) {
> boolean success = saveOrClear(SECURE_STORAGE_PASSWORD_KEY, this.password, isRememberPassword());
> if (success) {
> //Avoid second secure storage prompt.
> // Password is stored, token should be cleared.
> clearToken();
> }
> {code:Connection#clearToken}
> // dont clear the token instance var: JBIDE-22594
> setRememberToken(false);
> saveOrClear(SECURE_STORAGE_TOKEN_KEY, null, false);
> {code}
> I suspect that we should only clear in secure storage, not in the Connection instance as we see in JBIDE-22594 (for the opposite case where we dont clear the token in the Connection instance). But then one has to keep in mind that all auth is token based. Even if you auth via password initially, the auth is then switched to token based once the authorization succeeded and we got a token:
> {code:title=Connection#updateAuthorized}
> setToken(token);
> if (IAuthorizationContext.AUTHSCHEME_OAUTH.equalsIgnoreCase(getAuthScheme())) {
> setUsername(username);
> }
> // force auth strategy to token if authorized
> TokenAuthorizationStrategy tokenStrategy = new TokenAuthorizationStrategy(token, username);
> client.setAuthorizationStrategy(tokenStrategy);
> {code}
> Another issue is that the connection and the auth schemeare both stored in different classes. The connection is stored via
> {code:title=ConnectionPersistency#persist}
> preferences.saveConnections(connections.keySet().toArray(new String[] {}));
> ...
> {code}
> while the auth scheme is stored in Connection#saveAuthSchemePreference:
> {code:title=Connection#connect}
> saveAuthSchemePreference();
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22760) Cannot install content from Central, connectors not available:
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22760?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22760.
------------------------------
Resolution: Done
Yes, this is a dupe. Sorry about that!
> Cannot install content from Central, connectors not available:
> --------------------------------------------------------------
>
> Key: JBIDE-22760
> URL: https://issues.jboss.org/browse/JBIDE-22760
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite
> Affects Versions: 4.4.1.AM2
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: Screen Shot 2016-07-19 at 12.24.16 PM.png, Screen Shot 2016-07-19 at 12.24.29 PM.png
>
>
> {code}
> Problems occurred while performing installation: The following connectors are not available: JBoss Seam Tools (id=org.jboss.tools.runtime.seam.detector.feature.feature.group, org.jboss.tools.seam.feature.feature.group, org.jboss.tools.maven.seam.feature.feature.group, org.jboss.tools.project.examples.seam.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Maven Portlet Configurator (id=org.jboss.tools.maven.portlet.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), AngularJS for Web Tools (id=org.jboss.tools.jst.angularjs.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Portlet Tools (id=org.jboss.tools.portlet.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), Mylyn Issue Tracker Connectors (id=org.jboss.tools.common.mylyn.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Maven Seam Configurator (id=org.jboss.tools.maven.seam.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Hybrid Mobile Tools + CordovaSim (id=org.jboss.tools.aerogear.easymport.feature.feature.group, org.jboss.tools.aerogear.thym.feature.feature.group, org.jboss.tools.cordovasim.feature.feature.group, org.jboss.tools.browsersim.feature.feature.group, org.jboss.tools.livereload.feature.feature.group, org.jboss.tools.jst.angularjs.feature.feature.group, org.jboss.tools.feedhenry.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Tools Maven Packaging Configurator (id=org.jboss.tools.maven.jbosspackaging.feature.feature.group, org.jboss.ide.eclipse.as.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...)
> The following connectors are not available: JBoss Seam Tools (id=org.jboss.tools.runtime.seam.detector.feature.feature.group, org.jboss.tools.seam.feature.feature.group, org.jboss.tools.maven.seam.feature.feature.group, org.jboss.tools.project.examples.seam.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Maven Portlet Configurator (id=org.jboss.tools.maven.portlet.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), AngularJS for Web Tools (id=org.jboss.tools.jst.angularjs.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Portlet Tools (id=org.jboss.tools.portlet.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), Mylyn Issue Tracker Connectors (id=org.jboss.tools.common.mylyn.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Maven Seam Configurator (id=org.jboss.tools.maven.seam.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Hybrid Mobile Tools + CordovaSim (id=org.jboss.tools.aerogear.easymport.feature.feature.group, org.jboss.tools.aerogear.thym.feature.feature.group, org.jboss.tools.cordovasim.feature.feature.group, org.jboss.tools.browsersim.feature.feature.group, org.jboss.tools.livereload.feature.feature.group, org.jboss.tools.jst.angularjs.feature.feature.group, org.jboss.tools.feedhenry.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...), JBoss Tools Maven Packaging Configurator (id=org.jboss.tools.maven.jbosspackaging.feature.feature.group, org.jboss.ide.eclipse.as.feature.feature.group, site=https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discov...)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22757:
------------------------------------
Scripts which rely on BUILD_ID value looking like yyyy-mm-dd_HH-MM-SS:
In jbosstools-build-ci:
./publish/publish.sh (deprecated in favour of rsync.sh)
./publish/rsync.sh
./util/cleanup/jbosstools-cleanup.sh
./publish/build-jbosstools-component.sh
./buildchow/templates/*.yaml
Elsewhere:
./jbosstools-locus/site/pom.xml
./reddeer/site/pom.xml
./jbosstools-versionwatch/run.jenkins.job.sh
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
./jbosstools-integration-stack/scripts/build.xml
./jbosstools-integration-stack/jbosstools/README.adoc
./jbosstools-integration-stack/*/*/*/pom.xml
./jbosstools-build-sites/aggregate/site/pom.xml
./jbosstools-build-sites/aggregate/earlyaccess-site/pom.xml
./jbosstools-build-sites/aggregate/coretests-site/pom.xml
./jbosstools-build-sites/aggregate/central-site/pom.xml
./jbosstools-browsersim/products/browsersim-standalone/pom.xml
./jbdevstudio-product/results/pom.xml
and ... all the jbosstools Jenkins jobs which pass -DBUILD_ID=${BUILD_ID} to maven.
> jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
> -----------------------------------------------------------------
>
> Key: JBIDE-22757
> URL: https://issues.jboss.org/browse/JBIDE-22757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: buildID-broken.png
>
>
> Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
> [1] https://issues.jenkins-ci.org/browse/JENKINS-26520
> [2] https://issues.jenkins-ci.org/browse/JENKINS-26626
> So instead of timestamped build folders, we're seeing things like this:
> !buildID-broken.png|thumbnail!
> Workaround until fixed in Jenkins:
> {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
> Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22757 at 7/19/16 1:30 PM:
-------------------------------------------------------------
Scripts which rely on BUILD_ID value looking like yyyy-mm-dd_HH-MM-SS:
In jbosstools-build-ci:
./publish/publish.sh (deprecated in favour of rsync.sh)
./publish/rsync.sh
./util/cleanup/jbosstools-cleanup.sh
./publish/build-jbosstools-component.sh
./buildchow/templates/*.yaml
Elsewhere:
./jbosstools-locus/site/pom.xml
./reddeer/site/pom.xml
./jbosstools-versionwatch/run.jenkins.job.sh
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
./jbosstools-integration-stack/scripts/build.xml
./jbosstools-integration-stack/jbosstools/README.adoc
./jbosstools-integration-stack/\*/\*/\*/pom.xml
./jbosstools-build-sites/aggregate/site/pom.xml
./jbosstools-build-sites/aggregate/earlyaccess-site/pom.xml
./jbosstools-build-sites/aggregate/coretests-site/pom.xml
./jbosstools-build-sites/aggregate/central-site/pom.xml
./jbosstools-browsersim/products/browsersim-standalone/pom.xml
./jbdevstudio-product/results/pom.xml
and ... all the jbosstools Jenkins jobs which pass -DBUILD_ID=$\{BUILD_ID} to maven.
was (Author: nickboldt):
Scripts which rely on BUILD_ID value looking like yyyy-mm-dd_HH-MM-SS:
In jbosstools-build-ci:
./publish/publish.sh (deprecated in favour of rsync.sh)
./publish/rsync.sh
./util/cleanup/jbosstools-cleanup.sh
./publish/build-jbosstools-component.sh
./buildchow/templates/*.yaml
Elsewhere:
./jbosstools-locus/site/pom.xml
./reddeer/site/pom.xml
./jbosstools-versionwatch/run.jenkins.job.sh
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
./jbosstools-integration-stack/scripts/build.xml
./jbosstools-integration-stack/jbosstools/README.adoc
./jbosstools-integration-stack/\*/\*/\*/pom.xml
./jbosstools-build-sites/aggregate/site/pom.xml
./jbosstools-build-sites/aggregate/earlyaccess-site/pom.xml
./jbosstools-build-sites/aggregate/coretests-site/pom.xml
./jbosstools-build-sites/aggregate/central-site/pom.xml
./jbosstools-browsersim/products/browsersim-standalone/pom.xml
./jbdevstudio-product/results/pom.xml
and ... all the jbosstools Jenkins jobs which pass -DBUILD_ID=${BUILD_ID} to maven.
> jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
> -----------------------------------------------------------------
>
> Key: JBIDE-22757
> URL: https://issues.jboss.org/browse/JBIDE-22757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: buildID-broken.png
>
>
> Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
> [1] https://issues.jenkins-ci.org/browse/JENKINS-26520
> [2] https://issues.jenkins-ci.org/browse/JENKINS-26626
> So instead of timestamped build folders, we're seeing things like this:
> !buildID-broken.png|thumbnail!
> Workaround until fixed in Jenkins:
> {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
> Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22757 at 7/19/16 1:30 PM:
-------------------------------------------------------------
Scripts which rely on BUILD_ID value looking like yyyy-mm-dd_HH-MM-SS:
In jbosstools-build-ci:
./publish/publish.sh (deprecated in favour of rsync.sh)
./publish/rsync.sh
./util/cleanup/jbosstools-cleanup.sh
./publish/build-jbosstools-component.sh
./buildchow/templates/*.yaml
Elsewhere:
./jbosstools-locus/site/pom.xml
./reddeer/site/pom.xml
./jbosstools-versionwatch/run.jenkins.job.sh
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
./jbosstools-integration-stack/scripts/build.xml
./jbosstools-integration-stack/jbosstools/README.adoc
./jbosstools-integration-stack/\*/\*/\*/pom.xml
./jbosstools-build-sites/aggregate/site/pom.xml
./jbosstools-build-sites/aggregate/earlyaccess-site/pom.xml
./jbosstools-build-sites/aggregate/coretests-site/pom.xml
./jbosstools-build-sites/aggregate/central-site/pom.xml
./jbosstools-browsersim/products/browsersim-standalone/pom.xml
./jbdevstudio-product/results/pom.xml
and ... all the jbosstools Jenkins jobs which pass -DBUILD_ID=${BUILD_ID} to maven.
was (Author: nickboldt):
Scripts which rely on BUILD_ID value looking like yyyy-mm-dd_HH-MM-SS:
In jbosstools-build-ci:
./publish/publish.sh (deprecated in favour of rsync.sh)
./publish/rsync.sh
./util/cleanup/jbosstools-cleanup.sh
./publish/build-jbosstools-component.sh
./buildchow/templates/*.yaml
Elsewhere:
./jbosstools-locus/site/pom.xml
./reddeer/site/pom.xml
./jbosstools-versionwatch/run.jenkins.job.sh
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo.java
./jbosstools-maven-plugins/tycho-plugins/repository-utils/src/main/java/org/jboss/tools/tycho/sitegenerator/CreateFullSiteMojo.java
./jbosstools-integration-stack/scripts/build.xml
./jbosstools-integration-stack/jbosstools/README.adoc
./jbosstools-integration-stack/*/*/*/pom.xml
./jbosstools-build-sites/aggregate/site/pom.xml
./jbosstools-build-sites/aggregate/earlyaccess-site/pom.xml
./jbosstools-build-sites/aggregate/coretests-site/pom.xml
./jbosstools-build-sites/aggregate/central-site/pom.xml
./jbosstools-browsersim/products/browsersim-standalone/pom.xml
./jbdevstudio-product/results/pom.xml
and ... all the jbosstools Jenkins jobs which pass -DBUILD_ID=${BUILD_ID} to maven.
> jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
> -----------------------------------------------------------------
>
> Key: JBIDE-22757
> URL: https://issues.jboss.org/browse/JBIDE-22757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: buildID-broken.png
>
>
> Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
> [1] https://issues.jenkins-ci.org/browse/JENKINS-26520
> [2] https://issues.jenkins-ci.org/browse/JENKINS-26626
> So instead of timestamped build folders, we're seeing things like this:
> !buildID-broken.png|thumbnail!
> Workaround until fixed in Jenkins:
> {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
> Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3892) Toolbar items/icons disappear when scaled in size
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3892?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3892:
--------------------------------
Fix Version/s: 10.x
(was: 10.1.0.AM1)
> Toolbar items/icons disappear when scaled in size
> -------------------------------------------------
>
> Key: JBDS-3892
> URL: https://issues.jboss.org/browse/JBDS-3892
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 10.0.0.Alpha1
> Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-bundle-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: studio.png
>
>
> It installs OK, it starts up and looks like this:
> !studio.png|thumbnail!
> Lots of widgets not loaded at all, the start icon is default eclipse one, sometimes it refuses to start at all until a clean workspace is selected.
> And still, no errors in the log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3892) Toolbar items/icons disappear when scaled in size
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3892?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3892:
-----------------------------------
Assignee: Alexey Kazakov (was: Denis Golovin)
> Toolbar items/icons disappear when scaled in size
> -------------------------------------------------
>
> Key: JBDS-3892
> URL: https://issues.jboss.org/browse/JBDS-3892
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 10.0.0.Alpha1
> Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-bundle-installer
> Reporter: Jan Richter
> Assignee: Alexey Kazakov
> Fix For: 10.x
>
> Attachments: studio.png
>
>
> It installs OK, it starts up and looks like this:
> !studio.png|thumbnail!
> Lots of widgets not loaded at all, the start icon is default eclipse one, sometimes it refuses to start at all until a clean workspace is selected.
> And still, no errors in the log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22757:
------------------------------------
Yes, it's a blocker. Timestamped folders are composited automatically as /latest/ folders, eg., [1], which are then used to create the JBT aggregate [2]. The JBT aggregate compares the version of source in the built binaries to the version in github, and if there's a disconnect, the build fails [3]. This check is designed to prevent accidentally including the wrong sources in the source zip.
[1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-fre... http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-fre...
[2] jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Ma...
[3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.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-freemarker.json
[ERROR] contains cf8c8ba5b9c79bf5d72920d913e372befe1c6bbf, but upstream jbosstools-freemarker project's MANIFEST.MF has Eclipse-SourceReferences
[ERROR] commitId 1048bbb0ef4ef287a6250d5e75cc86998158a102.
[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.
{code}
The property is wrapped because of this [4], but the bug may no longer be an issue with Maven 3.x.
[4] https://stackoverflow.com/questions/13228472/how-to-acces-maven-build-tim...
> jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
> -----------------------------------------------------------------
>
> Key: JBIDE-22757
> URL: https://issues.jboss.org/browse/JBIDE-22757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: buildID-broken.png
>
>
> Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
> [1] https://issues.jenkins-ci.org/browse/JENKINS-26520
> [2] https://issues.jenkins-ci.org/browse/JENKINS-26626
> So instead of timestamped build folders, we're seeing things like this:
> !buildID-broken.png|thumbnail!
> Workaround until fixed in Jenkins:
> {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
> Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months