For a slightly more stable URL, https://build.geoserver.org/view/release/job/geoserver-release/lastSuccessfulBuild/artifact/release/ avoids the job number.
Currently, its not possible to upload artifacts directly to https://build.geoserver.org/geoserver/releases/ for security reasons (short version - workers don't have authorization to scp to master). I looked into that when setting up the nightly builds, and didn't have much luck getting around the issue (for now, the workaround has been to archive the artifacts, and have a cron job copy them from the archive location to /geoserver). I'd still like to find a way around this, but don't really have a timeline. For the releases, the archived artifact location should work fine. The Copy Artifact Plugin <https://wiki.jenkins.io/display/JENKINS/Copy+Artifact+Plugin> (installed) can let downstream jobs (e.g. geoserver-release-publish) copy the artifacts from an upstream job directly through Jenkins. Torben On Tue, Jun 11, 2019 at 10:42 PM Jody Garnett <[email protected]> wrote: > The artifacts are attached to the build job for now: > > > https://build.geoserver.org/view/release/job/geoserver-release/240/artifact/release/2.14.4/ > > Not quite sure how to reproduce the logic to transfer them to a more > stable URL (other than uploading to source forge). > -- > Jody Garnett > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
