[FOLIO-1131] Add FOLIO Software Build pipeline graphic to documentation Created: 16/Mar/18  Updated: 12/Nov/18  Resolved: 26/Mar/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Peter Murray Assignee: Peter Murray
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 2 hours, 45 minutes
Original estimate: Not Specified

Sprint:

 Comments   
Comment by Peter Murray [ 16/Mar/18 ]

Wayne Schneider - Can you verify that the Software Build Pipeline section of http://folio-1131-software-build-pipeline.dev.folio.org.s3-website-us-east-1.amazonaws.com/doc/automation/ is correct? Anyone else that this should be run past to verify?

Comment by David Crossley [ 16/Mar/18 ]

That is great Peter. Seeing it in your recent presentation, i wondered if it would be good to add. Thanks.

The latest Okapi "release" is used for all three. But leaving it to Wayne to comment on the explanation.

If you want to store the source file, then there is a space at

work/graphic-source/

(Slightly related: Regarding the other sections of this document, John Malconian did suggest that the Jenkins and release information needs some revision. FOLIO-1132 Open )

Comment by Wayne Schneider [ 16/Mar/18 ]

I think we spoke about this graphic at one point before, Peter Murray. IIRC, you use "okapi" to refer to the whole of the backend, which is a little confusing to me, but I can see why you do it. Technically, Okapi is always a released version, everything else is always tip of master until regression tests pass, then folio-snapshot-stable is pinned to the released Okapi and the snapshot versions of the front- and backend modules. That is probably a level of technical detail that is not necessary for this document.

I do like the graphic, it really gives a good visual of how the systems are supposed to fit together.

Comment by Peter Murray [ 16/Mar/18 ]

Thanks for the graphic source location, David – I forgot about that.

Jakub Skoczen and Cate Boerema – I'm working on better describing the pipeline of software builds that we're using as part of a deck I'm going to offer EBSCO for the Chinese CALIS developers meeting next week. In the process, I thought it worthwhile to enhance the developer documentation. Can you take a look at the "Software Build Pipeline" section of http://folio-1131-software-build-pipeline.dev.folio.org.s3-website-us-east-1.amazonaws.com/doc/automation/

  • Is it okay to make this information more public by putting it on the developer's documentation website?
  • Is what is there essentially correct?

Note that updating the rest of the document (from the Jenkins heading to the bottom) is being talked about in FOLIO-1132 Open .

If this looks okay to you, I'll merge it into the master branch for dev.folio.org.

Comment by Peter Murray [ 21/Mar/18 ]

Jakub Skoczen and Cate Boerema – Any reason I shouldn't merge this to master on the dev.folio.org site?

Comment by Cate Boerema (Inactive) [ 22/Mar/18 ]

Looks good to me, Peter Murray, but Jakub would be better positioned to judge.

Comment by Peter Murray [ 26/Mar/18 ]

Push to production.

Generated at Thu Feb 08 23:11:04 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.