Additionally it seems all Jenkins nodes are reserved:
** cassandra2 is reserved for jobs with matching label
expression; cassandra3
is reserved for jobs with matching label expression; cassandra4 is reserved
for jobs with matching label expression; cassandra5 is reserved for jobs
with matching la
Hi,
I prototyped an integration between Jenkins and GH pull requests based,
see
- https://builds.apache.org/view/S-Z/view/Sling/job/sling-site/
- https://github.com/apache/sling-site/pull/3
This is done using solely the Jenkins multibranch pipeline job type,
which is pretty cool as it does not r
> On Oct 20, 2017, at 1:56 AM, Maxim Solodovnik wrote:
>
> Additionally it seems all Jenkins nodes are reserved:
>
> On Fri, Oct 20, 2017 at 9:35 AM, Alex Harui
> wrote:
>
>> Hi,
>>
>> I'm finding that the UI for Jenkins is horribly slow today.
Yes, we seem to have some problems that have
> On Oct 19, 2017, at 7:35 PM, Alex Harui wrote:
>
> Hi,
>
> I'm finding that the UI for Jenkins is horribly slow today.
I think it’s been a slow for a while. There are good days and there are bad
days (like today, where it is bordering on unusable). I’ve been doing trace
routes from home
Jenkins UI feels more reponseive now. Thanks.
-Alex
On 10/20/17, 10:17 AM, "Chris Lambertus" wrote:
>
>> On Oct 20, 2017, at 1:56 AM, Maxim Solodovnik
>>wrote:
>>
>> Additionally it seems all Jenkins nodes are reserved:
>>
>> On Fri, Oct 20, 2017 at 9:35 AM, Alex Harui
>> wrote:
>>
>>> Hi,
> On Oct 20, 2017, at 12:54 PM, Alex Harui wrote:
>
> Jenkins UI feels more reponseive now. Thanks.
> -Alex
Hopefully it stays that way. The restart is now completed, as you noted.
-Chris
signature.asc
Description: Message signed with OpenPGP
Hello from the Beam project,
We have a Jenkins build that pushes a snapshot jar every 24 hours (if tests
pass) and we would like to have the same for docker images that form a core
part of the Beam project.
Can you advise on the best way to go about this?
I am aware of the use of bintray for Doc
Be very careful here. Making such binaries available outside of your
immediate developer community is a violation of Apache policy:
http://www.apache.org/dev/release-distribution.html#unreleased
The middle two bullet points are the issue here.
CouchDB decided to build packages and binaries off
Thanks for the heads up!
When it comes to jars, I believe what we do is the usual and allowed
process for release candidates / nightly test jars. They go to the snapshot
repository [1], per the Release Policy [2] and ASF Jar FAQ [3]. So when it
comes to jars, I am fairly sure what we are doing is
