On Wed, Nov 22, 2017 at 7:50 AM, Sean McGinnis wrote:
> I just put up a patch to fix the failing job:
>
> https://review.openstack.org/#/c/522284/
>
> Are you saying it was redundant though?
I was just wondering if we actually need this post-release job.
But I'll let the tripleo-ui maintainers to
Yeah, I confirm we were able to build an RPM and release a new version
of TripleO UI, which was our goal. I guess we can remove the
flacky/failing job.
On Wed, Nov 22, 2017 at 3:54 AM, Honza Pokorny wrote:
> I'm investigating on behalf of the tripleo-ui team. It looks like the
> definition for t
I'm investigating on behalf of the tripleo-ui team. It looks like the
definition for the jobs changed under us, and we'll need to update our
configuration. I'll track it down.
For the time being, though, we can safely ignore this issue. As
indicated, the publish-openstack-javascript-tarball job
Indeed, adding Jason in copy.
Do we actually need release-openstack-javascript job?
On Tue, Nov 21, 2017 at 8:27 PM, Tony Breeds wrote:
> On Wed, Nov 22, 2017 at 03:07:33AM +, z...@openstack.org wrote:
>> Build failed.
>>
>> - publish-openstack-javascript-tarball
>> http://logs.openstack.or
On Wed, Nov 22, 2017 at 03:07:33AM +, z...@openstack.org wrote:
> Build failed.
>
> - publish-openstack-javascript-tarball
> http://logs.openstack.org/e5/e5831f230bd29516dc202eb406270604f27e27f9/release/publish-openstack-javascript-tarball/9908482/
> : SUCCESS in 4m 58s
> - release-openstack
