Hi Foreman devs,
Our 1.15 release is almost there! Tagging is done. I kicked off the release
pipeline, which means the first release tarballs are on their way.
After that I will sign them and continue so we can build rpms & debs. As
soon as that's ready I will sign and publish them.
I am boarding a plane now, hopefully when I land the tarballs will be ready
to be signed 
Sorry for the slight delay!
In case something goes wrong let me know on this thread.
Best regards,
I guess you don't want Hammer CLI 0.10.2 packages to be merged at this
point then - do you want them merged after this release for 1.15.1, or
do not include it in the 1.15 series?
(There were requests at
https://github.com/theforeman/foreman-packaging/pull/1641 and 1638 that
would have needed your approval. They also require a number of
dependency changes/additions.)
···
On 09/05/17 12:04, Daniel Lobato wrote:
> Our 1.15 release is almost there! Tagging is done. I kicked off the
> release pipeline, which means the first release tarballs are on their way.
–
Dominic Cleal
dominic@cleal.org
Since Hammer CLI 0.10.2 contains significant usability improvements
around ssl certificates (fetching certs without need of root
permissions) and sessions (retry on expiry) I think that we should
definitely include it in 1.15.1 if it's not possible to include it in
1.15.0.
T.
···
On Tue, May 9, 2017 at 1:15 PM, Dominic Cleal wrote:
> On 09/05/17 12:04, Daniel Lobato wrote:
>> Our 1.15 release is almost there! Tagging is done. I kicked off the
>> release pipeline, which means the first release tarballs are on their way.
>
> I guess you don't want Hammer CLI 0.10.2 packages to be merged at this
> point then - do you want them merged after this release for 1.15.1, or
> do not include it in the 1.15 series?
>
> (There were requests at
> https://github.com/theforeman/foreman-packaging/pull/1641 and 1638 that
> would have needed your approval. They also require a number of
> dependency changes/additions.)
>
> --
> 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.
Update, RPMS are signed and signatures are uploaded.
Currently the pipeline is stuck on tests for Debian Stretch (not sure
if just an artifact or a real failure yet, investigating).
Help investigating the issue would be appreciated
After tests pass on Debian stretch both RPMs and debs will be pushed
to their respective repos as you can see in the pipeline.
http://ci.theforeman.org/view/Release%20pipeline/
···
On Tue, May 9, 2017 at 8:04 PM, Daniel Lobato wrote:
> Hi Foreman devs,
>
> Our 1.15 release is almost there! Tagging is done. I kicked off the release
> pipeline, which means the first release tarballs are on their way.
>
> After that I will sign them and continue so we can build rpms & debs. As
> soon as that's ready I will sign and publish them.
>
> I am boarding a plane now, hopefully when I land the tarballs will be ready
> to be signed :) Sorry for the slight delay!
>
> In case something goes wrong let me know on this thread.
>
> Best regards,
–
Daniel Lobato
@dlobatog
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
1.15.1 is expected to be released around 2 weeks after .0.
From what I see the biggest change seems to be
https://github.com/theforeman/foreman-packaging/pull/1627 (for debs)
rpm-wise the changes are not as critical I think, so if they can be
built for 1.15.1
that'd be good, there are 2 weeks of nightlies to test hammer before
the release.
···
On Tue, May 9, 2017 at 10:55 PM, Tomas Strachota wrote:
> Since Hammer CLI 0.10.2 contains significant usability improvements
> around ssl certificates (fetching certs without need of root
> permissions) and sessions (retry on expiry) I think that we should
> definitely include it in 1.15.1 if it's not possible to include it in
> 1.15.0.
>
> T.
>
> On Tue, May 9, 2017 at 1:15 PM, Dominic Cleal wrote:
>> On 09/05/17 12:04, Daniel Lobato wrote:
>>> Our 1.15 release is almost there! Tagging is done. I kicked off the
>>> release pipeline, which means the first release tarballs are on their way.
>>
>> I guess you don't want Hammer CLI 0.10.2 packages to be merged at this
>> point then - do you want them merged after this release for 1.15.1, or
>> do not include it in the 1.15 series?
>>
>> (There were requests at
>> https://github.com/theforeman/foreman-packaging/pull/1641 and 1638 that
>> would have needed your approval. They also require a number of
>> dependency changes/additions.)
>>
>> --
>> 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.
>
> --
> 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.
–
Daniel Lobato
@dlobatog
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Thanks, it seems like either I don't understand the combination filter
or it didn't work
(https://github.com/theforeman/foreman-infra/blob/cb03c58b7b2bf3b5c61a125e4c32841a07a6a274/puppet/modules/jenkins_job_builder/files/theforeman.org/yaml/jobs/release_test.yaml#L33)
combination-filter: 'os == "el7" || os == "f24" || os == "jessie" ||
(os == "stretch" && version != "1.14" && version != "1.15") || os ==
"trusty" || os == "xenial"'
I removed it from the job just to run it once and it passes fine.
http://ci.theforeman.org/job/release_push_deb/ doesn't have a
combination filter so it just publishes to the other 3 repos.(jessie
trusty and xenial).
http://ci.theforeman.org/view/Release%20pipeline/
···
On Thu, May 11, 2017 at 2:02 AM, Michael Moll wrote:
> Hi,
>
> On Thu, May 11, 2017 at 01:57:26AM +0900, Daniel Lobato wrote:
>> Currently the pipeline is stuck on tests for Debian Stretch (not sure
>> if just an artifact or a real failure yet, investigating).
>
> Stretch is not supported with 1.15 (and known to fail). So that should
> get overriden for 1.15 (or whatever the approach is with these jobs in
> similar situations).
>
> Regards
> --
> Michael Moll
>
> --
> 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.
–
Daniel Lobato
@dlobatog
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> Thanks, it seems like either I don't understand the combination filter
> or it didn't work
> (https://github.com/theforeman/foreman-infra/blob/cb03c58b7b2bf3b5c61a125e4c32841a07a6a274/puppet/modules/jenkins_job_builder/files/theforeman.org/yaml/jobs/release_test.yaml#L33)
>
> combination-filter: 'os == "el7" || os == "f24" || os == "jessie" ||
> (os == "stretch" && version != "1.14" && version != "1.15") || os ==
> "trusty" || os == "xenial"'
It should have been using major_version, fixed.
> http://ci.theforeman.org/job/release_push_deb/ doesn't have a
> combination filter so it just publishes to the other 3 repos.(jessie
> trusty and xenial).
Fixed, added stretch.
···
On 11/05/17 02:16, Daniel Lobato wrote:
–
Dominic Cleal
dominic@cleal.org
Thanks - all packages are out now, freight cache needs to be updated
by someone with access to deb.theforeman.org, see the steps in:
http://projects.theforeman.org/projects/foreman/wiki/Release_Process#Completion-tasks
Similarly, those who have permissions please update Twitter, IRC and
Google+ , I've just posted the announcement to foreman-users
···
On Thu, May 11, 2017 at 4:12 PM, Dominic Cleal wrote:
> On 11/05/17 02:16, Daniel Lobato wrote:
>> Thanks, it seems like either I don't understand the combination filter
>> or it didn't work
>> (https://github.com/theforeman/foreman-infra/blob/cb03c58b7b2bf3b5c61a125e4c32841a07a6a274/puppet/modules/jenkins_job_builder/files/theforeman.org/yaml/jobs/release_test.yaml#L33)
>>
>> combination-filter: 'os == "el7" || os == "f24" || os == "jessie" ||
>> (os == "stretch" && version != "1.14" && version != "1.15") || os ==
>> "trusty" || os == "xenial"'
>
> It should have been using major_version, fixed.
>
>> http://ci.theforeman.org/job/release_push_deb/ doesn't have a
>> combination filter so it just publishes to the other 3 repos.(jessie
>> trusty and xenial).
>
> Fixed, added stretch.
>
> --
> 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.
–
Daniel Lobato
@dlobatog
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Packages have been passing in nightly now, so I've built them all into
the 1.15 staging repos. Hopefully I've not missed any changes, but let
me know if there's a related test failure during the next release and I
can re-check.
···
On 10/05/17 06:01, Daniel Lobato wrote:
> 1.15.1 is expected to be released around 2 weeks after .0.
> From what I see the biggest change seems to be
> https://github.com/theforeman/foreman-packaging/pull/1627 (for debs)
> rpm-wise the changes are not as critical I think, so if they can be
> built for 1.15.1
> that'd be good, there are 2 weeks of nightlies to test hammer before
> the release.
–
Dominic Cleal
dominic@cleal.org
I've changed the stable symlinks, rebuilding the cache now.
···
On 12/05/17 00:14, Daniel Lobato wrote:
> Thanks - all packages are out now, freight cache needs to be updated
> by someone with access to deb.theforeman.org
–
Dominic Cleal
dominic@cleal.org
