CI is, at its core, running a series of commands on each commit, then
performing actions/displaying reports based on their results. I'd think
that any CI server could handle Fossil. The various VCS plugins/support
just do the integration a bit more smoothly, or displays the output
formatted more nicely.
I just treat the fossil binary as another shell command. Jenkins' URL
trigger polls the commit timeline on each of my repositories, then
triggers a build when the page's contents change (I.e. when a new commit
is made.) I'd eventually like to use the TCL support to hit the Jenkins
post-commit URL, since I'm not immediately certain that my solution will
work for locked-down repositories.
On 10/23/2012 02:48 PM, sphere foura wrote:
Nolan,
I have no experience with Jenkins whatsoever, but can figure the
basics out. Since you say that you have already done it, it's worth a try.
What I really wanted was confirmation that it's not a dead end road
that I'm taking. So thanks for your confirmation.
Apologies if my Q was weird. I'm new to setting up CI+repo.
--sph
On Tue, Oct 23, 2012 at 11:39 PM, Nolan Darilek
<no...@thewordnerd.info <mailto:no...@thewordnerd.info>> wrote:
I've used it with Jenkins for over a year now. What exactly is it
that you need?
On 10/23/2012 01:08 PM, sphere foura wrote:
Remigiusz,
Thanks for the info. Even I was thinking of doing post-commit
eventually.
Sadly, there is no way I can use fossil if there is no mechanism
to integrate with some CI tool or the other.
Someday perhaps I could write a plugin for
cruisecontrol/Jenkins/Hudson/whatever, but not now with a major
project coming up.
-sph
On Tue, Oct 23, 2012 at 8:33 PM, Remigiusz Modrzejewski
<l...@maxnet.org.pl <mailto:l...@maxnet.org.pl>> wrote:
On Oct 23, 2012, at 13:28 , sphere foura wrote:
> My question is: Which CI tool best connects with fossil?
Can anyone back
> their assertion with a proven implementation?
The last time I checked, there was no integration provided by
any of them. But it's usually no problem to provide your own
script to do the checkout, what makes the matter pretty
trivial if you want periodical tests. I wanted post-commit,
but there was no support for that in Fossil at that time.
There allegedly is now, through some Tcl hooks, but
integrating it with CI seems to be still uncharted territory...
Kind regards,
Remigiusz Modrzejewski
PS. Excuse any grammar mistakes, I'm nearly braindead after
too long meeting.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
<mailto:fossil-users@lists.fossil-scm.org>
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
<mailto:fossil-users@lists.fossil-scm.org>
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
<mailto:fossil-users@lists.fossil-scm.org>
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
