Closed BClark09 closed 6 years ago
@kaikreuzer I had a bit of time to write this distribution task for both apt and yum. This way the release pipeline can just call a set of tasks and the release would be published to Bintray without my intervention.
Would I be able to duplicate the openhab-linuxpkg
project in cloudbees and call it openhab-linuxpkg-release
? This way I can have separate projects for the continuous snapshots and have something linked to the pipeline for releases.
@pfink, I have set it up so that all openhab-linuxpkg-release
would need is to be called after the pipeline with the property: OPENHAB_VERSION
set to $version
("2.2.0" for example). Would this be the best way to do it?
Yes, I think so, it could be done using the build step. Question if the pipeline job should wait for your job to complete and also if errors should be propagated. Both should only be done if openhab-linuxpkg-release
works very reliable. If it does, I think it would be nice to see everything belonging to the release in one view.
As long as there's a tar.gz file in Bintray by the time the tasks are called then it the task will be very reliable (assuming that this PR is setup correctly). I don't think the current version of the openhab-linuxpkg
task has ever failed.
@kaikreuzer, am I okay to make that new cloudbees task? (Sorry for asking again so soon, but I have some time to work and test today).
Thanks for asking (again) as I failed to receive a notification earlier on. Yes please, feel free to go ahead and create what you need on Jenkins!
Thanks!
Had a couple of Cloudbees > Artifactory > Bintray permission errors, but that's all sorted and it looks like the dry-run is fine to take away:
https://openhab.ci.cloudbees.com/job/openhab-linuxpkg-release/3/console
Closes #88
buildRelease
task.Signed-off-by: Ben Clark ben@benjyc.uk