Date
1 - 2 of 2
RPMbuild verify & merge jobs
Greetings folks,
Well, we finally have a working rpmbuild script! Because of that I've
created two new jobs integration-verify-rpmbuild &
integration-merge-rpmbuild which are watching for changes in
packaging/rpm/** so we should start seeing -1/+1 from jenkins on patch
submissions there.
We only push new artifacts on a successful merge build (of course).
Also, please note that our build script does not pick up new .spec files
(presently) so it's very possible that a new spec file will break the
build after it's been added to the builder script :(
Sam and I will probably need to noodle on that some to come up with a
good way to handle new spec files showing up and being able to build the
right away (if possible).
-Andy-
--
Andrew J Grimberg
Systems Administrator
The Linux Foundation
Well, we finally have a working rpmbuild script! Because of that I've
created two new jobs integration-verify-rpmbuild &
integration-merge-rpmbuild which are watching for changes in
packaging/rpm/** so we should start seeing -1/+1 from jenkins on patch
submissions there.
We only push new artifacts on a successful merge build (of course).
Also, please note that our build script does not pick up new .spec files
(presently) so it's very possible that a new spec file will break the
build after it's been added to the builder script :(
Sam and I will probably need to noodle on that some to come up with a
good way to handle new spec files showing up and being able to build the
right away (if possible).
-Andy-
--
Andrew J Grimberg
Systems Administrator
The Linux Foundation
Forgot to mention, we're only building Fedora 19 packages at present. My
last test with trying to get EL6 packages to build was failing and I
haven't tracked down why yet.
Also, I know that Sam has been asked by a few folks where they can get
the RPMs here's the links to the current -release RPMs. They have the
appropriate .repo files in them and _disable_ the testing repo by
default and _enable_ the release repo (as would be expected ;) )
EPEL6 systems:
https://nexus.opendaylight.org/content/repositories/opendaylight-yum-epel-6-x86_64/rpm/opendaylight-release/0.1.0-1.el6.noarch/opendaylight-release-0.1.0-1.el6.noarch.rpm
Fedora 19 systems:
https://nexus.opendaylight.org/content/repositories/opendaylight-yum-fedora-19-x86_64/rpm/opendaylight-release/0.1.0-1.fc19.noarch/opendaylight-release-0.1.0-1.fc19.noarch.rpm
One other note. We don't presently have any GPG signing setup so
the .repo files are configure to disable gpgchecking for themselves.
There's a copy of the -release rpm in the testing repositories as well.
Just tack a -testing onto the end of the x86_64 ;)
-Andy-
toggle quoted message
Show quoted text
last test with trying to get EL6 packages to build was failing and I
haven't tracked down why yet.
Also, I know that Sam has been asked by a few folks where they can get
the RPMs here's the links to the current -release RPMs. They have the
appropriate .repo files in them and _disable_ the testing repo by
default and _enable_ the release repo (as would be expected ;) )
EPEL6 systems:
https://nexus.opendaylight.org/content/repositories/opendaylight-yum-epel-6-x86_64/rpm/opendaylight-release/0.1.0-1.el6.noarch/opendaylight-release-0.1.0-1.el6.noarch.rpm
Fedora 19 systems:
https://nexus.opendaylight.org/content/repositories/opendaylight-yum-fedora-19-x86_64/rpm/opendaylight-release/0.1.0-1.fc19.noarch/opendaylight-release-0.1.0-1.fc19.noarch.rpm
One other note. We don't presently have any GPG signing setup so
the .repo files are configure to disable gpgchecking for themselves.
There's a copy of the -release rpm in the testing repositories as well.
Just tack a -testing onto the end of the x86_64 ;)
-Andy-
On Fri, 2014-01-24 at 15:31 -0800, Andrew Grimberg wrote:
Greetings folks,
Well, we finally have a working rpmbuild script! Because of that I've
created two new jobs integration-verify-rpmbuild &
integration-merge-rpmbuild which are watching for changes in
packaging/rpm/** so we should start seeing -1/+1 from jenkins on patch
submissions there.
We only push new artifacts on a successful merge build (of course).
Also, please note that our build script does not pick up new .spec files
(presently) so it's very possible that a new spec file will break the
build after it's been added to the builder script :(
Sam and I will probably need to noodle on that some to come up with a
good way to handle new spec files showing up and being able to build the
right away (if possible).
-Andy-
--
Andrew J Grimberg
Systems Administrator
The Linux Foundation
Andrew J Grimberg
Systems Administrator
The Linux Foundation