[FOLIO-2606] provide Vagrant image for Q1 Fameflower Created: 19/May/20 Updated: 07/Oct/20 Resolved: 26/May/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | DevOps: sprint 89 | ||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||
| Description |
|
Wayne Schneider please provide details as necessary. |
| Comments |
| Comment by Marc Johnson [ 26/May/20 ] |
|
What version of the release will this Vagrant box be based upon, the initial release, the official release or post service pack? |
| Comment by Wayne Schneider [ 26/May/20 ] |
|
I was asked by Anton Emelianov to provide the latest released modules, as defined by the tip of the Q1-2020 branch of platform-complete. So that is "post service pack," I think. |
| Comment by Anton Emelianov (Inactive) [ 26/May/20 ] |
|
Yes, it should be post service pack. |
| Comment by Marc Johnson [ 26/May/20 ] |
|
Wayne Schneider Anton Emelianov Hmm, that is different to what Oleksii Petrenko stated on Slack
|
| Comment by Anton Emelianov (Inactive) [ 26/May/20 ] |
|
Marc Johnson, I resolved it with Oleksii Petrenko. We should use what is in https://jenkins-aws.indexdata.com/job/folio-org/job/platform-complete/job/q1-2020/ |
| Comment by Wayne Schneider [ 26/May/20 ] |
|
release-core Vagrant box available as folio/release-core (https://app.vagrantup.com/folio/boxes/release-core) Building complete release box now. |
| Comment by Wayne Schneider [ 26/May/20 ] |
|
"release" Vagrant box available as folio/release (https://app.vagrantup.com/folio/boxes/release). Anton Emelianov Oleksii Petrenko please let me know if you need me to do anything to get the information out to the teams, otherwise I'll rely on you to keep teams informed. Thanks! |
| Comment by Marc Johnson [ 27/May/20 ] |
|
I'd like to check my understanding.
Does that mean that there is a single release vagrant box image and so only the latest official release will be available as a vagrant image? In effect, at some point that box will switch to tracking the 2020 Q2 branch at some point (it can be decided later when that transition happens)? |
| Comment by Wayne Schneider [ 27/May/20 ] |
|
Marc Johnson Vagrant boxes can have multiple versions available, so any number of releases can be available at the same time. You can designate which version you want by using the --box-version option on vagrant init or by manually updating your Vagrantfile to designate the box version, e.g.: Vagrant.configure("2") do |config| config.vm.box = "folio/release" config.vm.box_version = "1.0.0-20200526.4318" end We can certainly talk about structuring version numbering going forward. Vagrant requires that box versions follow semantic versioning conventions. The current convention is "1.0.0-[date].[build number]" |
| Comment by Marc Johnson [ 27/May/20 ] |
|
Wayne Schneider Thanks
Sure. It was more about that the versions of the box follow one thread, a particular branch build of a platform. (This might become important when we support multiple quarterly releases at once and they might change concurrently) I'm not proposing any changes. I only wanted to make sure I understand what had been done. |