Hi all,
to help with builds (or better to ensure code is buildable, at least
one time per day), what do you think to add a new issue for Jenkins
builds of Zest branches (master, and maybe others) ?
https://builds.apache.org/
Bye,
Sandro
2015-06-12 2:51 GMT+02:00 Niclas Hedhman
It would be great if you could lead the way on this.
Perhaps you and others haven't seen our codebase guideline;
http://zest.apache.org/community/codebase.html, which contains a nice
diagram on the Git forking model we use.
On Fri, Jun 12, 2015 at 4:31 PM, Sandro Martini
Sandro Martini created ZEST-28:
--
Summary: Create Jenkins Builds for Zest sources
Key: ZEST-28
URL: https://issues.apache.org/jira/browse/ZEST-28
Project: Zest
Issue Type: Sub-task
Hi Sandro,
at least for me this is a good idea ! I guess it will be possible to
measure aspects like
failing tests, coverage, .. in a automated way.
Cheers,
jj
2015-06-12 9:51 GMT+02:00 Sandro Martini sandro.mart...@gmail.com:
Hi all,
to help with builds (or better to ensure code is
Yes, I did a setup some time ago for Pivot (one build per branch with
default JDK, and another with a more recent JDK, so in total 4 or more
daily builds).
Zest uses Gradle so all should be doable.
At the moment Zest is using Gradle-2.2.1, but latest (2.4) is faster,
what do you think to update
Hi Paul,
And for information we have our old CI server at
https://qi4j.ci.cloudbees.com/
It already points to Apache git service.
great, I haven't an account there, but I'll try to take a look
The uploadArchive weekly job push SNAPSHOTS maven artifacts to our old
repository hosted at
Hi,
Perhaps you and others haven't seen our codebase guideline;
http://zest.apache.org/community/codebase.html, which contains a nice
diagram on the Git forking model we use.
Note that in that page, references aren't to ASF Git Zest repository
... and probably something (later) should be
Yes, you are correct. Those community pages needs to be ASFified soon
enough. Qi4j started in 2007, and it has been a long journey and many
drastic changes along the way, from subversion to self-hosted Git to GitHub
hosted and now to ASF hosted, from SiteVision CMS to AsciiDoc + Jekyll and
now
Hi all,
sorry for the noise emails at any failed build ... tell me if it's too
much and I can temporarily disable or reduce to 1 build per day for
now ...
Bye
2015-06-12 22:47 GMT+02:00 Apache Jenkins Server jenk...@builds.apache.org:
See
Also, who can enable more Karma for committers at Zest on this build? I
don't seem to be allowed to view nor change the config.
Niclas
On Sat, Jun 13, 2015 at 11:08 AM, Niclas Hedhman nic...@hedhman.org wrote:
IIRC, instead of limiting the builds, one can limit the number of emails
to a
[
https://issues.apache.org/jira/browse/ZEST-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14583403#comment-14583403
]
Sandro Martini commented on ZEST-28:
Here you can find the build for the develop branch,
Niclas Hedhman a écrit :
Perhaps you and others haven't seen our codebase guideline;
http://zest.apache.org/community/codebase.html, which contains a nice
diagram on the Git forking model we use.
And for information we have our old CI server at
https://qi4j.ci.cloudbees.com/
It already points
[
https://issues.apache.org/jira/browse/ZEST-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14583388#comment-14583388
]
Paul Merlin commented on ZEST-28:
-
The build now use Gradle 2.4, see commit 07bf7fe
Create
See
https://builds.apache.org/job/Zest-qi4j%20develop%20on%20Java7%20(Oracle%20JDK)/2/
--
[...truncated 1440 lines...]
:org.qi4j.extensions:org.qi4j.extension.indexing-sql:jar
:org.qi4j.samples:org.qi4j.sample.sql-support:makeVersionClass
See
https://builds.apache.org/job/Zest-qi4j%20develop%20on%20Java7%20(Oracle%20JDK)/1/
--
[...truncated 1836 lines...]
^
15 matches
Mail list logo
