The “restrict where this job can be run” setting is trial and error. We occasionally have Jenkins jobs blow up because the slave wasn’t set up for something that causes our jobs to fail so we manually exclude them.
We would have to look at the test failures. Having them work on our laptops and fail in Jenkins is not unusual. With Log4j occasionally a test will just randomly fail for not apparent reason. If it happens regularly then most likely there is something wrong with the test (or code). Ralph > On May 7, 2019, at 9:40 AM, Andrei Ivanov <[email protected]> wrote: > > I've copied the "Log4j 2 2.x" job and adjusted it and now there is > https://builds.apache.org/view/L/view/Logging/job/Log4j%20Audit/ :-) > I hope the label for "Restrict where this project can be run" is ok. > > I've read through the pom.xml and I've enabled the "integration-tests" > profile, with a plan to also enable the "rat" once I fix some of the files > reported to be missing a licence. > > I see one of the tests failed, but I'm not sure why as it works fine for me. > > On Tue, May 7, 2019 at 7:16 PM Matt Sicker <[email protected]> wrote: > >> Great! >> >> On Tue, 7 May 2019 at 10:50, Andrei Ivanov <[email protected]> >> wrote: >>> >>> Seems to work now, thanks :-) >>> >>> On Tue, May 7, 2019 at 6:48 PM Matt Sicker <[email protected]> wrote: >>> >>>> Alright, I just added him to the hudson-jobadmin group. Andrei, can >>>> you check again? Might need to log out, not sure. >>>> >>>> On Tue, 7 May 2019 at 10:39, Ralph Goers <[email protected]> >>>> wrote: >>>>> >>>>> I just reviewed the Jenkins wiki which says you have to be in the >>>> appropriate LDAP group. Unfortunately, only the PMC chair has update >>>> authority in that tool so Matt will have to fix this for you. >>>>> >>>>> Ralph >>>>> >>>>>> On May 7, 2019, at 8:26 AM, Ralph Goers < >> [email protected]> >>>> wrote: >>>>>> >>>>>> At the very top of the menu on the left under the Jenkins logo you >>>> should see a “New Item” link. If you don’t then you don’t have the >> correct >>>> permissions. >>>>>> >>>>>> Ralph >>>>>> >>>>>>> On May 7, 2019, at 8:22 AM, Andrei Ivanov < >> [email protected]> >>>> wrote: >>>>>>> >>>>>>> I was able to log in, but I don't think I have enough >> permissions, I >>>> can >>>>>>> only see the jobs and run them, but not configure new items. >>>>>>> >>>>>>> On Tue, May 7, 2019 at 6:10 PM Matt Sicker <[email protected]> >> wrote: >>>>>>> >>>>>>>> I’m somewhat familiar with it if you need help. That may sound >> like >>>> an >>>>>>>> understatement, but alas, that’s the difference between being a >>>> developer >>>>>>>> and user of a product sometimes. Miss the forest for the trees >> so to >>>> say. >>>>>>>> >>>>>>>> >>>>>>>> On Tue, May 7, 2019 at 09:57, Ralph Goers < >>>> [email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Use your ASF credentials. If you aren’t aware of it, you can >> manage >>>> your >>>>>>>>> credentials at id.apache.org <http://id.apache.org/>. >>>>>>>>> >>>>>>>>> Ralph >>>>>>>>> >>>>>>>>>> On May 7, 2019, at 6:58 AM, Andrei Ivanov < >> [email protected] >>>>> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> I don't have that much experience with it, but I can try :-) >>>>>>>>>> >>>>>>>>>> What about Jenkins credentials/permissions? >>>>>>>>>> >>>>>>>>>> On Tue, May 7, 2019 at 3:14 PM Apache < >> [email protected]> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> If you are familiar with Jenkins you should just be able to >> create >>>>>>>> one. >>>>>>>>>>> >>>>>>>>>>> Ralph >>>>>>>>>>> >>>>>>>>>>>> On May 7, 2019, at 12:53 AM, Andrei Ivanov < >>>> [email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> I'm trying to see if there's a CI job defined for the Audit >>>> project. >>>>>>>>>>>> >>>>>>>>>>>> I'm looking at >> https://builds.apache.org/view/L/view/Logging/ >>>> and I >>>>>>>>>>> don't >>>>>>>>>>>> see one. >>>>>>>>>>>> >>>>>>>>>>>> If I am correct, how can one be defined? >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> Andrei >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>> Matt Sicker <[email protected]> >>>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Matt Sicker <[email protected]> >>>> >> >> >> >> -- >> Matt Sicker <[email protected]> >>
