On Fri, Jun 22, 2018 at 10:31 PM, Joan Touzet <woh...@apache.org> wrote:
> Interesting. Previously, I was told we were not allowed to push snapshot > builds > to anywhere that the public might have access - only for our development > teams. > I know you were told not to push snapshots to Bintray so as to not abuse their kindness and bandwidth as they are donating their services to us. Snapshots in general should not advertised to the general public. They should also be marked clearly as development only and not actual approved releases etc etc. Linking to the snapshots should be done on dev mailing lists and in dev areas of the websites, and not linked to from the official download pages. A good example (hosted on our own hardware is https://ci.apache.org/projects/subversion/nightlies/index.html which clearly states NOT for distribution. As for what 3rd party services can host our unofficial snapshots and releases the answer is 'it depends'. Is it a service that has been donated? Or are we paying for the service and therefore can expect more from them in terms of bandwidth and features and can we reliably notify users of their non official status. > If we are now allowed to publish snapshot/nightly/checkin-based images to > DockerHub, that eases a lot of CouchDB's pain. > I see you have lots of tags there already, but stopped some months ago. I am unsure if you were told specifically to not use dockerhub but for now at least, I do not see an issue with your resuming this - And best of all you already have a disclaimer there. Gav... > As far as running a manual job, that works, or you could potentially use > the > Promoted Builds plugin. (We don't use that, but I've used it in the past to > promote builds for release in a CI/CD setup.) > > In our case, we have to build by checking out (from git) a specific tagged > revision. The build process detects that it was checked out from a tag, and > adjusts the in-built version number to display that it is a real release, > instead of a snapshot build. Because of this, it would make more sense for > us to use a manually triggered build that takes a parameter, using the > Build With Parameters Jenkins plugin. We could then use this to force > checkout from the specific tag. > > -Joan > ----- Original Message ----- > From: "Francesco Chicchiriccò" <ilgro...@apache.org> > To: builds@apache.org > Sent: Friday, June 22, 2018 11:44:44 AM > Subject: [DISCUSS] Deploy releases to DockerHub > > Hi there, > at Syncope we have just enabled - thanks to Gavin's support - the deploy > to DockerHub via Jenkins (jobs [1][2]) - see [3]; the point is that the 3 > Docker images cannot be simply built from their respective Dockerfiles, but > need to be generated as part of the Maven build. > > Now that SNAPSHOTs are covered by [1] and [2], I was wondering how it > would be possible to push releases to DockerHub: I thought that we could > create an additional job on Jenkins, which we will manually run at end of > our release process [4]; such job will run on the GIT tag of the release. > > Gavin suggested to ask here for discussion, so here I am. > WDYT? > > Regards. > > [1] https://builds.apache.org/view/S-Z/view/Syncope/job/ > Syncope-2_0_X-deploy/ > [2] https://builds.apache.org/view/S-Z/view/Syncope/job/ > Syncope-master-deploy/ > [3] https://issues.apache.org/jira/browse/INFRA-16647 > [4] http://syncope.apache.org/release-process#Finalize_the_release > -- Gav...
