[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13671:
-------------------------------
Attachment: server-before-after-jgit-3-different-timestamps.png
server-before-after-jgit-4-different-timestamps-features.png
server-before-after-jgit-dirty-workspace-upversioned-features.png
server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png
More screenshots showing what happens after we move to jgit:
!server-before-after-jgit-3-different-timestamps.png|thumbnail!
!server-before-after-jgit-4-different-timestamps-features.png|thumbnail!
!server-before-after-jgit-dirty-workspace-upversioned-features.png|thumbnail!
!server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png|thumbnail!
> Replace build timestamp in qualifier by last-mod-timestamp from git
> -------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.1.AM1
>
> Attachments: arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, jbide13671-before-and-after.png, server-before-after-jgit-3-different-timestamps.png, server-before-after-jgit-4-different-timestamps-features.png, server-before-after-jgit-dirty-workspace-upversioned-features.png, server-before-after-jgit-dirty-workspace-upversioned-plugin-with-change.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13671 at 6/29/16 12:20 PM:
--------------------------------------------------------------
Using these two PRs [1], [2], here's what happens in Base when we switch to jgit:
!base-before-after-jgit.png|thumbnail!
[1] https://github.com/jbosstools/jbosstools-build/pull/223
[2] https://github.com/jbosstools/jbosstools-base/pull/514
And, here's some examples of what happens in Arquillian when comparing a clean jgit-based build with a dirty-workspace version of the same build, to show that even without committing changes, your LOCALLY built plugins/features will be correctly upversioned so you can do install tests.
!arq-dirty-workspace-compare1.png|thumbnail!
!arq-dirty-workspace-compare1.png|thumbnail!
!arq-dirty-workspace-compare3-bigger-change.png|thumbnail!
!arq-dirty-workspace-compare4-bigger-change.png|thumbnail!
was (Author: nickboldt):
Using these two PRs, here's what happens in Base when we switch to jgit:
!base-before-after-jgit.png|thumbnail!
And, here's some examples of what happens in Arquillian when comparing a clean jgit-based build with a dirty-workspace version of the same build, to show that even without committing changes, your LOCALLY built plugins/features will be correctly upversioned so you can do install tests.
!arq-dirty-workspace-compare1.png|thumbnail!
!arq-dirty-workspace-compare1.png|thumbnail!
!arq-dirty-workspace-compare3-bigger-change.png|thumbnail!
!arq-dirty-workspace-compare4-bigger-change.png|thumbnail!
> Replace build timestamp in qualifier by last-mod-timestamp from git
> -------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.1.AM1
>
> Attachments: arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13671:
-------------------------------
Attachment: base-before-after-jgit.png
arq-dirty-workspace-compare2.png
arq-dirty-workspace-compare1.png
arq-dirty-workspace-compare3-bigger-change.png
arq-dirty-workspace-compare4-bigger-change.png
Using these two PRs, here's what happens in Base when we switch to jgit:
!base-before-after-jgit.png|thumbnail!
And, here's some examples of what happens in Arquillian when comparing a clean jgit-based build with a dirty-workspace version of the same build, to show that even without committing changes, your LOCALLY built plugins/features will be correctly upversioned so you can do install tests.
!arq-dirty-workspace-compare1.png|thumbnail!
!arq-dirty-workspace-compare1.png|thumbnail!
!arq-dirty-workspace-compare3-bigger-change.png|thumbnail!
!arq-dirty-workspace-compare4-bigger-change.png|thumbnail!
> Replace build timestamp in qualifier by last-mod-timestamp from git
> -------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.1.AM1
>
> Attachments: arq-dirty-workspace-compare1.png, arq-dirty-workspace-compare2.png, arq-dirty-workspace-compare3-bigger-change.png, arq-dirty-workspace-compare4-bigger-change.png, base-before-after-jgit.png, jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22603:
------------------------------------
I think I managed to reproduce with two OS3 connections to CDK (admin + openshift-dev). Websocket start throwing connections
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22603:
-------------------------------
Sprint: devex #116 June 2016 (was: devex #117 July 2016)
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22677) rsync stuck on OSX
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22677?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22677:
-------------------------------------
Same issue with a node app:
{noformat}
Error while publishing server nodejs-example at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /Users/fbricon/Dev/workspaces/runtime-New_configuration/.metadata/.plugins/org.jboss.ide.eclipse.as.core/node@nodejs-example/deploy
Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@1ab68434 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@7c47993d did not terminate within 5 minutes.
{noformat}
Eventually, at some point, the rsync process finishes, well past that 5min mark.
> rsync stuck on OSX
> ------------------
>
> Key: JBIDE-22677
> URL: https://issues.jboss.org/browse/JBIDE-22677
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Priority: Blocker
>
> I deployed an eap app from the eap64-basic-s2i template, then created an openshift 3 server.
> On server startup, publishing fails to complete after 5 minutes and a thread dump shows rsync is still blocking in the background.
> {noformat}
> "pool-40-thread-1" #231 prio=5 os_prio=31 tid=0x00007f9a55dd0000 nid=0xeb9f runnable [0x000000013199a000]
> java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> - locked <0x00000007b3d45cb8> (a java.lang.UNIXProcess$ProcessPipeInputStream)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> - locked <0x00000007b3d49d50> (a java.io.InputStreamReader)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.fill(BufferedReader.java:161)
> at java.io.BufferedReader.readLine(BufferedReader.java:324)
> - locked <0x00000007b3d49d50> (a java.io.InputStreamReader)
> at java.io.BufferedReader.readLine(BufferedReader.java:389)
> at org.jboss.tools.openshift.core.server.RSync.lambda$0(RSync.java:152)
> at org.jboss.tools.openshift.core.server.RSync$$Lambda$181/1635081930.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> I'm deploying on CDK 2.1RC5
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-22680:
--------------------------------------
Summary: Create CI jobs running integration tests on incoming PRs
Key: JBIDE-22680
URL: https://issues.jboss.org/browse/JBIDE-22680
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build, qa
Reporter: Mickael Istria
Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months