Re: A jenkins plugin is required to be installed: github pull request builder
Hi Bayer, The blogs instruction is very helpful, I'll try to create a job according to it. Thank you very much. Michael On Sat, Dec 12, 2015 at 2:30 AM, Andrew Bayer wrote: > Hi - > > We already have a GitHub PR builder plugin installed - see > https://blogs.apache.org/infra/entry/github_pull_request_builds_now, and > https://builds.apache.org/job/cloudstack-pull-analysis/configure for an > example of how to configure to use it. > > A. > > On Fri, Dec 11, 2015 at 12:41 PM, Michael Wu wrote: > >> Hi administrators of Jenkins, >> >> I'm using the jenkins service at builds.apache.org for incubator-eagle >> project to make builds, and I'd like to integrate it with github repo to >> automatically trigger builds when new pull requests comes. This requires a >> plugin: "github pull request builder", be installed to the Jenkins and >> configured correctly. Could you please help install it? Thanks. >> >> BTW, paste the official wiki page of the plugin for your reference. >> >> Michael >> > >
Re: A jenkins plugin is required to be installed: github pull request builder
Hi Andrew, Following the guide, configured new job, and it can be hooked with incubator-eagle github. However, I still encounter an issue for configuring the CI job to clone from git repo with either ssh: or https: protocol, the job's console is at https://builds.apache.org/job/incubator-eagle-pr-reviewer/1/console. The issue is, 1. if I follow the guide to set git repo url as g...@github.com:apache/incubator-eagle.git, it shows an error message as captured in the attached screenshot, seeming github doesn't hold ssh public key for the jenkins server. 2. Otherwise if I set the git repo url as https://github.com/apache/incubator-eagle.git, as we can see in the job's console output, the job cannot clone from it. Could you please give me a further guide on how to deal with such problem? Thanks a lot! Michael On Mon, Dec 14, 2015 at 12:13 PM, Michael Wu wrote: > Hi Bayer, > > The blogs instruction is very helpful, I'll try to create a job according > to it. Thank you very much. > > Michael > > On Sat, Dec 12, 2015 at 2:30 AM, Andrew Bayer > wrote: > >> Hi - >> >> We already have a GitHub PR builder plugin installed - see >> https://blogs.apache.org/infra/entry/github_pull_request_builds_now, and >> https://builds.apache.org/job/cloudstack-pull-analysis/configure for an >> example of how to configure to use it. >> >> A. >> >> On Fri, Dec 11, 2015 at 12:41 PM, Michael Wu wrote: >> >>> Hi administrators of Jenkins, >>> >>> I'm using the jenkins service at builds.apache.org for incubator-eagle >>> project to make builds, and I'd like to integrate it with github repo to >>> automatically trigger builds when new pull requests comes. This requires a >>> plugin: "github pull request builder", be installed to the Jenkins and >>> configured correctly. Could you please help install it? Thanks. >>> >>> BTW, paste the official wiki page of the plugin for your reference. >>> >>> Michael >>> >> >> >
Re: A jenkins plugin is required to be installed: github pull request builder
xecutor.java:381) Caused by: hudson.plugins.git.GitException: Command "git init /Users/jenkins/jenkins-home/workspace/incubator-eagle-pr-reviewer" returned status code 1: stdout: stderr: xcode-select: error: no developer tools were found at '/Applications/Xcode.app', and no install could be requested (perhaps no UI is present), please install manually from 'developer.apple.com'. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1640) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1616) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1612) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1254) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute(CliGitAPIImpl.java:604) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ERROR: null Retrying after 10 seconds ** Thanks. Michael On Thu, Dec 24, 2015 at 5:10 AM, Andrew Bayer wrote: > Use the git://github.com/apache/incubator-eagle.git URL. > > A. > > On Wed, Dec 23, 2015 at 11:00 AM, Michael Wu wrote: > >> Hi Andrew, >> >> Following the guide, configured new job, and it can be hooked with >> incubator-eagle github. However, I still encounter an issue for configuring >> the CI job to clone from git repo with either ssh: or https: protocol, the >> job's console is at >> https://builds.apache.org/job/incubator-eagle-pr-reviewer/1/console. >> >> The issue is, >> 1. if I follow the guide to set git repo url as >> g...@github.com:apache/incubator-eagle.git, >> it shows an error message as captured in the attached screenshot, seeming >> github doesn't hold ssh public key for the jenkins server. >> 2. Otherwise if I set the git repo url as >> https://github.com/apache/incubator-eagle.git, as we can see in the >> job's console output, the job cannot clone from it. >> >> Could you please give me a further guide on how to deal with such >> problem? Thanks a lot! >> >> Michael >> >> >> On Mon, Dec 14, 2015 at 12:13 PM, Michael Wu wrote: >> >>> Hi Bayer, >>> >>> The blogs instruction is very helpful, I'll try to create a job >>> according to it. Thank you very much. >>> >>> Michael >>> >>> On Sat, Dec 12, 2015 at 2:30 AM, Andrew Bayer >>> wrote: >>> >>>> Hi - >>>> >>>> We already have a GitHub PR builder plugin installed - see >>>> https://blogs.apache.org/infra/entry/github_pull_request_builds_now, >>>> and https://builds.apache.org/job/cloudstack-pull-analysis/configure >>>> for an example of how to configure to use it. >>>> >>>> A. >>>> >>>> On Fri, Dec 11, 2015 at 12:41 PM, Michael Wu >>>> wrote: >>>> >>>>> Hi administrators of Jenkins, >>>>> >>>>> I'm using the jenkins service at builds.apache.org for >>>>> incubator-eagle project to make builds, and I'd like to integrate it with >>>>> github repo to automatically trigger builds when new pull requests comes. >>>>> This requires a plugin: "github pull request builder", be installed to the >>>>> Jenkins and configured correctly. Could you please help install it? >>>>> Thanks. >>>>> >>>>> BTW, paste the official wiki page of the plugin for your reference. >>>>> >>>>> Michael >>>>> >>>> >>>> >>> >> >
Re: A jenkins plugin is required to be installed: github pull request builder
BTW, in the workspace title "*Workspace of incubator-eagle-pr-reviewer on mac-mini-1*", I find the job seem to be running on "mac-mini-1", could it be there is some wares missed on that slave? Please help! Thanks. Michael On Thu, Dec 24, 2015 at 9:30 AM, Michael Wu wrote: > Andrew, > > I tried but the job still failed and the console-log seemed to remain the > same, could you please help take a look at it? This issue has failed the > checks for any pull request of project incubator-eagle. > The job is at https://builds.apache.org/job/incubator-eagle-pr-reviewer > and I paste the console-log below: > ** > > Building remotely on mac-mini-1 > <https://builds.apache.org/computer/mac-mini-1> (osx mac) in workspace > /Users/jenkins/jenkins-home/workspace/incubator-eagle-pr-reviewer > Cloning the remote Git repository > Cloning repository git://github.com/apache/incubator-eagle.git > > git init /Users/jenkins/jenkins-home/workspace/incubator-eagle-pr-reviewer > # timeout=10 > ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException > <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>: > Could not init > /Users/jenkins/jenkins-home/workspace/incubator-eagle-pr-reviewer > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute(CliGitAPIImpl.java:606) > > <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute&entity=method> > at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462) > > <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute&entity=method> > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) > > <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call&entity=method> > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) > > <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call&entity=method> > at hudson.remoting.UserRequest.perform(UserRequest.java:121) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> > at hudson.remoting.UserRequest.perform(UserRequest.java:49) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> > at hudson.remoting.Request$2.run(Request.java:326) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request$2.run&entity=method> > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) > > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.InterceptingExecutorService$1.call&entity=method> > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.FutureTask.run&entity=method> > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor.runWorker&entity=method> > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor$Worker.run&entity=method> > at java.lang.Thread.run(Thread.java:745) > <http://stacktrace.jenkins-ci.org/search/?query=java.lang.Thread.run&entity=method> > at ..remote call to mac-mini-1(Native Method) > at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) > at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) > at hudson.remoting.Channel.call(Channel.java:778) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) > at sun.reflect.GeneratedMethodAccessor621.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) > at com.sun.proxy.$Proxy151.execute(Unknown Source) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1003) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java
Re: A jenkins plugin is required to be installed: github pull request builder
Cool, thanks a lot, Andrew! BTW, is there any way to rebuild the job for a specific pull request? Or say, how can we re-trigger a build if the CI status has been marked as "All checks have failed", please? On Thu, Dec 24, 2015 at 9:38 AM, Andrew Bayer wrote: > That was something wrong with the Mac mini slave, which also was > misconfigured to allow any job to run on it, not just ones explicitly tied > to it. I fixed that and re ran your build and it worked fine. > > > On Wednesday, December 23, 2015, Michael Wu wrote: > >> Andrew, >> >> I tried but the job still failed and the console-log seemed to remain the >> same, could you please help take a look at it? This issue has failed the >> checks for any pull request of project incubator-eagle. >> The job is at https://builds.apache.org/job/incubator-eagle-pr-reviewer >> and I paste the console-log below: >> ** >> >> Building remotely on mac-mini-1 >> <https://builds.apache.org/computer/mac-mini-1> (osx mac) in workspace >> /Users/jenkins/jenkins-home/workspace/incubator-eagle-pr-reviewer >> Cloning the remote Git repository >> Cloning repository git://github.com/apache/incubator-eagle.git >> > git init >> /Users/jenkins/jenkins-home/workspace/incubator-eagle-pr-reviewer # >> timeout=10 >> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException >> <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>: >> Could not init >> /Users/jenkins/jenkins-home/workspace/incubator-eagle-pr-reviewer >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute(CliGitAPIImpl.java:606) >> >> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute&entity=method> >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462) >> >> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute&entity=method> >> at >> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) >> >> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call&entity=method> >> at >> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) >> >> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call&entity=method> >> at hudson.remoting.UserRequest.perform(UserRequest.java:121) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> >> at hudson.remoting.UserRequest.perform(UserRequest.java:49) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> >> at hudson.remoting.Request$2.run(Request.java:326) >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request$2.run&entity=method> >> at >> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) >> >> <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.InterceptingExecutorService$1.call&entity=method> >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.FutureTask.run&entity=method> >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> >> <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor.runWorker&entity=method> >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> >> <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor$Worker.run&entity=method> >> at java.lang.Thread.run(Thread.java:745) >> <http://stacktrace.jenkins-ci.org/search/?query=java.lang.Thread.run&entity=method> >> at ..remote call to mac-mini-1(Native Method) >> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) >> at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) >> at hudson.remoting.Channel.call(Channel.java:778) >> at >> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) >> at sun.reflect.Generated
[Jenkins Plugin Required] Could you please help install "Embeddable Build Status Plugin" to the Jenkins servers?
Hi jenkins-admin team, I'm a contributor of incubator-eagle project and we are using builds.apache.org to build CI jobs for the project. Recently, an interesting Jenkins plugin attracted our appeals and was considered helpful for all CI jobs linked with github repos to set build status icon in the main pages, its name is "Embeddable Build Status Plugin", whose official WIKI page is at: https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin. Could you please help evaluate the plugin and install it on servers if it's worthy doing? Thanks. Michael
Re: [Jenkins Plugin Required] Could you please help install "Embeddable Build Status Plugin" to the Jenkins servers?
Hi Andrew, Thanks for your quick response. Ticket INFRA-11006 <https://issues.apache.org/jira/browse/INFRA-11006> has been created. Michael On Mon, Dec 28, 2015 at 7:42 PM, Andrew Bayer wrote: > Please open INFRA JIRAs for this sort of thing. > > > On Monday, December 28, 2015, Michael Wu wrote: > >> Hi jenkins-admin team, >> >> I'm a contributor of incubator-eagle project and we are using >> builds.apache.org to build CI jobs for the project. Recently, an >> interesting Jenkins plugin attracted our appeals and was considered helpful >> for all CI jobs linked with github repos to set build status icon in the >> main pages, its name is "Embeddable Build Status Plugin", whose official >> WIKI page is at: >> https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin >> . >> >> Could you please help evaluate the plugin and install it on servers if >> it's worthy doing? Thanks. >> >> Michael >> >
[BuildBot Registry] Could anyone of infras team please kindly help setup the CI for incubator-eagle?
Hi Builds Team, I'm a contributor of incubator-eagle group, we met the needs to ask Buildbot to build and test our website branch and have available for display at ci.apache.org/projects/eagle/, could anyone kindly help guide me what steps we should follow to make it, please? A jira ticket for this task was filed on Api. 25th, and we're still eagerly waiting for further instructions. The jira ticket is at: https://issues.apache.org/jira/browse/INFRA-11738 It'll be highly appreciated if anyone can help us on it. Best regards, Michael
Re: [BuildBot Registry] Could anyone of infras team please kindly help setup the CI for incubator-eagle?
Gav, Really appreciate your response. Now that some information of the project has been updated, I'd like to list them here for your reference (anything missed for you to continue, please do let me know). Also, I've got some questions for the working flow of this build service, I'll list them at the bottom, it'll be appreciated if you are convenient to give some comments. Project information: *** *Project name:* incubator-eagle *Project github repo:* https://github.com/apache/incubator-eagle *Expected access url after builds:* https://ci.apache.org/projects/eagle/ *Documentation branch:* master *Containing folder in project:* incubator-eagle/eagle-docs/ *Site content generating tool:* MkDocs (http://www.mkdocs.org/) *** Remaining questions: 1. After you setup auto-jobs for building this project, will we get the access to manage the job by ourselves as future needs come across? E.g. trigger new builds, modify configuration of the job, etc? 2. Is there any guide materials for manipulating the builds as a maintainer? 3. Suppose we have the files in eagle-docs evolve as the version of the project moves forward, what shall be the mechanism for keeping different version docs accessable? Could it be adding version-info in the uri, i.e. ci.apache.org/project/eagle/*v1.0* (maybe some other formats)? Thank you very much! Best Regards, Michael On Fri, May 13, 2016 at 3:39 PM, Gav wrote: > I will work on it tomorrow morning > > Gav... > > On Thu, May 12, 2016 at 10:24 PM, Michael Wu wrote: > > > Hi Builds Team, > > > > I'm a contributor of incubator-eagle group, we met the needs to > > ask Buildbot to build and test our website branch and have available for > > display at ci.apache.org/projects/eagle/, could anyone kindly help guide > > me > > what steps we should follow to make it, please? > > > > A jira ticket for this task was filed on Api. 25th, and we're still > eagerly > > waiting for further instructions. The jira ticket is at: > > https://issues.apache.org/jira/browse/INFRA-11738 > > > > It'll be highly appreciated if anyone can help us on it. > > > > Best regards, > > Michael > > >
Re: [BuildBot Registry] Could anyone of infras team please kindly help setup the CI for incubator-eagle?
Hi Gav, Is there any progress we get on this, please? We're eagerly waiting for response, what further we can provide, please feel free to let me know. Thanks! Michael On Fri, May 13, 2016 at 5:08 PM, Michael Wu wrote: > Gav, > > Really appreciate your response. Now that some information of the project > has been updated, I'd like to list them here for your reference (anything > missed for you to continue, please do let me know). Also, I've got some > questions for the working flow of this build service, I'll list them at the > bottom, it'll be appreciated if you are convenient to give some comments. > > Project information: > *** > *Project name:* incubator-eagle > *Project github repo:* > https://github.com/apache/incubator-eagle > *Expected access url after builds:* > https://ci.apache.org/projects/eagle/ > *Documentation branch:* master > *Containing folder in project:* incubator-eagle/eagle-docs/ > *Site content generating tool:* MkDocs (http://www.mkdocs.org/) > *** > > Remaining questions: > 1. After you setup auto-jobs for building this project, will we get the > access to manage the job by ourselves as future needs come across? E.g. > trigger new builds, modify configuration of the job, etc? > 2. Is there any guide materials for manipulating the builds as a > maintainer? > 3. Suppose we have the files in eagle-docs evolve as the version of the > project moves forward, what shall be the mechanism for keeping different > version docs accessable? Could it be adding version-info in the uri, i.e. > ci.apache.org/project/eagle/*v1.0* (maybe some other formats)? > > > Thank you very much! > > Best Regards, > Michael > > On Fri, May 13, 2016 at 3:39 PM, Gav wrote: > >> I will work on it tomorrow morning >> >> Gav... >> >> On Thu, May 12, 2016 at 10:24 PM, Michael Wu wrote: >> >> > Hi Builds Team, >> > >> > I'm a contributor of incubator-eagle group, we met the needs to >> > ask Buildbot to build and test our website branch and have available for >> > display at ci.apache.org/projects/eagle/, could anyone kindly help >> guide >> > me >> > what steps we should follow to make it, please? >> > >> > A jira ticket for this task was filed on Api. 25th, and we're still >> eagerly >> > waiting for further instructions. The jira ticket is at: >> > https://issues.apache.org/jira/browse/INFRA-11738 >> > >> > It'll be highly appreciated if anyone can help us on it. >> > >> > Best regards, >> > Michael >> > >> > >
Re: [BuildBot Registry] Could anyone of infras team please kindly help setup the CI for incubator-eagle?
Hi guys, Could anyone from builds and infra group kindly help on this requirement? If it's a tricky job, is it possible just let me know what information of the project I shall provide or what step I shall follow? Really appreciated! Michael On Wed, May 18, 2016 at 10:14 AM, Michael Wu wrote: > Hi Gav, > > Is there any progress we get on this, please? We're eagerly waiting for > response, what further we can provide, please feel free to let me know. > Thanks! > > Michael > > On Fri, May 13, 2016 at 5:08 PM, Michael Wu wrote: > >> Gav, >> >> Really appreciate your response. Now that some information of the project >> has been updated, I'd like to list them here for your reference (anything >> missed for you to continue, please do let me know). Also, I've got some >> questions for the working flow of this build service, I'll list them at the >> bottom, it'll be appreciated if you are convenient to give some comments. >> >> Project information: >> *** >> *Project name:* incubator-eagle >> *Project github repo:* >> https://github.com/apache/incubator-eagle >> *Expected access url after builds:* >> https://ci.apache.org/projects/eagle/ >> *Documentation branch:* master >> *Containing folder in project:* incubator-eagle/eagle-docs/ >> *Site content generating tool:* MkDocs (http://www.mkdocs.org/) >> *** >> >> Remaining questions: >> 1. After you setup auto-jobs for building this project, will we get the >> access to manage the job by ourselves as future needs come across? E.g. >> trigger new builds, modify configuration of the job, etc? >> 2. Is there any guide materials for manipulating the builds as a >> maintainer? >> 3. Suppose we have the files in eagle-docs evolve as the version of the >> project moves forward, what shall be the mechanism for keeping different >> version docs accessable? Could it be adding version-info in the uri, i.e. >> ci.apache.org/project/eagle/*v1.0* (maybe some other formats)? >> >> >> Thank you very much! >> >> Best Regards, >> Michael >> >> On Fri, May 13, 2016 at 3:39 PM, Gav wrote: >> >>> I will work on it tomorrow morning >>> >>> Gav... >>> >>> On Thu, May 12, 2016 at 10:24 PM, Michael Wu wrote: >>> >>> > Hi Builds Team, >>> > >>> > I'm a contributor of incubator-eagle group, we met the needs to >>> > ask Buildbot to build and test our website branch and have available >>> for >>> > display at ci.apache.org/projects/eagle/, could anyone kindly help >>> guide >>> > me >>> > what steps we should follow to make it, please? >>> > >>> > A jira ticket for this task was filed on Api. 25th, and we're still >>> eagerly >>> > waiting for further instructions. The jira ticket is at: >>> > https://issues.apache.org/jira/browse/INFRA-11738 >>> > >>> > It'll be highly appreciated if anyone can help us on it. >>> > >>> > Best regards, >>> > Michael >>> > >>> >> >> >
Re: [BuildBot Registry] Could anyone of infras team please kindly help setup the CI for incubator-eagle?
Paste the ticket link of this requirement for reference: https://issues.apache.org/jira/browse/INFRA-11738 Details could also be found in previous emails of this thread. Thanks. On Fri, May 20, 2016 at 4:32 PM, Michael Wu wrote: > Hi guys, > > Could anyone from builds and infra group kindly help on this requirement? > If it's a tricky job, is it possible just let me know what information of > the project I shall provide or what step I shall follow? > > Really appreciated! > > Michael > > On Wed, May 18, 2016 at 10:14 AM, Michael Wu wrote: > >> Hi Gav, >> >> Is there any progress we get on this, please? We're eagerly waiting for >> response, what further we can provide, please feel free to let me know. >> Thanks! >> >> Michael >> >> On Fri, May 13, 2016 at 5:08 PM, Michael Wu wrote: >> >>> Gav, >>> >>> Really appreciate your response. Now that some information of the >>> project has been updated, I'd like to list them here for your reference >>> (anything missed for you to continue, please do let me know). Also, I've >>> got some questions for the working flow of this build service, I'll list >>> them at the bottom, it'll be appreciated if you are convenient to give some >>> comments. >>> >>> Project information: >>> *** >>> *Project name:* incubator-eagle >>> *Project github repo:* >>> https://github.com/apache/incubator-eagle >>> *Expected access url after builds:* >>> https://ci.apache.org/projects/eagle/ >>> *Documentation branch:* master >>> *Containing folder in project:* incubator-eagle/eagle-docs/ >>> *Site content generating tool:* MkDocs (http://www.mkdocs.org/) >>> *** >>> >>> Remaining questions: >>> 1. After you setup auto-jobs for building this project, will we get the >>> access to manage the job by ourselves as future needs come across? E.g. >>> trigger new builds, modify configuration of the job, etc? >>> 2. Is there any guide materials for manipulating the builds as a >>> maintainer? >>> 3. Suppose we have the files in eagle-docs evolve as the version of the >>> project moves forward, what shall be the mechanism for keeping different >>> version docs accessable? Could it be adding version-info in the uri, i.e. >>> ci.apache.org/project/eagle/*v1.0* (maybe some other formats)? >>> >>> >>> Thank you very much! >>> >>> Best Regards, >>> Michael >>> >>> On Fri, May 13, 2016 at 3:39 PM, Gav wrote: >>> >>>> I will work on it tomorrow morning >>>> >>>> Gav... >>>> >>>> On Thu, May 12, 2016 at 10:24 PM, Michael Wu >>>> wrote: >>>> >>>> > Hi Builds Team, >>>> > >>>> > I'm a contributor of incubator-eagle group, we met the needs to >>>> > ask Buildbot to build and test our website branch and have available >>>> for >>>> > display at ci.apache.org/projects/eagle/, could anyone kindly help >>>> guide >>>> > me >>>> > what steps we should follow to make it, please? >>>> > >>>> > A jira ticket for this task was filed on Api. 25th, and we're still >>>> eagerly >>>> > waiting for further instructions. The jira ticket is at: >>>> > https://issues.apache.org/jira/browse/INFRA-11738 >>>> > >>>> > It'll be highly appreciated if anyone can help us on it. >>>> > >>>> > Best regards, >>>> > Michael >>>> > >>>> >>> >>> >> >
