New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change release to push all bits into Maven #4829

Open
enebo opened this Issue Oct 26, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@enebo
Member

enebo commented Oct 26, 2017

@mkristian started a proof of concept of adding windows installer as an artifact: #4790. We also need all existing bit to have extra fingerprints.

As a related part of this we also need to submit PRs to the ruby managers to point at the maven urls where the bits will be at.

@enebo enebo added this to the JRuby 9.1.14.0 milestone Oct 26, 2017

@enebo enebo modified the milestones: JRuby 9.1.14.0, JRuby 9.1.15.0 Nov 8, 2017

@enebo

This comment has been minimized.

Show comment
Hide comment
@enebo

enebo Nov 8, 2017

Member

This is partially done in that we pushed fingerprints into our maven artifacts but we have not tried to get any ruby managers to start using the new url scheme yet so I am punting that part down to next point release. It should be retroactive back to 9.1.14.0 once finished.

Member

enebo commented Nov 8, 2017

This is partially done in that we pushed fingerprints into our maven artifacts but we have not tried to get any ruby managers to start using the new url scheme yet so I am punting that part down to next point release. It should be retroactive back to 9.1.14.0 once finished.

@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius Nov 29, 2017

Member

What more is outstanding for this? The Ruby managers have not addressed the related issues, but we have filed them and there's movement (in rvm at least). We are also in communication with Engine Yard about keeping their sponsored S3 around for a bit longer.

Member

headius commented Nov 29, 2017

What more is outstanding for this? The Ruby managers have not addressed the related issues, but we have filed them and there's movement (in rvm at least). We are also in communication with Engine Yard about keeping their sponsored S3 around for a bit longer.

@enebo

This comment has been minimized.

Show comment
Hide comment
@enebo

enebo Nov 29, 2017

Member

Yeah I guess finish windows installer artifacts and once those PRs happen on ruby managers we should be good.

Member

enebo commented Nov 29, 2017

Yeah I guess finish windows installer artifacts and once those PRs happen on ruby managers we should be good.

@headius headius modified the milestones: JRuby 9.1.15.0, JRuby 9.1.16.0 Dec 5, 2017

@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius Dec 5, 2017

Member

Still waiting on Windows installer logic in maven push and for Ruby installers to catch up with new URLs.

Member

headius commented Dec 5, 2017

Still waiting on Windows installer logic in maven push and for Ruby installers to catch up with new URLs.

@enebo enebo modified the milestones: JRuby 9.1.16.0, JRuby 9.1.17.0 Feb 12, 2018

@headius headius modified the milestones: JRuby 9.1.17.0, JRuby 9.2.0.0 Apr 12, 2018

@headius headius added the packaging label Apr 12, 2018

@enebo enebo modified the milestones: JRuby 9.2.0.0, JRuby 9.2.1.0 May 24, 2018

@headius

This comment has been minimized.

Show comment
Hide comment
@headius
Member

headius commented Oct 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment