Yes, I agree.  Sorry, the branch was just for testing until I get it
right.  Ideally in the end all branches have 1 or more Jenkinsfiles.

Thanks for the link to that article Josh.  I honestly don't understand what
yetus gives you and I think I see a fairly simple way to make tests run in
docker with just a Jenkinsfile so I wasn't going to add complexity yet.

Thanks for the input.

Mike

On Tue, Feb 5, 2019 at 3:40 PM Josh Elser <[email protected]> wrote:

> I feel like trying to put the Jenkinsfile in a separate branch might
> cause more headache than it's worth.
>
> Happen to stumble on AW's write-up on a similar subject?
>
> https://effectivemachines.com/2019/01/24/using-apache-yetus-with-jenkins-and-github-part-1/
>
> On 2/5/19 2:35 PM, Michael Wall wrote:
> > I think I see a path forward using a Jenkinsfile.  Please comment on this
> > plan if something doesn't make sense or someone does not agree.
> >
> > 1 - Create a new branch off master called jenkinsfile or such and add a
> > jenkinsfile that runs only unit tests but does it in docker.
> > 2 - Create a new job on jenkins.revelc.net that only builds that branch
> > 3 - Iterate on the jenkinsfile until it works cleanly
> > 4 - Reconfigure the Accumulo-Master job on builds.apache.org to use the
> > Jenkinsfile
> >
> >  From there it will hopefully make sense about what to do next.  Maybe a
> > Jenkinsfile-IT or something.
> >
> > Christopher, looks like I already have permission on jenkins.revelc.net
> to
> > make jobs.
> >
> > Thanks
> >
> > Mike
> >
> > On Sun, Jan 6, 2019 at 10:32 PM Christopher <[email protected]> wrote:
> >
> >> I've seen similar problems with processes left behind on my own
> >> Jenkins instance, but my solution is to periodically log in and nuke
> >> the processes, and even occasionally reboot the instance. I don't
> >> think these options are available to us on builds.apache.org, because
> >> we don't have direct access to them. I'm also not sure why it happens
> >> or why Jenkins doesn't properly clean up child processes leftover from
> >> no-longer-running builds it launched.
> >>
> >> One suggestion was to run in Docker, but I don't know how to do that.
> >> I attempted to do it that way, and got as far as Jenkins running and
> >> connecting to the Docker instance, but the Maven versions available to
> >> configure the Maven build does not seem to match what's inside the
> >> Docker container and the job quickly fails.... so it's not clear how
> >> to do a Maven build in Jenkins with Docker given the options INFRA has
> >> made available to us. Perhaps if they had instructions, or an example
> >> Maven job we could model our jobs after?
> >>
> >>
> >> On Sun, Jan 6, 2019 at 9:34 PM Michael Wall <[email protected]> wrote:
> >>>
> >>> Anyone look at this yet?
> >>>
> >>
> https://lists.apache.org/thread.html/e78b1b8ccaf11eb5cb557ec29d3208c3fec0450fd2b908b3f7922c56@%3Cbuilds.apache.org%3E
> >>>
> >>> Not sure who even has karma to do anything here
> >>> https://builds.apache.org/view/A/view/Accumulo/
> >>
> >
>

Reply via email to