[JBoss JIRA] (JBIDE-24789) Find a way to avoid freeze of master for several days
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24789?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24789:
-----------------------------------------
personally, i try to avoid to work on weekend, so it is 12 days for commit and 3 days for accumulation of PRs, writing doc/N&N and not preparing the forthcoming sprint as we are in Kanban.
And for this release, it is not 3 days but a week, so 10 days of commit and 5 days of accumulations.
So for each version of 4 sprints, it is 22 days of commit and 8 days of freeze, it means more than 30% of the time frozen :(
it also means that we always need to check: are we frozen? are we not frozen? ; I already merged a PR during previous freeze just because I forgot it was code freeze and realized half a day later.
> Find a way to avoid freeze of master for several days
> -----------------------------------------------------
>
> Key: JBIDE-24789
> URL: https://issues.jboss.org/browse/JBIDE-24789
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
>
> Currently, for each milestone, final release, the master branch is frozen for several days which is decreasing productivity and increase risk at the end of code freeze (as everybody wants to merge a lot of PRs at the same time)
> it would be nice to find a way to avoid the freeze on the master branch.
> Proposal:
> - create a branch for each milestone/release:
> -- it allows to continue working on master
> -- it allows to provide blocker/critical fix if needed on the branch
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24789) Find a way to avoid freeze of master for several days
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24789?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-24789 at 8/2/17 9:21 AM:
-----------------------------------------------------------------
personally, i try to avoid to work on weekend, so it is 12 days for commit and 3 days for accumulation of PRs, writing doc/N&N and not preparing the forthcoming sprint as we (Fuse Tolling) are in Kanban.
And for this release, it is not 3 days but a week, so 10 days of commit and 5 days of accumulations.
So for each version of 4 sprints, it is 22 days of commit and 8 days of freeze, it means more than 30% of the time frozen :(
it also means that we always need to check: are we frozen? are we not frozen? ; I already merged a PR during previous freeze just because I forgot it was code freeze and realized half a day later.
was (Author: aurelien.pupier):
personally, i try to avoid to work on weekend, so it is 12 days for commit and 3 days for accumulation of PRs, writing doc/N&N and not preparing the forthcoming sprint as we are in Kanban.
And for this release, it is not 3 days but a week, so 10 days of commit and 5 days of accumulations.
So for each version of 4 sprints, it is 22 days of commit and 8 days of freeze, it means more than 30% of the time frozen :(
it also means that we always need to check: are we frozen? are we not frozen? ; I already merged a PR during previous freeze just because I forgot it was code freeze and realized half a day later.
> Find a way to avoid freeze of master for several days
> -----------------------------------------------------
>
> Key: JBIDE-24789
> URL: https://issues.jboss.org/browse/JBIDE-24789
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
>
> Currently, for each milestone, final release, the master branch is frozen for several days which is decreasing productivity and increase risk at the end of code freeze (as everybody wants to merge a lot of PRs at the same time)
> it would be nice to find a way to avoid the freeze on the master branch.
> Proposal:
> - create a branch for each milestone/release:
> -- it allows to continue working on master
> -- it allows to provide blocker/critical fix if needed on the branch
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24789) Find a way to avoid freeze of master for several days
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24789?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24789:
------------------------------------
You're asking for the exact process we've used for the last year, which we decided was unnecessary overhead. You can't got 3 days without committing to master? Each sprint is 21 days -- this gives you 18 days for commits and 3 days for accumulation of PRs, writing doc/N&N, and preparing for the forthcoming sprint.
> Find a way to avoid freeze of master for several days
> -----------------------------------------------------
>
> Key: JBIDE-24789
> URL: https://issues.jboss.org/browse/JBIDE-24789
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
>
> Currently, for each milestone, final release, the master branch is frozen for several days which is decreasing productivity and increase risk at the end of code freeze (as everybody wants to merge a lot of PRs at the same time)
> it would be nice to find a way to avoid the freeze on the master branch.
> Proposal:
> - create a branch for each milestone/release:
> -- it allows to continue working on master
> -- it allows to provide blocker/critical fix if needed on the branch
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24643) NoStackTrace in StandardFileSystemPublishController.markModulePublished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24643?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24643:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> NoStackTrace in StandardFileSystemPublishController.markModulePublished
> -----------------------------------------------------------------------
>
> Key: JBIDE-24643
> URL: https://issues.jboss.org/browse/JBIDE-24643
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to delete module
> com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.markModulePublished(StandardFileSystemPublishController.java:584)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.removeModule(StandardFileSystemPublishController.java:482)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.WildFlyFileSystemPublishController.removeModule(WildFlyFileSystemPublishController.java:36)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:332)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> The reporter(s) left the following comment(s):
> --- Aurélien Pupier wrote on a317: ---
> I created an openShift Server Adapter for a FIS project
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.9.0.v20170322-0013 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.1.v20161107-2032 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 |
> | org.eclipse.jdt.debug | 3.10.0.v20160418-1524 | 3.10.1.v20160811-0441 |
> | org.eclipse.jface | 3.12.1.v20160923-1528 | 3.12.1.v20160923-1528 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.core.ui | 1.7.1.20161104-1805 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.wtp | 1.3.1.20160831-1005 | 1.3.1.20160831-1005 |
> | org.eclipse.m2e.wtp.overlay | 1.3.0.20160530-2310 | 1.3.2.20161026-1738 |
> | org.eclipse.swt | 3.105.2.v20161122-0613 | 3.105.2.v20161122-0613 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132253 | 1.10.0.v201705172051 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.ide.eclipse.as.ui | 3.2.3.v20170123-1748 | 3.2.3.v20170123-1748 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.1.v20160711-1757 | 3.3.0.v20170606-1714 |
> | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.jst.web.kb | 3.8.3.v20161214-1634 | 3.8.3.v20161214-1634 |
> | org.jboss.tools.openshift.core | 3.3.3.v20170405-1252 | 3.3.3.v20170405-1252 |
> Operating Systems:
> | Linux | 2.6.32.13 | 4.11.7 |
> | MacOSX | 10.10.5 | 10.12.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/57a218b3e4b0fe642b1... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBDS-4442) Central page does not work on Fedora 26 if package webkitgtk3 is not installed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4442?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4442:
-----------------------------
Fix Version/s: 11.x
(was: 11.0.0.GA)
> Central page does not work on Fedora 26 if package webkitgtk3 is not installed
> ------------------------------------------------------------------------------
>
> Key: JBDS-4442
> URL: https://issues.jboss.org/browse/JBDS-4442
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 11.0.0.AM1
> Environment: Fedora 26 Alpha
> Red Hat JBoss Developer Studio
> Version: 11.0.0.AM1
> Build id: AM1-v20170606-1759-B247
> Build date: 20170606-1759
> Reporter: Josef Kopriva
> Assignee: Supriya Bharadwaj
> Fix For: 11.x
>
>
> After fresh installation of F26 and Devstudio central shows error message
> {code:java}
> org.eclipse.swt.SWTException: An exception was raised in JavaScript
> at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273)
> at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
> at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175)
> at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163)
> at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077)
> at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614)
> at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:104)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5434)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437)
> at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425)
> at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4492)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4105)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months