Packaging and nightlies post-Rails 4

Development
1

Our nightly repos over the next few weeks are going to be stale and/or
unstable, as we try and update packages in response to the update of
Foreman to use Rails 4. Many people (inc. myself) won't be around much
for a few weeks, so please be patient as we figure it out.

TLDR: maintainers of the plugins listed below, please release updates.

Debian packages of Foreman should be built automatically, unless there
are unforeseen issues, will be pushed to the nightly archives shortly I
think. Many plugins won't work until their maintainers issue updates
and packages are created, so be wary when updating. See the list below
for more info.

New nightly RPMs of Foreman core or plugin releases won't be published
until further notice. I will try and keep plugin releases going to
non-nightly repos if possible - so continue to send PRs to rpm/develop
and we'll cherry pick them to other releases and build as usual. The
nightly builds will depend on how far Foreman core packaging has progressed.

Before merge of Rails 4, I'll suspend RPM builds of Foreman core until
the associated PR
(https://github.com/theforeman/foreman-packaging/pull/877) is merged and
all of the updated packages are rebuilt. This ought to be ready within
a week, but I'll send an update when Foreman core RPM builds have
resumed in Koji.

Plugin updates will be required next from the following projects, which
must be compatible with develop/Rails 4:

  • foreman_bootdisk
  • foreman_discovery
  • foreman_docker
  • foreman_setup
  • foreman-tasks

These projects may also need updates, I'm unsure of their current
compatibility:

  • foreman_deployments
  • foreman_remote_execution
  • foreman_salt

Others may still be incompatible, these are just the ones where the
packages can't even be built.

Updates to all of the above plugins will be needed for both RPM and
Debian package builds. If maintainers can send PRs to the two packaging
develop branches to update plugins on release, it'll help a great deal
to get this all fixed.

Once the plugins are updated then we can push nightly builds to
yum.theforeman.org again. If some plugins don't get updated after a
couple of weeks, I'll exclude them temporarily via comps/.

Any packages that haven't been pushed to the main mirrors are accessible
via http://stagingdeb.theforeman.org (under theforeman-nightly),
http://koji.katello.org/koji and
http://koji.katello.org/releases/yum/foreman-nightly/.

··· -- Dominic Cleal dominic@cleal.org
2

The Katello XL pipeline has also been shut down for the time being until
packaging is complete which means there won't be any new nightly packages
pushed out to our repositories either.

Dominic – if there is anything specific packaging wise I can help with
please let me know as I am happy to work on any of the packages that need
building and do testing to get the RPMs out there for testing.

Eric

··· On Fri, Dec 18, 2015 at 5:55 AM, Dominic Cleal wrote:

Our nightly repos over the next few weeks are going to be stale and/or
unstable, as we try and update packages in response to the update of
Foreman to use Rails 4. Many people (inc. myself) won’t be around much
for a few weeks, so please be patient as we figure it out.

TLDR: maintainers of the plugins listed below, please release updates.

Debian packages of Foreman should be built automatically, unless there
are unforeseen issues, will be pushed to the nightly archives shortly I
think. Many plugins won’t work until their maintainers issue updates
and packages are created, so be wary when updating. See the list below
for more info.

New nightly RPMs of Foreman core or plugin releases won’t be published
until further notice. I will try and keep plugin releases going to
non-nightly repos if possible - so continue to send PRs to rpm/develop
and we’ll cherry pick them to other releases and build as usual. The
nightly builds will depend on how far Foreman core packaging has
progressed.

Before merge of Rails 4, I’ll suspend RPM builds of Foreman core until
the associated PR
(https://github.com/theforeman/foreman-packaging/pull/877) is merged and
all of the updated packages are rebuilt. This ought to be ready within
a week, but I’ll send an update when Foreman core RPM builds have
resumed in Koji.

Plugin updates will be required next from the following projects, which
must be compatible with develop/Rails 4:

  • foreman_bootdisk
  • foreman_discovery
  • foreman_docker
  • foreman_setup
  • foreman-tasks

These projects may also need updates, I’m unsure of their current
compatibility:

  • foreman_deployments
  • foreman_remote_execution
  • foreman_salt

Others may still be incompatible, these are just the ones where the
packages can’t even be built.

Updates to all of the above plugins will be needed for both RPM and
Debian package builds. If maintainers can send PRs to the two packaging
develop branches to update plugins on release, it’ll help a great deal
to get this all fixed.

Once the plugins are updated then we can push nightly builds to
yum.theforeman.org again. If some plugins don’t get updated after a
couple of weeks, I’ll exclude them temporarily via comps/.

Any packages that haven’t been pushed to the main mirrors are accessible
via http://stagingdeb.theforeman.org (under theforeman-nightly),
http://koji.katello.org/koji and
http://koji.katello.org/releases/yum/foreman-nightly/.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

3

> From: "Dominic Cleal" <dominic@cleal.org>
> To: "foreman-dev" <foreman-dev@googlegroups.com>
> Sent: Friday, December 18, 2015 5:55:56 AM
> Subject: [foreman-dev] Packaging and nightlies post-Rails 4
>
> Our nightly repos over the next few weeks are going to be stale and/or
> unstable, as we try and update packages in response to the update of
> Foreman to use Rails 4. Many people (inc. myself) won't be around much
> for a few weeks, so please be patient as we figure it out.
>
> TLDR: maintainers of the plugins listed below, please release updates.
>
> Debian packages of Foreman should be built automatically, unless there
> are unforeseen issues, will be pushed to the nightly archives shortly I
> think. Many plugins won't work until their maintainers issue updates
> and packages are created, so be wary when updating. See the list below
> for more info.
>
> New nightly RPMs of Foreman core or plugin releases won't be published
> until further notice. I will try and keep plugin releases going to
> non-nightly repos if possible - so continue to send PRs to rpm/develop
> and we'll cherry pick them to other releases and build as usual. The
> nightly builds will depend on how far Foreman core packaging has progressed.
>
> Before merge of Rails 4, I'll suspend RPM builds of Foreman core until
> the associated PR
> (https://github.com/theforeman/foreman-packaging/pull/877) is merged and
> all of the updated packages are rebuilt. This ought to be ready within
> a week, but I'll send an update when Foreman core RPM builds have
> resumed in Koji.
>
> Plugin updates will be required next from the following projects, which
> must be compatible with develop/Rails 4:
>
> - foreman_bootdisk
> - foreman_discovery
> - foreman_docker
> - foreman_setup
> - foreman-tasks
>
> These projects may also need updates, I'm unsure of their current
> compatibility:
>
> - foreman_deployments
> - foreman_remote_execution
>
> - foreman_salt

Tests have been red for a while, will hopefully find some time over the next
couple weeks to fix this, and now that'll include whatever I need to do for rails 4.

··· ----- Original Message -----

Others may still be incompatible, these are just the ones where the
packages can’t even be built.

Updates to all of the above plugins will be needed for both RPM and
Debian package builds. If maintainers can send PRs to the two packaging
develop branches to update plugins on release, it’ll help a great deal
to get this all fixed.

Once the plugins are updated then we can push nightly builds to
yum.theforeman.org again. If some plugins don’t get updated after a
couple of weeks, I’ll exclude them temporarily via comps/.

Any packages that haven’t been pushed to the main mirrors are accessible
via http://stagingdeb.theforeman.org (under theforeman-nightly),
http://koji.katello.org/koji and
http://koji.katello.org/releases/yum/foreman-nightly/.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

Thanks for heads-up.

> - foreman_discovery

Will take a look through the holidays. If not, then early January
discovery plugin will work again with develop.

··· -- Later, Lukas #lzap Zapletal
5

Foreman core's been built now into foreman-nightly-rhel* tags and I'm
beginning to work on the plugin dependency builds, while merging in the
open PRs that I can as I go.

Automatic builds of Foreman core are re-enabled in Jenkins, but will not
be tested or pushed to the mirrors until the plugin repo's reasonable
ready too.

··· On 18/12/15 10:55, Dominic Cleal wrote: > New nightly RPMs of Foreman core or plugin releases won't be published > until further notice. I will try and keep plugin releases going to > non-nightly repos if possible - so continue to send PRs to rpm/develop > and we'll cherry pick them to other releases and build as usual. The > nightly builds will depend on how far Foreman core packaging has progressed. > > Before merge of Rails 4, I'll suspend RPM builds of Foreman core until > the associated PR > (https://github.com/theforeman/foreman-packaging/pull/877) is merged and > all of the updated packages are rebuilt. This ought to be ready within > a week, but I'll send an update when Foreman core RPM builds have > resumed in Koji.

–
Dominic Cleal
dominic@cleal.org

6

> Debian packages of Foreman should be built automatically, unless there
> are unforeseen issues, will be pushed to the nightly archives shortly I
> think. Many plugins won't work until their maintainers issue updates
> and packages are created, so be wary when updating. See the list below
> for more info.

Debian packages are now being published after #12876 was fixed. Some
plugins have already received compatibility updates.

> These projects may also need updates, I'm unsure of their current
> compatibility:
>
> - foreman_deployments

Filed http://projects.theforeman.org/issues/12941.

> - foreman_remote_execution

Discussion at
https://github.com/theforeman/foreman-packaging/pull/929#issuecomment-167105606
since I know the plugin doesn't attempt to maintain nightly
compatibility. It'll probably have to be removed as repo tests will
fail if it's not rebuilt.

> - foreman_salt

Filed http://projects.theforeman.org/issues/12942.

··· On 18/12/15 10:55, Dominic Cleal wrote:

–
Dominic Cleal
dominic@cleal.org

7

> Plugin updates will be required next from the following projects, which
> must be compatible with develop/Rails 4:
[…]
> Others may still be incompatible, these are just the ones where the
> packages can't even be built.

foreman_chef also has a problem, filed at
Feature #12994: Support for Rails 4 - Chef - Foreman.

··· On 18/12/15 10:55, Dominic Cleal wrote:

–
Dominic Cleal
dominic@cleal.org

8

I think all of the RPMs in Koji for nightlies are in a good state, with
builds for Fedora 21 (updated from 19 to match Rails) and others are
converted to the newer SCLs.

With the exception of a few plugins that aren't updated (see below),
I'll push the repos at the start of next week, around Monday.

> Once the plugins are updated then we can push nightly builds to
> yum.theforeman.org again. If some plugins don't get updated after a
> couple of weeks, I'll exclude them temporarily via comps/.

The following plugins remain incompatible with post-Rails 4 and will be
temporarily removed from the updated nightly repos as they can't be
built/installed:

foreman_bootdisk
foreman_chef
foreman_deployments
foreman_discovery
foreman_remote_execution
foreman_salt
foreman_docker's fixed, but the package is blocked on #13005 in Foreman.

Please release a new gem once fixed - bonus points if you can also
submit foreman-packaging PRs. Thanks to those that have already updated.

··· On 18/12/15 10:55, Dominic Cleal wrote:

–
Dominic Cleal
dominic@cleal.org

9

> From: "Dominic Cleal" <dominic@cleal.org>
> To: "foreman-dev" <foreman-dev@googlegroups.com>
> Sent: Friday, December 18, 2015 11:55:56 AM
> Subject: [foreman-dev] Packaging and nightlies post-Rails 4
>
> Our nightly repos over the next few weeks are going to be stale and/or
> unstable, as we try and update packages in response to the update of
> Foreman to use Rails 4. Many people (inc. myself) won't be around much
> for a few weeks, so please be patient as we figure it out.
>
> TLDR: maintainers of the plugins listed below, please release updates.
>
> Debian packages of Foreman should be built automatically, unless there
> are unforeseen issues, will be pushed to the nightly archives shortly I
> think. Many plugins won't work until their maintainers issue updates
> and packages are created, so be wary when updating. See the list below
> for more info.
>
> New nightly RPMs of Foreman core or plugin releases won't be published
> until further notice. I will try and keep plugin releases going to
> non-nightly repos if possible - so continue to send PRs to rpm/develop
> and we'll cherry pick them to other releases and build as usual. The
> nightly builds will depend on how far Foreman core packaging has progressed.
>
> Before merge of Rails 4, I'll suspend RPM builds of Foreman core until
> the associated PR
> (https://github.com/theforeman/foreman-packaging/pull/877) is merged and
> all of the updated packages are rebuilt. This ought to be ready within
> a week, but I'll send an update when Foreman core RPM builds have
> resumed in Koji.
>
> Plugin updates will be required next from the following projects, which
> must be compatible with develop/Rails 4:
>
> - foreman_bootdisk
> - foreman_discovery
> - foreman_docker
> - foreman_setup
> - foreman-tasks
>
> These projects may also need updates, I'm unsure of their current
> compatibility:
>
> - foreman_deployments
> - foreman_remote_execution
> - foreman_salt

foreman_salt is now rails 4 compatible, PR's opened to return it to
the nightly repos. Sorry, took a while to find time to fix
everything.

··· ----- Original Message -----

Others may still be incompatible, these are just the ones where the
packages can’t even be built.

Updates to all of the above plugins will be needed for both RPM and
Debian package builds. If maintainers can send PRs to the two packaging
develop branches to update plugins on release, it’ll help a great deal
to get this all fixed.

Once the plugins are updated then we can push nightly builds to
yum.theforeman.org again. If some plugins don’t get updated after a
couple of weeks, I’ll exclude them temporarily via comps/.

Any packages that haven’t been pushed to the main mirrors are accessible
via http://stagingdeb.theforeman.org (under theforeman-nightly),
http://koji.katello.org/koji and
http://koji.katello.org/releases/yum/foreman-nightly/.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

10

I am starting to build some of the Katello repository packages into the new
SCLs but hitting an error pretty quickly on koji. Did you encounter this at
all?

http://koji.katello.org/koji/getfile?taskID=395327&name=root.log

The associated change that is being built is:
https://github.com/Katello/katello-packaging/pull/129

··· On Wed, Dec 23, 2015 at 10:31 AM, Dominic Cleal wrote:

On 18/12/15 10:55, Dominic Cleal wrote:

New nightly RPMs of Foreman core or plugin releases won’t be published
until further notice. I will try and keep plugin releases going to
non-nightly repos if possible - so continue to send PRs to rpm/develop
and we’ll cherry pick them to other releases and build as usual. The
nightly builds will depend on how far Foreman core packaging has
progressed.

Before merge of Rails 4, I’ll suspend RPM builds of Foreman core until
the associated PR
(https://github.com/theforeman/foreman-packaging/pull/877) is merged and
all of the updated packages are rebuilt. This ought to be ready within
a week, but I’ll send an update when Foreman core RPM builds have
resumed in Koji.

Foreman core’s been built now into foreman-nightly-rhel* tags and I’m
beginning to work on the plugin dependency builds, while merging in the
open PRs that I can as I go.

Automatic builds of Foreman core are re-enabled in Jenkins, but will not
be tested or pushed to the mirrors until the plugin repo’s reasonable
ready too.

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

11

Remove the ruby193-scldevel package from the build/srpm-build groups in
that build tag. The updated tfm-build package depends on the correct
scldevels (now rh-ruby22 etc.) and they will conflict with ruby193.

Also you should remove v8314-scldevel as it'll be pulled in, though it
won't cause a problem as-is.

··· On 23/12/15 17:20, Eric D Helms wrote: > I am starting to build some of the Katello repository packages into the > new SCLs but hitting an error pretty quickly on koji. Did you encounter > this at all? > > http://koji.katello.org/koji/getfile?taskID=395327&name=root.log

–
Dominic Cleal
dominic@cleal.org

12

> I think all of the RPMs in Koji for nightlies are in a good state, with
> builds for Fedora 21 (updated from 19 to match Rails) and others are
> converted to the newer SCLs.
>
> With the exception of a few plugins that aren't updated (see below),
> I'll push the repos at the start of next week, around Monday.

Foreman nightly and nightly plugin repos have been updated, minus the
following plugins:

> foreman_bootdisk
> foreman_chef
> foreman_deployments
> foreman_discovery
> foreman_remote_execution
> foreman_salt

As and when the plugins get updates released, I'll add them back in.
All the spec files etc are still in git, they're just removed from comps/.

The latest build is still a few days old (commit 51f005e), pre-dating
the Patternfly/#4629 merge. Once the corresponding packaging PRs for
that are working and merged, it'll be updated daily as usual.

··· On 06/01/16 11:20, Dominic Cleal wrote:

–
Dominic Cleal
dominic@cleal.org