[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-05-29 Thread Tommaso Teofili (JIRA)

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564553#comment-14564553
 ] 

Tommaso Teofili edited comment on OAK-2476 at 5/29/15 10:42 AM:


with the help of [~rombert] and [~mduerig] I've set up Jenkins to run builds 
for both trunk, branch 1.2 and branch 1.0, the notifications on oak-dev@ will 
contain the branch used for the build at hand, e.g. {noformat}[Oak branch 
origin/trunk] - Build failed ...{noformat}
Note that for that I've switched the SCM to be the mirrored Git at 
http://github.com/apache/jackrabbit-oak .


was (Author: teofili):
with the help of [~rombert] and [~mduerig] I've set up Jenkins to run builds 
for both trunk, branch 1.2 and branch 1.0, the notifications on oak-dev@ will 
contain the branch used for the build at hand, e.g. {noformat}[Oak branch 
origin/trunk] - Build failed ...{noformat}.

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
  Labels: CI, build, infrastructure
 Fix For: 1.3.1


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-05-26 Thread JIRA

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558981#comment-14558981
 ] 

Michael Dürig edited comment on OAK-2476 at 5/26/15 11:21 AM:
--

We should have the same matrices also for the 1.0 and 1.2 branches. [~teofili], 
would you have some time to spare on this?

cc [~rombert] re. the idea of putting a seed configuration into SCM, which 
could be used to spawn off individual matrices. 


was (Author: mduerig):
We should have the same matrices also for the 1.0 and 1.2 branches. [~teofili], 
would you have some time to spare on this?

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
  Labels: CI, build, infrastructure
 Fix For: 1.3.1


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-03-20 Thread JIRA

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14371236#comment-14371236
 ] 

Michael Dürig edited comment on OAK-2476 at 3/20/15 12:38 PM:
--

Still no new platform problems with [build 
30|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/30/]. 
* All windows builds errored. Presumable due to no disk space left. I've taken 
the Windows builds off line for now (via the combination filter) so it doesn't 
impact the test of the builds. Let's follow up separately re. Windows. 
* One test failure: 
{{org.apache.jackrabbit.oak.jcr.OrderableNodesTest.testAddNode}}. --I'll file 
an issue.-- See OAK-2655
* Still the problem with the {{geronimo-jta_1.0.1B_spec}} dependency. I'll 
create an BUILDS issue. 


was (Author: mduerig):
Still no new platform problems with [build 
30|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/30/]. 
* All windows builds errored. Presumable due to no disk space left. I've taken 
the Windows builds off line for now (via the combination filter) so it doesn't 
impact the test of the builds. Let's follow up separately re. Windows. 
* One test failure: 
{{org.apache.jackrabbit.oak.jcr.OrderableNodesTest.testAddNode}}. I'll file an 
issue. 
* Still the problem with the {{geronimo-jta_1.0.1B_spec}} dependency. I'll 
create an BUILDS issue. 

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
  Labels: CI, build, infrastructure
 Fix For: 1.2


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-03-17 Thread JIRA

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365119#comment-14365119
 ] 

Michael Dürig edited comment on OAK-2476 at 3/17/15 4:08 PM:
-

Many of the Windows builds now fail with

{code}
Action ended 6:18:02ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver 
aborted due to exception
hudson.AbortException
at hudson.tools.JDKInstaller.install(JDKInstaller.java:277)
at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:140)
at 
hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68)
at 
hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204)
at hudson.model.JDK.forNode(JDK.java:123)
at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:351)
at 
hudson.matrix.MatrixConfiguration.getEnvironment(MatrixConfiguration.java:94)
at hudson.model.Run.getEnvironment(Run.java:2216)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:885)
at 
hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:126)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
at hudson.model.Build$BuildExecution.post2(Build.java:182)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
at hudson.model.Run.execute(Run.java:1731)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Finished: FAILURE
{code}



was (Author: mduerig):
May of the Windows builds now fail with

{code}
Action ended 6:18:02ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver 
aborted due to exception
hudson.AbortException
at hudson.tools.JDKInstaller.install(JDKInstaller.java:277)
at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:140)
at 
hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68)
at 
hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107)
at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204)
at hudson.model.JDK.forNode(JDK.java:123)
at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:351)
at 
hudson.matrix.MatrixConfiguration.getEnvironment(MatrixConfiguration.java:94)
at hudson.model.Run.getEnvironment(Run.java:2216)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:885)
at 
hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:126)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
at hudson.model.Build$BuildExecution.post2(Build.java:182)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
at hudson.model.Run.execute(Run.java:1731)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Finished: FAILURE
{code}


 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
  Labels: CI, build, infrastructure
 Fix For: 1.2


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-03-16 Thread JIRA

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363076#comment-14363076
 ] 

Michael Dürig edited comment on OAK-2476 at 3/16/15 11:14 AM:
--

I see PermGen space error for the pedantic builds now [1]. Might this have to 
do with findbugs? Can we just increase the perm gen size for that build?

[1] 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/15/jdk=latest1.6,label=Ubuntu,nsfixtures=SEGMENT_MK,profile=pedantic/console


was (Author: mduerig):
I see PermGen space error for the pedantic builds now. Might this have to do 
with findbugs? Can we just increase the perm gen size for that build?

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
  Labels: CI, build, infrastructure
 Fix For: 1.2


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-03-12 Thread Tommaso Teofili (JIRA)

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358854#comment-14358854
 ] 

Tommaso Teofili edited comment on OAK-2476 at 3/12/15 3:53 PM:
---

I've had a couple of additional issues with Jenkins not being able to cope with 
parenthesis and commas in axis values, anyway the basic configuration should be 
ok.

For the record during the [currently running 
build|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/11/] at 
lest one job running on Windows failed because of the Jenkins slave disk being 
full, while the one(s) running on Ubuntu seem to be going ok.

Once the build configuration has proved to be ok, I'll remove the previously 
created Jenkins jobs (one for each JDK).


was (Author: teofili):
I've had a couple of additional issues with Jenkins not being able to cope with 
parenthesis and commas in axis values, anyway the basic configuration should be 
ok.

For the record during the [currently running 
build|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/11/] at 
lest one job running on Windows failed because of the Jenkins slave disk being 
full, while the one(s) running on Ubuntu seem to be going ok.

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
  Labels: CI, build, infrastructure
 Fix For: 1.1.8, 1.2


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-03-12 Thread Tommaso Teofili (JIRA)

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358854#comment-14358854
 ] 

Tommaso Teofili edited comment on OAK-2476 at 3/12/15 3:51 PM:
---

I've had a couple of additional issues with Jenkins not being able to cope with 
parenthesis and commas in axis values, anyway the basic configuration should be 
ok.

For the record during the [currently running 
build|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/11/] at 
lest one job running on Windows failed because of the Jenkins slave disk being 
full, while the one(s) running on Ubuntu seem to be going ok.


was (Author: teofili):
I've had a couple of additional issues with Jenkins not being able to couple 
with parenthesis and commas in axis values, anyway the basic configuration 
should be ok.

For the record during the [currently running 
build|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/11/] at 
lest one job running on Windows failed because of the Jenkins slave disk being 
full, while the one(s) running on Ubuntu seem to be going ok.

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
  Labels: CI, build, infrastructure
 Fix For: 1.1.8, 1.2


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-02-18 Thread JIRA

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14325608#comment-14325608
 ] 

Michael Dürig edited comment on OAK-2476 at 2/18/15 9:08 AM:
-

Maybe set it up as an matrix build? [~mirko] should be able to help here.

We should also run all fixtures instead of only the SegmentMK one. Optimally 
we'd have another dimension for fixtures in the build matrix. So the matrix 
dimensions would look like 

{code}
[java 6, java 7, java 8] x [linux, windows] x [DOCUMENT_MK, DOCUMENT_NS, 
SEGMENT_MK, DOCUMENT_RDB, MEMORY_NS]. 
{code}

[~edivad] knows about how about how to run the build against a specific 
fixture. 


was (Author: mduerig):
Maybe set it up as an matrix build? [~mirko] should be able to help here.

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Critical
 Fix For: 1.1.7


 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (OAK-2476) Move our CI to Jenkins

2015-02-04 Thread Tommaso Teofili (JIRA)

[ 
https://issues.apache.org/jira/browse/OAK-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305431#comment-14305431
 ] 

Tommaso Teofili edited comment on OAK-2476 at 2/4/15 4:23 PM:
--

We have now 3 different jobs:

- [Oak trunk java 6|https://builds.apache.org/job/Oak%20trunk%20java%206/]
- [Oak trunk java 7|https://builds.apache.org/job/Oak%20trunk%20java%207/]
- [Oak trunk java 8|https://builds.apache.org/job/Oak%20trunk%20java%208/]

they can execute on ubuntu or Windows, so we should have at least a good 
starting coverage.


was (Author: teofili):
I've created 3 different jobs:

- [Oak trunk java 6|https://builds.apache.org/job/Oak%20trunk%20java%206/]
- [Oak trunk java 7|https://builds.apache.org/job/Oak%20trunk%20java%207/]
- [Oak trunk java 8|https://builds.apache.org/job/Oak%20trunk%20java%208/]

they can execute on ubuntu or Windows, so we should have at least a good 
starting coverage.

 Move our CI to Jenkins
 --

 Key: OAK-2476
 URL: https://issues.apache.org/jira/browse/OAK-2476
 Project: Jackrabbit Oak
  Issue Type: Task
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili

 We should strive for stabilization of our CI setup, as of now we had Buildbot 
 and Travis.
 It seems ASF Jenkins can perform jobs on different environments (*nix, 
 Windows and others) so we can evaluate that and check if it better address 
 our needs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)