Hi,
The Apache JIRA was very responsive a few months ago. Now it is damn slow, so I
cannot cope with the tickets flowing in any more. Every view now lasts 10-20
seconds.
Anyone seeing this too ?
Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
+1
signature.asc
Description: Message signed with OpenPGP using GPGMail
I appreciate if we can reach a common
understanding who can use it and how its to be used.
Greetings
Dr. Olaf Flebbe
signature.asc
Description: Message signed with OpenPGP using GPGMail
Hi,
Since I am struggling with getting the vagrant-puppet-docker things to run
correct on debian, I now tried to use the centos6 way.
image: Removing intermediate container 05e60389c4c4
image: Step 10 : CMD /usr/sbin/sshd -D
image: ---> Running in eea418d398ea
image: ---> bb7b7
+1. Thanks for clarification.
signature.asc
Description: Message signed with OpenPGP using GPGMail
I second Cos,
First steps first: Automatically build repositories are needed badly.
Olaf
> Am 27.03.2015 um 00:43 schrieb Konstantin Boudnik :
>
> I am reading this discussion and it's great to have the road map for the
> fully-automated CI including containers rebuilding, etc.
>
> However, i
#2 for sure
signature.asc
Description: Message signed with OpenPGP using GPGMail
Hi,
While I was in a rush, I accidentely checked in a couple of bogus commits
(They were not merged properly)
The resulting code is o.k. but commits in between are not.
Can we revert origin/master back to f83a9c48af6031015e175326a3a3e25bf749b2f2,
the last regular commit ?
git checkout origi
to break. If you feel like the commits are bad - just revert the commits.
>
> Cos
>
>> On Mon, May 11, 2015 at 08:01AM, Olaf Flebbe wrote:
>> Hi,
>>
>> While I was in a rush, I accidentely checked in a couple of bogus commits
>> (They were not merged properl
Hi Evans,
A +1 for creating symlinks in the post-install phase of the package, since
they are needed for the package to work, if I understand correctly. packages
itself should work (somehow) out of the box. Why are you not considering
packaging the symlinks directly in the RPM/DEB?
Olaf
> Am
Hi Evans,
Sorry for late answer, I was away from fast internet for a few weeks. Great to
see progress. Please contact me directly what issue you have with debian8.
Since I have no credentials I cannot help right now.
The official debian release "docker pull debian:jessie“ should be sufficient.
> Am 11.06.2015 um 11:07 schrieb Konstantin Boudnik :
>
>
>
> Good stuff, dudes! Big time welcome!!!
>
thanks all! it is an amazing experience to work with you. a special thanks and
congrats to evans, being a big help to push things forward!
olaf
> Am 11.06.2015 um 11:07 schrieb Konstantin Boudnik :
>
>
>
> Good stuff, dudes! Big time welcome!!!
>
hi cos,
thanks for asking.
two of the new commits were critical since last minute changes broke
compilation.
I see no further technical Jiras waiting for inclusion into a 1.0 tag.
But I am missing one „huge“ commit:
Our web site is essentially a heap of obsolete stuff. Since the website is
s
Hi,
I plan to attend the ApacheCon Europe Big Data in Budapest and would like to
give either a tutorial // bigtop install session or at least a BoF session.
What do you think, anyone else supporting this? Or anyone else already
submitted a talk already ?
Olaf
signature.asc
Description: Mess
Hi
I updated my proposal. Maybe I can arrange Michael Weiser can attend, too,
since he did most of the technical input.
Olaf
> Am 09.07.2015 um 08:46 schrieb n...@reactor8.com:
>
> Here is doc setup to track the event details, including possible talks and
> any other group details:
>
> http
Jay,
What's the JIRA Issue number?
Olaf
> Am 10.07.2015 um 23:30 schrieb Jay Vyas :
>
> My thought is no. Hive tests were broken in 0.8 and we released hive. We
> continue evolving on head so it's ok. But in pretty lax about this stuff
>
> Sent from my iPhone
>
>> On Jul 9, 2015, at 10:49 A
Hi everyone,
nice to know someyone with scientific computing background around, too.
Let me phrase a bit different what "native" to LInux mean to me: The
filesystem's API is the open(2), close(2) systemcalls, rather a Java API. FUSE
mounted filesystems are generally slow because of the add
ating it our of the master anyway, so I see no reason to
>>> hold
>>>>>> 1.0
>>>>>> because of the website changes.
>>>>>>
>>>>>> So, shall I spin-out RC1 then?
>>>>>> Cos
>>>>>>
>
Cos,
> I didn't bring up the release or their tags anywhere in my email, so I am not
> sure what's your point here... Besides, with git we aren't relying on release
> tags as they are mutable; instead we are relying on commit SHA1.
>
A git tag is not mutable and should not be moved, since it i
Cos,
> Evidently, "is not mutable" and "shouldn't be moved" are two very different
> properties.
Of course, you are right.
> What github does for their releases is of no relevance to us,.
You are right, but I would like to mention we use this in bigtop.mk, too.
HUE_SITE=https://github.com/clou
mine got accepted, too
olaf
> Am 29.07.2015 um 06:14 schrieb :
>
> With yours looks like we have 4 total so far for the group.
>
> @olaf and @evans also submitted a couple others I believe
>
>
> -Original Message-
> From: RJ Nowling [mailto:rnowl...@gmail.com]
> Sent: Tuesday, Jul
-1: There are directories in the release tgz which should be left out.
buildSrc/build
buildSrc/.gradle
If these dirs are removed from tar , +1 from me.
And there is a difference to the release-1.0.0 tag (is this a workaround for
the JIRA just commited?)
diff -ur bigtop-1.0.0/pom.xml ../bigtop
a/browse/BIGTOP-1499
>
> I will re-do the artifacts tonight and start the vote unless there's a strong
> opinion about the first point above.
>
> Thanks!
> Cos
>
> On Mon, Aug 03, 2015 at 10:29PM, Olaf Flebbe wrote:
>> -1: There are directories in the rele
+1, for me too ... for the same reason.
Olaf
> Am 04.08.2015 um 17:24 schrieb Evans Ye :
>
> I'd be +1 since the svn publishing is not that intuitive which me took lots
> of time to figure it out.
>
> 2015-08-04 10:09 GMT+08:00 jay vyas :
>
>> FYI, I've created this INFRA ticket to conclude th
Sigh,... I had only this night the chance to recompile everything and I am
hitting this problem within crunch
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.1:site (default-cli) on project
crunch-parent: Execution default-cli of goal
org.apache.maven.plugins:maven-
have any clue yet, but maybe it's a network issue?
>
>
> 2015-08-09 16:25 GMT+08:00 Olaf Flebbe :
>
>> Sigh,... I had only this night the chance to recompile everything and I am
>> hitting this problem within crunch
>>
>> [ERROR] Failed to execute
Hi,
What are we using the KEYS file for ? What is the status of BIGTOP-1762 ?
I would like to advance bigtop and have the CI create a signed repository of
bigtop (that's one of the reasons behind BIGTOP-1917)
There seems to be some signing process for yum repos: Who has "owns" this key?
ca
+1: Verified debian rebuild, git Tag
signature.asc
Description: Message signed with OpenPGP using GPGMail
Yep, mvn installed by the gradlew toolchain is 3.0.5 in branch-1.0 which does
not show this bug.
I accidantely used gradlew toolchain from master branch which shows the crunch
problem in branch 1.0, but this is not an supported situation.
Olaf
> Am 10.08.2015 um 23:52 schrieb Andrew Purtell :
no:
$ docker run bigtop/slaves:debian-8 bash -c '. /etc/profile.d/bigtop.sh; mvn
--version'
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
13:51:28+)
Maven home: /usr/local/maven
Java version: 1.7.0_79, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-ope
This is more or less a dup to BIGTOP-1916. But I am unsure if I should update
this *now* since the URL to 1.0.0 release is not valid .
Olaf
> Am 10.08.2015 um 01:59 schrieb Konstantin Boudnik :
>
> A small update:
>The URL to the KEYS at the botton has the old version of the KEYS file
>
>
Hi Nate!
Same for me. Unfortunately will be arriving late Sunday.
Olaf
> Am 17.08.2015 um 16:52 schrieb Evans Ye :
>
> Would be a great idea Nate, but same with RJ I won't be there until Sunday.
>
> 2015-08-17 7:30 GMT+08:00 Roman Shaposhnik :
>
>> Hi Nate!
>>
>> awesome news on the possibi
Hi,
Nive to have data generators in Bigtop.
But please do not include it in bigtop_utils, since this package is mandatory.
Not everyone needs a data generator .
Olaf
> Am 26.08.2015 um 11:25 schrieb Jay Vyas :
>
> Publishing the jar to bigtops maven is probably a good first step ,Then apps
Ticket to follow ...
Olaf
> Am 26.08.2015 um 22:56 schrieb Konstantin Boudnik :
>
> On Wed, Aug 26, 2015 at 10:38PM, Olaf Flebbe wrote:
>> Hi,
>>
>> Nive to have data generators in Bigtop.
>>
>> But please do not include it in bigtop_utils, since thi
and its libraries into a local maven repo.
>>>>>>> This makes development easy. Eventually, I would like to post
>>>>>>> binaries
>>>>>> through
>>>>>>> Maven for easy integration by users. RPMs / Debs could be
I can second it:
I added to /etc/yum.repo.d/meins.repo
[meins]
name=Bigtop epo
baseurl=http://bigtop.s3.amazonaws.com/releases/1.0.0/centos/7/x86_64/
enabled=1
gpgcheck=0
priority=1
and got
Downloading packages:
hbase-0.98.12-1.el7.centos.noa FAILED
Hi,
even hue is downloading cloudera snapshots (sic!) from maven to compile
against. IIRC these binaries are not bundled with "our" packaging.
Olaf
> Am 10.09.2015 um 03:18 schrieb Konstantin Boudnik :
>
> I have been running the full build to validate the DSL patch and have noticed
> that kit
Sorry, I haven't followed the initial discussion since I was not onboard at
that time.
From my view bigtop is the fastest moving project, I ever knew. I am active for
over 20 years in all kinds of opensource projects, but bigtops tops them all in
speed, second fastest maybe samba and linux kern
Hi,
Evans is adressing my concerns very well.
Olaf
> Am 15.09.2015 um 14:43 schrieb Evans Ye :
>
> There're some points made by Olaf and I think they're valuable. But I think
> we can get the benefit of reviewing process by applying some policy to our
> CTR.
>
> For example, one is forced to d
Welcome YoungWoo Kim!
Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
Welcome RJ!
Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
hi
I have the free nexus server running as a caching proxy in front of my docker
compiles, which speeds up downloads tremendously. I didn't count but at least
2/3 of all artifacts even from https:// repos are cached.
i added 5 or so dependency repos on the server and generated an
.m2/settings.
Hi,
I tried to rebuid the bigtop-slave docker image through
http://ci.bigtop.apache.org:8080/view/Docker/job/Docker-Toolchain-Trunk/
Sadly, It failed immediatly. Evans, do you know what is going wrong ?
Thanks
Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
HI RJ,
Regarding R :
We should not provide an R of our own, rather integrate in distribution
supplied packages (i.e. R / R-devel from EPEL for Centos/Fedora , r-base-dev
on an debian distro, i am sure there is something on opensuse build service too)
Olaf
> Am 04 Oct 2015 um 14:28 schrieb
u feel about installing R whenever we need to build Bigtop? :)
>
> Thanks,
> RJ
>
> On Sun, Oct 4, 2015 at 3:56 PM, Olaf Flebbe wrote:
>
>> HI RJ,
>>
>> Regarding R :
>>
>> We should not provide an R of our own, rather integrate in distribution
>> supplie
> Am 05.10.2015 um 09:12 schrieb Konstantin Boudnik :
>
> On Sun, Oct 04, 2015 at 09:22PM, Olaf Flebbe wrote:
>> Hi,
>>
>> there are options to have clean room dependency installation for debian and
>> rpm systems: debian's pbuilder and fedora
hi,
The build dockers are updated. Be sure to use bigtop/slaves:trunk-centos-7 for
instance. The trunk-... containers denote the current git trunk built by
docker/build-slaves/... recipies.
-olaf
> Am 08.10.2015 um 19:32 schrieb Konstantin Boudnik :
>
> Indeed, but I don't think we have upgr
Hi Cos,
What signatures are targeting specifically ?
org.apache.hadoop.io.MD5Hash and its usage?
or
something like
bigtop-packages/src/deb/hama/rules: dh_md5sums
bigtop-packages/src/common/pig/do-component-build: echo
"ea58a078e3861d4dfc8bf3296a53a5f8 apache-forrest-0.9.tar.gz"
No, I was more after our own release signing practices. And me as the RM for
> the last is to blame to not raising this earlier. We're still using md5 and
> sha1 to sign our releases. And I am proposing to switch to sha512, starting
> from 1.1 and on.
>
> Cos
>
> On Sat, O
Hi Cos,
Is it correct that we should not put our release artifacts on apache dist,
since Apache is about code not binaries?
Can we use something like bintray.org ? Looks like the functionality we need:
RPM and DEB repo, and does have an API.
Olaf
> Am 18.10.2015 um 09:30 schrieb Evans Ye :
Evans, let me thank you for your work on the CI! Unfortunately I am very busy
with other things this and next week, so I cannot contribute right now.
-Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
Just included the long overdue hue-3.9 update.
I have a couple of puppet code changes I like to commit.
Olaf
> Am 06.11.2015 um 21:23 schrieb Konstantin Boudnik :
>
> Guys,
>
> I have put a draft of 1.1 BOM to
> https://issues.apache.org/jira/browse/BIGTOP-2078
> Thinking of making the releas
Hi,
I would like to add a nexus for speeding up the build process. Do anyone has
the credentials for starting a nexus container instance ?
Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
shots/
apache.snapshots.https
> Am 09.11.2015 um 04:20 schrieb Roman Shaposhnik :
>
> Olaf, could you please elaborate a little bit about your proposed
> usage of Nexus?
>
> Also, why not smt. like Artifactory? Just curious...
>
> Thanks,
> Roman.
>
> On Sun, Nov 8
Hi
I propose to drop centos6 after the next release, since its end of life is Q2
2017. The code base of rhel6/centos6 is way to old to support it for new
products.
We should advance to RHEL7 now...
Regarding ubuntu14.04 LTS : I have mixed feelings since we have a few issues
with puppet and th
Hi,
Seems I haven't broken too much ;-) +1 from me, too.
Thanks.
Olaf
> Am 17.11.2015 um 17:19 schrieb Roman Shaposhnik :
>
> On Mon, Nov 16, 2015 at 10:53 PM, Konstantin Boudnik wrote:
>> What I find real good about this experiment is that we don't see any abuse of
>> this policy. Committer
Hi,
Yep I broke it. ;-/ But opensuse broke itself, too. As far as I can tell this
change came from a suse update to the OS container.
Of course openssl and libressl cannot coexist, since libressl replaces openssl.
The docker images are weird. I will look into it this evening if I can work
o
Seems there is a easy fix. Will try to provide it with BIGTOP-2152
Olaf
> Am 18.11.2015 um 20:45 schrieb Konstantin Boudnik :
>
> On Wed, Nov 18, 2015 at 10:39AM, Olaf Flebbe wrote:
>> Hi,
>>
>> Yep I broke it. ;-/ But opensuse broke itself, too. As far as I can te
+1, thanks!
> Am 21.11.2015 um 20:34 schrieb Konstantin Boudnik :
>
> Using CTR for the Bigtop project has been discussed, experimented for a few
> months, and discussed again on this long thread [1] for alomost a year now.
> The
> consensus seems to be reached, but because this is a policy chan
Hi,
I worked the last days on adding a artifact repository proxy support at our
build environment:
https://issues.apache.org/jira/browse/BIGTOP-2081?focusedCommentId=15034750&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15034750
It works for me ;-)
But the ulti
Hi,
Seems like the caching of artifacts almost the does an Allstar-Blues!
http://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/69/. The
failures because of network issues are (almost) gone.
I observed the only failure
http://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-pa
Cos
>
> P.S. I wish I knew anything about Hue to help with it.
>
> On Tue, Dec 08, 2015 at 08:36AM, Olaf Flebbe wrote:
>> Hi,
>>
>> Seems like the caching of artifacts almost the does an Allstar-Blues!
>> http://ci.bigtop.apache.org/view/Packages/job/Bigtop-t
Hi,
I changed the build of bigtop-trunk-packages to have a pre job
bigtop-trunk-packages-nexus-start to be run on all node via a label-plugin and
a bigtop-trunk-packages-nexus-stop to clean up afterwards.
unfortunately the docker daemon on docker-slave-06 is unresponsive , so I
decided to disab
; Cos
>
> On Fri, Dec 11, 2015 at 11:43PM, Olaf Flebbe wrote:
>> Hi,
>>
>> I changed the build of bigtop-trunk-packages to have a pre job
>> bigtop-trunk-packages-nexus-start to be run on all node via a label-plugin
>> and a bigtop-trunk-packages-nexus-stop to cl
Hi Cos,
Nope, we do not need a SMTP Server we need a valid SMTP Client configuration.
http://ci.bigtop.apache.org/configure
Perhaps we can work something out with INFRA or AWS has something in place for
us.
Olaf
> Am 23.12.2015 um 08:48 schrieb Konstantin Boudnik :
>
> Guys,
>
> I am looki
Hi
I stumbled over fallout of BIGTOP-2110
IMHO this is absolutly weird to run gradle within gradle ... and pick up side
effects.
* The output is misleading (Because I get the bigtop logo each time I run
bigtop-slaves). I thought that we have dependency issues within build.gradle.
Somehow the
Hi Evans,
> My personal reason for not keep implementing this is because I plan to drop
> vagrant and embrace docker's native solutions(machine, compose, swarm) for
> our docker provisioner.
YES! PLEASE! That would be great!
Olaf
signature.asc
Description: Message signed with OpenPGP using GP
ing entries:
build
output
bigtop-packages
dl
IMHO Much more important than a few possible garbage entries in ~/.gradle (Or
is it only me falling over this sending GB of staff to docker when building
images on my toy machine?)
Olaf
> 2015-12-25 4:33 GMT+08:00 Olaf Flebbe :
>
>
Hi,
You can overwrite this by an patch file.
See
https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+Packaging
(If you need to apply ...)
Olaf
> Am 27.12.2015 um 13:02 schrieb MrAsanjar . :
>
> Hi all
> config.guess packaged in bigtop-jsvc_1.0.15.orig.tar.gz is outdated and
> doesn't in
Hi,
I see obsolete tags in bigtop/puppet
opensuse-12.3
ubuntu-10.04
ubuntu-12.04
centos-6.4
Any contraindications to remove these unmaintained images?
The rest seems to be build by out CI process.
Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
leaner view?
> Any reason to remove?
>
> 2015-12-28 10:23 GMT+08:00 MrAsanjar . :
>
>> I would definitely reduce number of regression testing.
>>
>> On Sun, Dec 27, 2015 at 2:19 PM, Konstantin Boudnik
>> wrote:
>>
>>> +1
>>>
>>&g
Ok, I will drop it!
Olaf
> Am 29.12.2015 um 20:15 schrieb Roman Shaposhnik :
>
> As somebody who introduced them in the first place -- I say: drop it!
> Drop it now! ;-)
signature.asc
Description: Message signed with OpenPGP using GPGMail
WTF ? I never seen this job! Who is maintaing them ? Why can I do not get the
config of these jobs ? What is the purpose ?
Olaf
> Am 31.12.2015 um 07:19 schrieb Konstantin Boudnik :
>
> Guys,
>
> looks like our artifacts publishing build
>
>https://builds.apache.org/job/Bigtop-trunk/151
Hi Amir,
I finally processed the JIRAs you are mentioning.
Please submit a patch for the jsvc issue. (Otherwise I will, based on the info
you have given.) Essentially the patches work the same as in debian package
files.
I am not to familiar with the PPA's of ubuntu. Is there a possibility to
Hi,
My personal New Year's Greeting:
Let me announce that now that regulary Bigtop CI jobs for for the first non-x86
HW are now up and running!
That's the Build for the IBM Power 8 Little Endian Architecture:
http://ci.bigtop.apache.org/job/Bigtop-trunk-packages-ppc64le/
While this may not be
Hi
the image is screwed up... java is missing for some reason.
Olaf
> Am 05.01.2016 um 07:59 schrieb Konstantin Boudnik :
>
> On Mon, Jan 04, 2016 at 09:28PM, Peter Linnell wrote:
>> On Mon, 4 Jan 2016 14:31:24 -0800
>> Konstantin Boudnik wrote:
>>
>>> Guys,
>>>
>>> something quite weird is
Hi,
updating the CI Infrastructure made Bigtop-trunk all blue.
I will disable the nexus workaroung now for Bigtop-trunk-packages . A new
bigtop/slaves:trunk-opensuse-13.2 image is pushed
Olaf
signature.asc
Description: Message signed with OpenPGP using GPGMail
ebian-8,label=docker-slave/lastSuccessfulBuild/artifact/output/apt/
Olaf
stantin Boudnik :
>
>
> I might be color-challenged %) then
>http://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/
>
> cos
>
> On Fri, Jan 08, 2016 at 06:43PM, Olaf Flebbe wrot
hu, Jan 07, 2016 at 03:28PM, jay vyas wrote:
>>> hahaha . I'd wait for Roman to respond on this. But I think anything
>>> thats not being maintained is on the chopping block.
>>>
>>> On Thu, Jan 7, 2016 at 3:16 PM, Olaf Flebbe wrote:
>>>
Good idea, removed it from Bigtop-trunk-packages ... Too lazy to remove it
from Bigtop-trunk as well.
Olaf
> Am 09.01.2016 um 15:45 schrieb jay vyas :
>
> Why not just turn off giraph in the CI ; until waiting to decide?
>
> On Sat, Jan 9, 2016 at 9:08 AM, Olaf Flebbe wrote:
Hi,
>
> I think having a local mirroring Nexus server - either per the whole build, or
> just standalone, might be very beneficial for the build time/failure rates.
>
> Cos
I like to have it both the -trunk and -trunk-packages, too.
Problem is how to start/stop it, since a build will fail
Hi,
> Am 11.01.2016 um 18:54 schrieb Evans Ye :
>
> I just found those deprecated CI jobs has been cleaned up.
Yep, that was me. It was tricky to do this efficiently.
>
> Anyway thanks for doing this, it looks so neat!
>
Evans, I didn't have a detailed look at the Docker Config of Jenkins it
> Am 11.01.2016 um 20:46 schrieb Konstantin Boudnik :
>
> BTW, shall we be adding opensuse-13.2 to Bigtop-trunk job?
Problem is opensuse uses a different repository mechanism "zypper" rather
redhat and debian derived distributions. AFAIK this hasn't been implemented.
Olaf
signature.asc
Desc
> Am 11.01.2016 um 22:59 schrieb Konstantin Boudnik :
>
> On Mon, Jan 11, 2016 at 10:57PM, Olaf Flebbe wrote:
>>
>>> Am 11.01.2016 um 20:46 schrieb Konstantin Boudnik :
>>>
>>> BTW, shall we be adding opensuse-13.2 to Bigtop-trunk job?
>>
&g
,
> an ebs volume.
> 2016/1/12 上午5:54 於 "Olaf Flebbe" 寫道:
>
>> Hi,
>>
>>> Am 11.01.2016 um 18:54 schrieb Evans Ye :
>>>
>>> I just found those deprecated CI jobs has been cleaned up.
>>
>> Yep, that was me. It was tri
> Am 15.01.2016 um 19:12 schrieb MrAsanjar . :
>
> It appears Jenkins build #15 for ppc64le is hung for the last three days,
> could we restarted?
> http://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages-ppc64le/
> Thanks in advance
This is the third time the machine hangs. Request
Somehow jenkins slave config of the machine was garbeled. I had to delete the
slave and add it again.
It works now, again
Olaf.
> Am 15.01.2016 um 19:12 schrieb MrAsanjar . :
>
> It appears Jenkins build #15 for ppc64le is hung for the last three days,
> could we restarted?
> http://ci.bigtop
You do not need to switch to ubuntu-15.04 , you should simply pull new images
docker pull bigtop/slaves:trunk-ubuntu-14.04
If you like to supply bigtop with a ubuntu-15.04 for amd64 configuration you
should look into the docker subdirectory and copy a directory and edit 14.04 ->
15.04
If you ha
Since an anonymous user cannot look into the configuration of a job
The centos-6 job looks like:
-
# setup configuration file
cat >
bigtop-deploy/vm/vagrant-puppet-docker/vagrantconfig_Bigtop-Docker-provisioner-centos-6.yaml
<<-__EOT__
docker:
memory_size: "4096"
Congrats Nate!
Olaf
> Am 25.01.2016 um 22:00 schrieb Andrew Purtell :
>
> On behalf of the Apache Bigtop Project Management Committee, I am pleased to
> announce that Nate D'Amico has accepted our invitation to join the Bigtop PMC.
>
> Please join me in congratulating Nate!
>
> --
> Best rega
> Am 27.01.2016 um 05:58 schrieb Jay Vyas :
>
> If hibench can run as a gradle task that would be far more useful to the
> typical audience IMO and less technical debt to carry
>
> .I think the amount of boilerplate for a package only is justified if
> it's a distributed component.
>
Or
gt;>>> will try to build more carefully to go well with the Bigtop.
>>>>>>>>
>>>>>>>> Yeongeon
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2015-11-07 10:49 GMT+09:
Hi Nate,
Thanks! Since I cannot attend this conference, I can only support creating the
presentation:
I would be happy if someone else will present Bigtop there.
I hacked a few slides together containing the key points of the porting efforts.
https://docs.google.com/presentation/d/1woWQlUPqEbBB
Hi Cos,
Do we need a paragraph in release docs about these things?
* Creating release CI Jobs:
Docker-Toolchain-1.1.0
Docker-Toolchain-1.1.0-push
Docker-Toolchain-1.1.0-pull
Bigtop-1.1
(Same for ppc64le)
* Tagging Docker Images
Olaf
signature.asc
Description: Message signed with OpenPGP u
Hi Evans,
I saw that latest Docker-Toolchain-Trunk didn't go through (I triggered a rerun)
For instance:
http://ci.bigtop.apache.org/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/17/console
Is it possible to improve gradle experience in the containers? Containers
hi,
the signature file is made with a key CB588E12 , not contained in KEYS.
Or missed I something important?
Olaf
> Am 31.01.2016 um 05:35 schrieb Konstantin Boudnik :
>
> This is the vote for release 1.1.0 of Apache Bigtop.
>
> It fixes the following issues:
>
> https://issues.apache.org/ji
hi andrew,
++1 ! thanks.
olaf
> Am 04.02.2016 um 19:14 schrieb Andrew Purtell :
>
> I volunteer to re-run the release vote next week with the same set of
> artifacts.
>
>>> On Feb 4, 2016, at 10:03 AM, Konstantin Boudnik wrote:
>>>
>>> On Thu, Feb 04, 2016 at 09:50AM, Andrew Purtell wrote
g: There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
> Subkey fingerprint: 88C5 8332 D1A9 6A83 F9B3 2776 7A7C 8596 CB58 8E12
>
>
> 2016-02-05 17:01 GMT+08:00 Olaf Flebbe :
>
>
Sun Jan 31 12:09:46 2016 CST using DSA key ID
>> CB588E12
>>> gpg: Good signature from "Konstantin I Boudnik (Cos) "
>>> gpg: aka "Konstantin I Boudnik (Cos) "
>>> gpg: WARNING: This key is not certified with a trusted signature!
>>&g
1 - 100 of 1148 matches
Mail list logo