Multiple version Pages support
Is it possible to have multiple GitLab Pages generated based on branches or tags?
For example, have the current master branch release published at:
https://userGroup.gitlab.io/project/file.ext <-- master branch published here
While all tagged versions and the latest commit on each branch have a slightly different url:
https://userGroup.gitlab.io/project/branchTagName/file.ext <-- specific branch or tag published here
(Obviously, this would cause problems if the branchTagName was a directory in the main project, but that should be avoided by the person using this approach.)
It seems like it should be possible, for example having one job with an "only" to make any pushes to the master url and a second job to make pushes to a variable based url (where the variable itself is the branch or tag name ).
I'm running into two distinct problems: job name & variable usage
If I use anything other than 'pages' as the job name, everything passes but it isn't deployed. I've tried underscores, dashes, camelCase, and all lower case. Does the job name have to be exactly 'pages'? If so, I couldn't find it in any documentation, and trust me I've been looking!
As for the variable, this is the first time I've tried using them in yml, so the best I could come up with was:
paths: - public/$CI_BUILD_REF_NAME
Which causes the build to fail. Any suggestions on this front?
Pending completion of the pages infrastructure changes &1316 Allow pages to have multiple versions
group/ └── project └── public ├── master ├── v1.0 ├── v1.3 └── v2.0
- What should be the default version?
- Do we need to support migration for existing customers or create a new file structure and put it behind a feature flag?
- If we need to support migration, how, need to ensure no downtime
- How to overcome the current pages storage limitation?