Is this happening when you are trying to log in to Jenkins?

On Mon, Apr 4, 2016 at 6:51 PM, Matt Post <[email protected]> wrote:

> "mjpost is missing the Job/ExtendedRead permission"
>
> → can you add me? Or do I need to email infrastructure?
>
> (Sorry for the constant questions!)
>
>
> > On Apr 4, 2016, at 5:19 PM, Lewis John Mcgibbney <
> [email protected]> wrote:
> >
> > Hi Matt,
> > This can be edited by going into the Jenkins job configuration tab [0]
> and
> > editing away.
> > If it requests for a log in then this should be your LDAP credentials
> > associated with your Apache ID.
> > Ta
> >
> > [0]
> >
> https://builds.apache.org/view/H-L/view/Joshua/job/joshua_master/configure
> >
> > On Mon, Apr 4, 2016 at 2:17 PM, Matt Post <[email protected]> wrote:
> >
> >> How do we edit the build info? Is this something only you can do,
> Lewis? I
> >> see some problems that would be resolved by adding $JOSHUA/bin to the
> path.
> >>
> >> matt
> >>
> >>
> >>> On Apr 4, 2016, at 4:59 PM, Lewis John Mcgibbney <
> >> [email protected]> wrote:
> >>>
> >>> OK so the build is now stable.
> >>> https://builds.apache.org/view/H-L/view/Joshua/job/joshua_master/10/
> >>> We should still utilize the docker container on builds... this is a
> >> better
> >>> idea.
> >>> We should also publish development documentation on each successful
> >> build.
> >>> This can be addressed over on
> >>> https://issues.apache.org/jira/browse/JOSHUA-250
> >>> Lewis
> >>>
> >>> On Mon, Apr 4, 2016 at 8:31 AM, Matt Post <[email protected]> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Also, note that the latest build failed because it's using Java 7, but
> >>>> Kellen's recent commits require Java 8.
> >>>>
> >>>> This means that those commits sort of snuck in a required Java 8
> >> upgrade.
> >>>> I'm fine to do this as we're on development, and we can make that a
> >> formal
> >>>> requirement as part of the next release. Java 8 is not that new.
> >>>>
> >>>> matt
> >>>>
> >>>>
> >>>>> On Apr 2, 2016, at 7:05 PM, Stian Soiland-Reyes <[email protected]>
> >>>> wrote:
> >>>>>
> >>>>> BTW - which of the nodes support docker containers?
> >>>>>
> >>>>> On 1 April 2016 at 17:20, Andrew Bayer <[email protected]>
> wrote:
> >>>>>> Should be on any of the ubuntu-[1,2,4,5,6] boxes or H10 and H11.
> >>>> Otherwise,
> >>>>>> probably not. As always, if you need system libraries installed, we
> >>>>>> strongly advise you run your build in a docker container, where you
> >> can
> >>>>>> control things like that.
> >>>>>>
> >>>>>> A.
> >>>>>>
> >>>>>> On Fri, Apr 1, 2016 at 9:18 AM, Lewis John Mcgibbney <
> >>>>>> [email protected]> wrote:
> >>>>>>
> >>>>>>> Hi builds@,
> >>>>>>> The named library is Boost http://www.boost.org/
> >>>>>>> Is this library installed on any build slave?
> >>>>>>>
> >>>>>>> On Fri, Apr 1, 2016 at 7:29 AM, Matt Post <[email protected]> wrote:
> >>>>>>>
> >>>>>>>> Thanks very much! Some of our tests are now passing (17/39), but
> >> now I
> >>>>>>> see
> >>>>>>>> that it is unable to locate boost:
> >>>>>>>>
> >>>>>>>>   [exec]   Unable to find the requested Boost libraries.
> >>>>>>>>   [exec]
> >>>>>>>>   [exec]   Boost version: 1.54.0
> >>>>>>>>   [exec]
> >>>>>>>>   [exec]   Boost include path: /usr/include
> >>>>>>>>   [exec]
> >>>>>>>>   [exec]   Could not find the following Boost libraries:
> >>>>>>>>   [exec]
> >>>>>>>>   [exec]           boost_system
> >>>>>>>>   [exec]           boost_thread
> >>>>>>>>   [exec]
> >>>>>>>>   [exec]   Some (but not all) of the required Boost libraries were
> >>>>>>>> found.  You may
> >>>>>>>>   [exec]   need to install these additional Boost libraries.
> >>>>>>>> Alternatively, set
> >>>>>>>>   [exec]   BOOST_LIBRARYDIR to the directory containing Boost
> >>>>>>> libraries
> >>>>>>>> or BOOST_ROOT
> >>>>>>>>   [exec]   to the location of Boost.
> >>>>>>>>
> >>>>>>>> Can you suggest what we can do to address this?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Apr 1, 2016, at 12:18 AM, Daniel Takamori <[email protected]>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>> The node, ubuntu3, that this job ran on runs 12.04 for
> >> compatibility
> >>>>>>>>> reasons and as such has an old version of cmake.  I've gone ahead
> >> and
> >>>>>>>>> modified your job from the label "solaris||ubuntu" to
> >>>>>>>>> "solaris||ubuntu&&!(ubuntu3)" to restrict to the newer 14.04
> nodes.
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>> -Pono
> >>>>>>>>>
> >>>>>>>>> On Fri, Apr 1, 2016 at 4:10 AM, Mattmann, Chris A (3980) <
> >>>>>>>>> [email protected]> wrote:
> >>>>>>>>>
> >>>>>>>>>> Send mail to [email protected], I’ve CC’ed them on this
> message.
> >>>>>>>>>>
> >>>>>>>>>> builds@, please help :)
> >>>>>>>>>>
> >>>>>>>>>>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>>>>>> Chris Mattmann, Ph.D.
> >>>>>>>>>> Chief Architect
> >>>>>>>>>> Instrument Software and Science Data Systems Section (398)
> >>>>>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >>>>>>>>>> Office: 168-519, Mailstop: 168-527
> >>>>>>>>>> Email: [email protected]
> >>>>>>>>>> WWW:  http://sunset.usc.edu/~mattmann/
> >>>>>>>>>>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>>>>>> Director, Information Retrieval and Data Science Group (IRDS)
> >>>>>>>>>> Adjunct Associate Professor, Computer Science Department
> >>>>>>>>>> University of Southern California, Los Angeles, CA 90089 USA
> >>>>>>>>>> WWW: http://irds.usc.edu/
> >>>>>>>>>>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> -----Original Message-----
> >>>>>>>>>> From: Matt Post <[email protected]>
> >>>>>>>>>> Reply-To: "[email protected]"
> >>>>>>>>>> <[email protected]>
> >>>>>>>>>> Date: Thursday, March 31, 2016 at 4:59 PM
> >>>>>>>>>> To: "[email protected]" <
> >>>>>>> [email protected]>
> >>>>>>>>>> Cc: "[email protected]" <[email protected]>
> >>>>>>>>>> Subject: Re: Build failed in Jenkins: joshua_master #4
> >>>>>>>>>>
> >>>>>>>>>>> (To be clear, I'm asking if anyone knows how we can get a newer
> >>>>>>> version
> >>>>>>>>>>> of cmake installed on build.apache.org...)
> >>>>>>>>>>>
> >>>>>>>>>>>> On Mar 31, 2016, at 7:50 PM, Matt Post <[email protected]>
> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> It looks like the first failure is at KenLM. I see:
> >>>>>>>>>>>>
> >>>>>>>>>>>>  CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
> >>>>>>>>>>>>       [exec]   CMake 2.8.8 or higher is required.  You are
> >>>>>>> running
> >>>>>>>>>>>> version 2.8.7
> >>>>>>>>>>>>
> >>>>>>>>>>>> Is there any way that this can be fixed? CMake on my Mac is
> >> 3.4.3.
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> *Lewis*
> >>>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Stian Soiland-Reyes
> >>>>> Apache Taverna (incubating), Apache Commons RDF (incubating)
> >>>>> http://orcid.org/0000-0001-9842-9718
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> *Lewis*
> >>
> >>
> >
> >
> > --
> > *Lewis*
>
>


-- 
*Lewis*

Reply via email to