Re: Process Jenkins DSL action
Hi Enrico, On Sat, Aug 15, 2020 at 8:31 AM Enrico Olivelli wrote: > Gavin, > thank you. > > Now I have this second problem, it looks like that in the new Jenkins > every Jenkins DSL script must be approved. > see > https://ci-hadoop.apache.org/job/BookKeeper/job/bookkeeper-seed/3/console > > I am not sure how can we make it work, the help reads "New or modified > scripts must either be approved by an Jenkins administrator before they can > be used or they must be run in the restricted sandbox." > I have approved all scripts waiting, please try again. > > > git config core.sparsecheckout # timeout=10 > > git checkout -f 7645cb839761b9dde6462c28a87a0d1c428bf5fa # timeout=10 > Commit message: "Bookie Client add quarantine ratio when error count exceed > threshold" > > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # > timeout=10 > Processing DSL script .test-infra/jenkins/job_bookkeeper_codecoverage.groovy > ERROR: script not yet approved for use > Finished: FAILURE > > > If I enable the "Groovy sandbox", then I see this second error > > Commit message: "Bookie Client add quarantine ratio when error count exceed > threshold" > > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # > timeout=10 > > ERROR: You must configure the DSL job to run as a specific user in order to > use the Groovy sandbox. > Finished: FAILURE > > > Thank you > > Enrico > > Il giorno ven 14 ago 2020 alle ore 20:57 Gavin McDonald < > gmcdon...@apache.org> ha scritto: > >> Hi Enrico! >> >> On Fri, Aug 14, 2020 at 8:41 PM Enrico Olivelli >> wrote: >> >> > Hi, >> > I am migrating Bookkeeper jobs and it looks like there is no 'Process >> DSL >> > actin' >> > >> > We have a seed job that creates all of the other jobs >> > >> > I have already created the new seed but actually it is useless. >> > >> > Any idea? >> > >> >> Right, so a part of this migration process involves finding out what >> plugins might be >> needed for Jobs, and installing them as we come across them. >> >> I just installed the Job DSL plugin and your Process DSL option should now >> be available for you. >> >> Let me know how you get on >> >> >> > Enrico >> > >> >> >> -- >> >> *Gavin McDonald* >> Systems Administrator >> ASF Infrastructure Team >> > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: Process Jenkins DSL action
Thank you Gavin, it looks like the script now has problems. I can fix them, but I don't know how can I make changes if you need to approve them every time. We were using Jenkins DSL in order to have Jenkins jobs configuration committed to git Do you think that enabling the Groovy sandbox would be a good idea? Enrico Il giorno sab 15 ago 2020 alle ore 13:15 Gavin McDonald < gmcdon...@apache.org> ha scritto: > Hi Enrico, > > > On Sat, Aug 15, 2020 at 8:31 AM Enrico Olivelli > wrote: > >> Gavin, >> thank you. >> >> Now I have this second problem, it looks like that in the new Jenkins >> every Jenkins DSL script must be approved. >> see >> https://ci-hadoop.apache.org/job/BookKeeper/job/bookkeeper-seed/3/console >> >> I am not sure how can we make it work, the help reads "New or modified >> scripts must either be approved by an Jenkins administrator before they can >> be used or they must be run in the restricted sandbox." >> > > I have approved all scripts waiting, please try again. > > >> >> > git config core.sparsecheckout # timeout=10 >> > git checkout -f 7645cb839761b9dde6462c28a87a0d1c428bf5fa # timeout=10 >> Commit message: "Bookie Client add quarantine ratio when error count exceed >> threshold" >> > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # >> timeout=10 >> Processing DSL script .test-infra/jenkins/job_bookkeeper_codecoverage.groovy >> ERROR: script not yet approved for use >> Finished: FAILURE >> >> >> If I enable the "Groovy sandbox", then I see this second error >> >> Commit message: "Bookie Client add quarantine ratio when error count exceed >> threshold" >> > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # >> timeout=10 >> >> ERROR: You must configure the DSL job to run as a specific user in order to >> use the Groovy sandbox. >> Finished: FAILURE >> >> >> Thank you >> >> Enrico >> >> Il giorno ven 14 ago 2020 alle ore 20:57 Gavin McDonald < >> gmcdon...@apache.org> ha scritto: >> >>> Hi Enrico! >>> >>> On Fri, Aug 14, 2020 at 8:41 PM Enrico Olivelli >>> wrote: >>> >>> > Hi, >>> > I am migrating Bookkeeper jobs and it looks like there is no 'Process >>> DSL >>> > actin' >>> > >>> > We have a seed job that creates all of the other jobs >>> > >>> > I have already created the new seed but actually it is useless. >>> > >>> > Any idea? >>> > >>> >>> Right, so a part of this migration process involves finding out what >>> plugins might be >>> needed for Jobs, and installing them as we come across them. >>> >>> I just installed the Job DSL plugin and your Process DSL option should >>> now >>> be available for you. >>> >>> Let me know how you get on >>> >>> >>> > Enrico >>> > >>> >>> >>> -- >>> >>> *Gavin McDonald* >>> Systems Administrator >>> ASF Infrastructure Team >>> >> > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team >
builds.a.o deadline extended by 1 week - now 22nd August
Hi All, There are still projects that haven't moved over to ci-builds and/or ci-hadoop. Whilst most of you have been able to do the right thing and move over by the initial deadline, some projects have not done so. Some of this may be due to credentials issues over the last week or so, or may simply have not not seen the messages over the last few weeks. So, I am offering a one time only extension of the deadline by 1 week, so those left now have until the 22nd August to complete their migrations. Those already on the new service, thank you and enjoy the new instance. I'll be moving more agents over today to the new master(s), leaving minimal agents on the old builds.a.o for those still there. -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: Process Jenkins DSL action
Using the sandbox is typically recommended as without it, the scripts can do anything an administrator can do. Usually you'd only disable it for limited scripts where you need to dig into internal Jenkins state, but those types of scripts are usually things like Jenkins init scripts that customize some settings and are configured by admins. Caveat: I haven't used JobDSL myself, so I'm not sure how useful that plugin is in the sandbox. On Sat, 15 Aug 2020 at 06:23, Enrico Olivelli wrote: > > Thank you Gavin, > it looks like the script now has problems. > I can fix them, but I don't know how can I make changes if you need to > approve them every time. > > We were using Jenkins DSL in order to have Jenkins jobs configuration > committed to git > > Do you think that enabling the Groovy sandbox would be a good idea? > > Enrico > > Il giorno sab 15 ago 2020 alle ore 13:15 Gavin McDonald < > gmcdon...@apache.org> ha scritto: > > > Hi Enrico, > > > > > > On Sat, Aug 15, 2020 at 8:31 AM Enrico Olivelli > > wrote: > > > >> Gavin, > >> thank you. > >> > >> Now I have this second problem, it looks like that in the new Jenkins > >> every Jenkins DSL script must be approved. > >> see > >> https://ci-hadoop.apache.org/job/BookKeeper/job/bookkeeper-seed/3/console > >> > >> I am not sure how can we make it work, the help reads "New or modified > >> scripts must either be approved by an Jenkins administrator before they can > >> be used or they must be run in the restricted sandbox." > >> > > > > I have approved all scripts waiting, please try again. > > > > > >> > >> > git config core.sparsecheckout # timeout=10 > >> > git checkout -f 7645cb839761b9dde6462c28a87a0d1c428bf5fa # timeout=10 > >> Commit message: "Bookie Client add quarantine ratio when error count > >> exceed threshold" > >> > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # > >> timeout=10 > >> Processing DSL script > >> .test-infra/jenkins/job_bookkeeper_codecoverage.groovy > >> ERROR: script not yet approved for use > >> Finished: FAILURE > >> > >> > >> If I enable the "Groovy sandbox", then I see this second error > >> > >> Commit message: "Bookie Client add quarantine ratio when error count > >> exceed threshold" > >> > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # > >> timeout=10 > >> > >> ERROR: You must configure the DSL job to run as a specific user in order > >> to use the Groovy sandbox. > >> Finished: FAILURE > >> > >> > >> Thank you > >> > >> Enrico > >> > >> Il giorno ven 14 ago 2020 alle ore 20:57 Gavin McDonald < > >> gmcdon...@apache.org> ha scritto: > >> > >>> Hi Enrico! > >>> > >>> On Fri, Aug 14, 2020 at 8:41 PM Enrico Olivelli > >>> wrote: > >>> > >>> > Hi, > >>> > I am migrating Bookkeeper jobs and it looks like there is no 'Process > >>> DSL > >>> > actin' > >>> > > >>> > We have a seed job that creates all of the other jobs > >>> > > >>> > I have already created the new seed but actually it is useless. > >>> > > >>> > Any idea? > >>> > > >>> > >>> Right, so a part of this migration process involves finding out what > >>> plugins might be > >>> needed for Jobs, and installing them as we come across them. > >>> > >>> I just installed the Job DSL plugin and your Process DSL option should > >>> now > >>> be available for you. > >>> > >>> Let me know how you get on > >>> > >>> > >>> > Enrico > >>> > > >>> > >>> > >>> -- > >>> > >>> *Gavin McDonald* > >>> Systems Administrator > >>> ASF Infrastructure Team > >>> > >> > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > -- Matt Sicker
Re: [ci-builds] GitHub credentials
You could potentially use a build strategy to only build PRs that contain one or more labels on the PR, and labels can only be added by committers by default. I've used this plugin at work recently for building an opt-in acceptance test pipeline: https://plugins.jenkins.io/github-label-filter/ On Fri, 14 Aug 2020 at 18:25, Chris Lambertus wrote: > > > > > On Aug 14, 2020, at 4:01 PM, Richard Eckart de Castilho > > wrote: > > > > Hi, > > > >> On 30. Jul 2020, at 05:42, Chris Lambertus wrote: > >> > >> There is no policy per-se, we have done this in the past, specifically for > >> repo:status tokens; > >> > >> Please create an infra jira ticket. Unfortunately, it’s an extremely > >> manual process on our end, and requires Infra to create and maintain an > >> account and password+token for each project, so it’s something we try to > >> avoid unless absolutely necessary. > > > > In which case would such a thing ever be "absolutely necessary"? > > If your project can justify the extreme need of an additional token because > your project has so many build requests that exceed the rate limits of the > asf-ci token Infra already provides, we'll evaluate it. We would prefer you > discuss the needs of your build with Infra so we can assess and allocate > resources as appropriate. > > > > > > However, I have come to find it very very convenient to be able to visit a > > PR and see how it fares, in particular since I like setting up repos to not > > permit merges unless the CI gives its thumbs up - which is of course also > > not absolutely necessary - but useful. > > > > Is there any chance there might be a more generic solution than using > > personal tokens or high-effort investment of INFRA to the problem of > > setting the commit status on GitHub from ci-builds in the near future? > > > > Cheers, > > > > -- Richard > -- Matt Sicker
Re: Process Jenkins DSL action
Il Sab 15 Ago 2020, 20:35 Matt Sicker ha scritto: > Using the sandbox is typically recommended as without it, the scripts > can do anything an administrator can do. My error with the sandbox is: ERROR: You must configure the DSL job to run as a specific user in order to use the Groovy sandbox I have found this guide: https://www.happycoders.eu/devops/jenkins-tutorial-implementing-seed-job/ If this configuration is not useful for other projects I could discuss on dev@ list to stop using Jenkins DSL and manually configure the jobs or switch to Jenkinsfile Enrico Usually you'd only disable it > for limited scripts where you need to dig into internal Jenkins state, > but those types of scripts are usually things like Jenkins init > scripts that customize some settings and are configured by admins. > > Caveat: I haven't used JobDSL myself, so I'm not sure how useful that > plugin is in the sandbox. > > On Sat, 15 Aug 2020 at 06:23, Enrico Olivelli wrote: > > > > Thank you Gavin, > > it looks like the script now has problems. > > I can fix them, but I don't know how can I make changes if you need to > > approve them every time. > > > > We were using Jenkins DSL in order to have Jenkins jobs configuration > > committed to git > > > > Do you think that enabling the Groovy sandbox would be a good idea? > > > > Enrico > > > > Il giorno sab 15 ago 2020 alle ore 13:15 Gavin McDonald < > > gmcdon...@apache.org> ha scritto: > > > > > Hi Enrico, > > > > > > > > > On Sat, Aug 15, 2020 at 8:31 AM Enrico Olivelli > > > wrote: > > > > > >> Gavin, > > >> thank you. > > >> > > >> Now I have this second problem, it looks like that in the new Jenkins > > >> every Jenkins DSL script must be approved. > > >> see > > >> > https://ci-hadoop.apache.org/job/BookKeeper/job/bookkeeper-seed/3/console > > >> > > >> I am not sure how can we make it work, the help reads "New or modified > > >> scripts must either be approved by an Jenkins administrator before > they can > > >> be used or they must be run in the restricted sandbox." > > >> > > > > > > I have approved all scripts waiting, please try again. > > > > > > > > >> > > >> > git config core.sparsecheckout # timeout=10 > > >> > git checkout -f 7645cb839761b9dde6462c28a87a0d1c428bf5fa # > timeout=10 > > >> Commit message: "Bookie Client add quarantine ratio when error count > exceed threshold" > > >> > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # > timeout=10 > > >> Processing DSL script > .test-infra/jenkins/job_bookkeeper_codecoverage.groovy > > >> ERROR: script not yet approved for use > > >> Finished: FAILURE > > >> > > >> > > >> If I enable the "Groovy sandbox", then I see this second error > > >> > > >> Commit message: "Bookie Client add quarantine ratio when error count > exceed threshold" > > >> > git rev-list --no-walk 7645cb839761b9dde6462c28a87a0d1c428bf5fa # > timeout=10 > > >> > > >> ERROR: You must configure the DSL job to run as a specific user in > order to use the Groovy sandbox. > > >> Finished: FAILURE > > >> > > >> > > >> Thank you > > >> > > >> Enrico > > >> > > >> Il giorno ven 14 ago 2020 alle ore 20:57 Gavin McDonald < > > >> gmcdon...@apache.org> ha scritto: > > >> > > >>> Hi Enrico! > > >>> > > >>> On Fri, Aug 14, 2020 at 8:41 PM Enrico Olivelli > > > >>> wrote: > > >>> > > >>> > Hi, > > >>> > I am migrating Bookkeeper jobs and it looks like there is no > 'Process > > >>> DSL > > >>> > actin' > > >>> > > > >>> > We have a seed job that creates all of the other jobs > > >>> > > > >>> > I have already created the new seed but actually it is useless. > > >>> > > > >>> > Any idea? > > >>> > > > >>> > > >>> Right, so a part of this migration process involves finding out what > > >>> plugins might be > > >>> needed for Jobs, and installing them as we come across them. > > >>> > > >>> I just installed the Job DSL plugin and your Process DSL option > should > > >>> now > > >>> be available for you. > > >>> > > >>> Let me know how you get on > > >>> > > >>> > > >>> > Enrico > > >>> > > > >>> > > >>> > > >>> -- > > >>> > > >>> *Gavin McDonald* > > >>> Systems Administrator > > >>> ASF Infrastructure Team > > >>> > > >> > > > > > > -- > > > > > > *Gavin McDonald* > > > Systems Administrator > > > ASF Infrastructure Team > > > > > > > -- > Matt Sicker >
Re: Who has not migrated yet?
Would you please create a Tuweni folder? Thank you! Antoine > On Aug 14, 2020, at 1:30 PM, P. Ottlinger wrote: > > Hi Gav, > > hopefully all of Creadur's projects are migrated . puh - > I created a new infra ticket > (https://issues.apache.org/jira/browse/INFRA-20688) to get some of the > older projects moved over to Gitbox, but all builds seem to work: > > https://ci-builds.apache.org/job/Creadur/ > > Thanks for the reminder! > > Phil
