Hi
Quick question: what operating system does the available CI server run?
Even if docker is an option, the host system is matters.
Thanks
-d
Info about our existing infra is documented here:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins
On Sat, 25 Apr 2020 at 13:38, Davyd McColl wrote:
>
> Hi
>
> Quick question: what operating system does the available CI server run?
> Even if docker is an option, the host system is matter
Thanks for the reply (:
Would external build systems like circleci be acceptable too?
-d
On April 25, 2020 21:03:01 Matt Sicker wrote:
Info about our existing infra is documented here:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins
On Sat, 25 Apr 2020 at 13:38, Davyd McColl wr
The only external build systems that are set up for Apache right now
are Travis and some limited GitHub Action experiments. Other CI
systems may need to talk with Apache Infra.
On Sat, 25 Apr 2020 at 14:47, Davyd McColl wrote:
>
> Thanks for the reply (:
>
> Would external build systems like circ
What would need to be done to make other CI systems talk with Apache Infra?
I ask because I've spend around a day now trying to convince Travis CI to build
log4net successfully, without a lot of joy, particularly because the Travis
Windows build environment is quite out of date, having been laun
Seems like I missed some other services: https://infra.apache.org/services.html
If nothing on there is appropriate, I think we need to create a Jira
ticket in https://issues.apache.org/jira/browse/INFRA
On Mon, 27 Apr 2020 at 01:28, Davyd McColl wrote:
>
> What would need to be done to make othe
Looks like AppVeyor is another option. Is that comparable to CircleCI?
(For context, I'm mostly familiar with Jenkins as I work on that
project at $dayjob)
On Mon, 27 Apr 2020 at 09:36, Matt Sicker wrote:
>
> Seems like I missed some other services:
> https://infra.apache.org/services.html
>
>
As apache folks, we have the benefit of sponsored msdn subscriptions and
thus some sponsored computing time in azure. May that be an option?
I dont know about the tasks involved.
I can also think of cross compiling on ubuntu inside docker by leveraging
dotnet-sdk and linking against the reference
Thanks, I've already tried using mono for cross-compilation, but older
targets (and specifically client profile) make this option a bit of a
non-starter. I got it mostly working, but mostly isn't all the way.
CircleCI provides a good build environment, which I'm probably going to try
to replic
https://www.appveyor.com/docs/windows-images-software/
Also worth looking into. As for Azure, definitely something worth
asking around about, especially if they have something useful for us!
On Mon, 27 Apr 2020 at 14:13, Davyd McColl wrote:
>
> Thanks, I've already tried using mono for cross-com
Mileage may vary, but I see no point in supporting ancient frameworks.
Better support only few valuable targets well and offload maintenance
efforts to whoever needs other targets that are hard to support. For
instance, whoever builds against client profile could fork and build
log4net from source.
If supporting them can come at minimal or zero cost, I don't see why not.
As stated before, this is already achieved within CircleCI, so I guess now
it's up to either integrating that within Apache infra, or replicating
elsewhere. I'm checking out appveyer too. At some point, though, I'd really
According to past Infra tickets, CircleCI requires write access to our
git repos, and that's not allowed at Apache. I have no idea if that
limitation in CircleCI has ever been fixed.
On Mon, 27 Apr 2020 at 14:55, Davyd McColl wrote:
>
> If supporting them can come at minimal or zero cost, I don't
Further info:
https://issues.apache.org/jira/browse/INFRA-17133
https://issues.apache.org/jira/browse/INFRA-16927
https://issues.apache.org/jira/browse/INFRA-15964
https://issues.apache.org/jira/browse/INFRA-12197
On Mon, 27 Apr 2020 at 15:09, Matt Sicker wrote:
>
> According to past Infra ticke
According to the documentation at CircleCI, this permission was required to
enumerate repositories for users. However, AppVeyer is capable of doing so
with a lesser permission, which I surmise may have been added after
CircleCI first established their permissions. I've submitted an inquiry on
t
Great, keep us updated! Some of those INFRA tickets are old, so it's
possible that CircleCI has changed things.
On Mon, 27 Apr 2020 at 15:31, Davyd McColl wrote:
>
> According to the documentation at CircleCI, this permission was required to
> enumerate repositories for users. However, AppVeyer i
16 matches
Mail list logo
