Hi VCL community, I just created the following job [1] on the new build environment with the configuration to build the VCL website from the vcl-site repo. This is needed because builds.a.o will be turned off August 22nd.
The only thing left to do is for a committer to review & merge the pull request I created [2]. This puts the website deployment into version control instead of a Jenkins job. Happy to help! Roy [1] https://ci-builds.apache.org/job/VCL/job/site/ [2] https://github.com/apache/vcl-site/pull/4 On 2020/07/25 10:58:30, Roy Lenferink <rlenfer...@apache.org> wrote: > To follow-up on this; I put the exact steps in the pull-request to make it go > as smooth as possible > https://github.com/apache/vcl-site/pull/4#issuecomment-663841783 > > This way it should be fairly easy to setup the new job. > > On 2020/07/20 16:12:51, Roy Lenferink <rlenfer...@apache.org> wrote: > > Hi all, > > > > The builds.a.o environment is on the move to a new ci-builds.a.o > > environment. Some time ago I > > created a vcl-site job to generate the VCL site. The configuration was > > still part of the Jenkins job. > > > > I just created [1] to put this into version control. I also created [2] to > > get a VCL folder created on the > > new Jenkins environment. On this new Jenkins environment access control > > changed a bit and > > access is granted per folder now. So any VCL committer is able to > > setup/manage the jobs for the VCL > > project. > > > > In [1] I created the pipeline as a multi-branch pipeline which deploys when > > changes are merged to the > > 'master' branch (default branch). Unfortunately one cannot take a quick > > peak at another project its > > job configuration anymore and since I am not a VCL committer I am not able > > to setup the job either so > > if any information is needed let me know. > > > > Roy > > > > [1] https://github.com/apache/vcl-site/pull/4 > > [2] https://issues.apache.org/jira/browse/INFRA-20561 > > >
