You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 28, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 28, 2024. It is now read-only.
It would be great if Travis had another step that would build VersionPress and publish it somewhere so that:
Each build is uniquely identified, which our npm run build script already does. It creates something like versionpress-4.0-beta2-9-gd9a03c79.zip, which means "the closest tag is 4.0-beta2, there have been 9 commits since then and the build was from commit d9a03c79".
When in a branch / PR, the most recent build would be aliased as https://some-service.com/versionpress-branch-name.zip
Latest builds from master would be aliased as https://some-service.com/versionpress-master.zip or .../versionpress-nightly.zip.
That's the best setup but whatever gives us versionpress-nightly.zip on some known URL would already be quite useful.
It would be great if Travis had another step that would build VersionPress and publish it somewhere so that:
npm run buildscript already does. It creates something likeversionpress-4.0-beta2-9-gd9a03c79.zip, which means "the closest tag is4.0-beta2, there have been 9 commits since then and the build was from commitd9a03c79".https://some-service.com/versionpress-branch-name.zipmasterwould be aliased ashttps://some-service.com/versionpress-master.zipor.../versionpress-nightly.zip.That's the best setup but whatever gives us
versionpress-nightly.zipon some known URL would already be quite useful.