Re: Jenkins job on ariatosca-website failing after gitbox transition
Jenkins is back up, and the website has been built. John On Tue, Dec 5, 2017 at 12:13 PM John D. Ament wrote: > Ok, so there's a couple of issues. > Jenkins access is limited to those in a certain group, since its a single > jenkins instance for all projects without limited privileges. Right now I > have access to manage jobs in jenkins, but would be happy to add others who > need it. > > The jenkins job is something I set up, based on a cookie cutter I use to > automate website builds (jenkins job configuration for me is like bonsai > trimming). The job just executes the shell script in the repo. I just > need to repoint to gitbox to reenable the job, but right now jenkins is > down. When it comes back I'll get the job going again. > > I've assigned myself the infra ticket, please try to avoid sending them > issues that we should be able to fix ourselves (and discussing it on list > helps identify who or what can/should be fixed). > > John > > > On Tue, Dec 5, 2017 at 12:05 PM Thomas Nadeau > wrote: > >> i just realized that after the switch to gitbox, pushed PRs to the >> ariatosca-website repo are not triggering the Jenkins job which results in >> the site being re-generated and published to ariatosca.org >> >> >> [5:45] >> so my PR yesterday and @Miguel Jiménez’s from today while merged, are not >> yet reflected >> >> >> smarthi [5:49 PM] >> on other projects like OpenNLP, Flink, Beam etc… there’s a buildbot setup >> that triggers a build and regenerates the website >> >> >> Thomas Nadeau [5:54 PM] >> thats good, but I don't really want to set up a different automation >> trigger/builder if I can help it :sunglasses: >> >> >> [5:54] >> i did look into buildbot earlier before I knew there was an apache infra >> jenkins job setup >> >> >> [5:55] >> I suspect that its just not triggered properly because the triggers need >> to >> come from github now instead of apache git >> >> >> [5:55] >> so token generator is a one button situation on github, so infra prob >> needs >> to have a committer generate the token and the replace the old one with >> that >> >> >> smarthi [6:00 PM] >> well u can file Infra ticket to enable buildbot for aria-site >> >> >> Thomas Nadeau [6:04 PM] >> how does one file a ticket? >> >> [6:05] >> just email to infra@apache? >> >> >> smarthi [6:06 PM] >> jira >> >> >> Thomas Nadeau [6:06 PM] >> ah like the gitbox one >> >> >> smarthi [6:07 PM] >> yes >> >> >> Thomas Nadeau [6:08 PM] >> ill fire one up now >> >> >> johndament [6:23 PM] >> i can fix the jenkins job >> >
Re: Jenkins job on ariatosca-website failing after gitbox transition
Ok, so there's a couple of issues. Jenkins access is limited to those in a certain group, since its a single jenkins instance for all projects without limited privileges. Right now I have access to manage jobs in jenkins, but would be happy to add others who need it. The jenkins job is something I set up, based on a cookie cutter I use to automate website builds (jenkins job configuration for me is like bonsai trimming). The job just executes the shell script in the repo. I just need to repoint to gitbox to reenable the job, but right now jenkins is down. When it comes back I'll get the job going again. I've assigned myself the infra ticket, please try to avoid sending them issues that we should be able to fix ourselves (and discussing it on list helps identify who or what can/should be fixed). John On Tue, Dec 5, 2017 at 12:05 PM Thomas Nadeau wrote: > i just realized that after the switch to gitbox, pushed PRs to the > ariatosca-website repo are not triggering the Jenkins job which results in > the site being re-generated and published to ariatosca.org > > > [5:45] > so my PR yesterday and @Miguel Jiménez’s from today while merged, are not > yet reflected > > > smarthi [5:49 PM] > on other projects like OpenNLP, Flink, Beam etc… there’s a buildbot setup > that triggers a build and regenerates the website > > > Thomas Nadeau [5:54 PM] > thats good, but I don't really want to set up a different automation > trigger/builder if I can help it :sunglasses: > > > [5:54] > i did look into buildbot earlier before I knew there was an apache infra > jenkins job setup > > > [5:55] > I suspect that its just not triggered properly because the triggers need to > come from github now instead of apache git > > > [5:55] > so token generator is a one button situation on github, so infra prob needs > to have a committer generate the token and the replace the old one with > that > > > smarthi [6:00 PM] > well u can file Infra ticket to enable buildbot for aria-site > > > Thomas Nadeau [6:04 PM] > how does one file a ticket? > > [6:05] > just email to infra@apache? > > > smarthi [6:06 PM] > jira > > > Thomas Nadeau [6:06 PM] > ah like the gitbox one > > > smarthi [6:07 PM] > yes > > > Thomas Nadeau [6:08 PM] > ill fire one up now > > > johndament [6:23 PM] > i can fix the jenkins job >
Jenkins job on ariatosca-website failing after gitbox transition
i just realized that after the switch to gitbox, pushed PRs to the ariatosca-website repo are not triggering the Jenkins job which results in the site being re-generated and published to ariatosca.org [5:45] so my PR yesterday and @Miguel Jiménez’s from today while merged, are not yet reflected smarthi [5:49 PM] on other projects like OpenNLP, Flink, Beam etc… there’s a buildbot setup that triggers a build and regenerates the website Thomas Nadeau [5:54 PM] thats good, but I don't really want to set up a different automation trigger/builder if I can help it :sunglasses: [5:54] i did look into buildbot earlier before I knew there was an apache infra jenkins job setup [5:55] I suspect that its just not triggered properly because the triggers need to come from github now instead of apache git [5:55] so token generator is a one button situation on github, so infra prob needs to have a committer generate the token and the replace the old one with that smarthi [6:00 PM] well u can file Infra ticket to enable buildbot for aria-site Thomas Nadeau [6:04 PM] how does one file a ticket? [6:05] just email to infra@apache? smarthi [6:06 PM] jira Thomas Nadeau [6:06 PM] ah like the gitbox one smarthi [6:07 PM] yes Thomas Nadeau [6:08 PM] ill fire one up now johndament [6:23 PM] i can fix the jenkins job