this was just flat out a bug…
it should have been {os}-s
I have mail into helpdesk (because its part of jenkins master config) to alter
the flavors from ubuntu to ubuntu1604 and centos to centos7
so that the os env can be properly called.
After thats done ill get this patched back in and we should be rolling..
thanks for the help/catch matt/dave
Ed
On Oct 16, 2017, at 10:24 AM, Dave Wallace
<dwallac...@gmail.com<mailto:dwallac...@gmail.com>> wrote:
Matt,
Thanks for pointing this out. There appears to be a bug in
ci-management/jjb/vpp/vpp.yaml, where the node type is specified as 'ubuntu-s'
instead of an os node (e.g. '{os}-basebuild-8c-32g').
----- %< -----
- job-template:
name: 'vpp-test-poc-verify-{stream}-{os}'
project-type: freestyle
node: 'ubuntu-s'
----- %< -----
@Ed, is this a bug or intentional (for testing purposes only)?
Thanks,
-daw-
On 10/16/2017 11:33 AM, Matthew Smith wrote:
Hi,
After submitting a rebased patch set this morning, I went and looked at the
console output of one of the jenkins jobs that kicked off automatically. The
job was named vpp-test-poc-verify-master-centos7. It caught my eye that the
name of the job implies that it should be running on CentOS 7 but the console
output showed that it was building deb packages. Here’s the full console log
for that build:
https://jenkins.fd.io/job/vpp-test-poc-verify-master-centos7/255/consoleFull
Is something broken there? This seemed a little suspect to me, but I don’t have
a full understanding of what each jenkins job is supposed to be doing or how
they’re supposed to run.
Thanks,
-Matt Smith
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
