FHIR Chat · FHIR IG Builds Page doesn't know about new builds · IG creation

Stream: IG creation

Topic: FHIR IG Builds Page doesn't know about new builds


view this post on Zulip Jean Duteau (Dec 04 2020 at 22:18):

My FHIR-SPL build isn't showing up on the IG Builds page (https://fhir.github.io/auto-ig-builder/builds.html) and, looking at the page code, I think that is because it's a new repository that is 'main' instead of 'master'.

view this post on Zulip Max Masnick (Dec 04 2020 at 22:49):

I'm not sure if it's supported yet -- some context is here: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Primary.20branch.20name

view this post on Zulip Lloyd McKenzie (Dec 05 2020 at 02:28):

Right. At the moment, 'main' is treated as a custom branch. You need to commit a branch called 'master' if you want the content to show up in the builds list.

view this post on Zulip Lloyd McKenzie (Dec 05 2020 at 02:28):

(and the normal ci build location)

view this post on Zulip Jose Costa Teixeira (Dec 06 2020 at 13:19):

Just asking: Isn't this something that will accumulate technical debt? I mean if we have all repos maintaining a main (because github) and a master (because of our CI build)), won't that cause more and more issues?

view this post on Zulip Lloyd McKenzie (Dec 06 2020 at 15:49):

We probably want to move all repositories to use main - once that's supported.

view this post on Zulip John Keyes (Dec 10 2020 at 20:11):

Jose Costa Teixeira said:

Just asking: Isn't this something that will accumulate technical debt? I mean if we have all repos maintaining a main (because github) and a master (because of our CI build)), won't that cause more and more issues?

I've been committing my changes to master, so that I get a CI build. Once in a while I use a PR to merge those changes back onto main. Once the CI build supports main, I will do a final merge to main and then delete my master branch.

view this post on Zulip Jose Costa Teixeira (Dec 10 2020 at 20:17):

Yes, and this means we all have many unnecessary branches - accumulating technical debt

view this post on Zulip Grahame Grieve (Dec 10 2020 at 20:43):

it's low technical debt. But you either a master or a main, not both

view this post on Zulip John Keyes (Dec 10 2020 at 20:59):

New GitHub repos use main instead of master, so it seems like we temporarily need both. Not a big deal though.

view this post on Zulip Jean Duteau (Dec 10 2020 at 21:20):

I get a CI build with my main. I don't think there is any need to have a master.

view this post on Zulip John Keyes (Dec 10 2020 at 21:34):

Interesting -- I do not get CI builds from changes to main.

view this post on Zulip Jean Duteau (Dec 10 2020 at 21:35):

it's on a build tag, but they are there: http://build.fhir.org/ig/HL7/fhir-spl/branches/main/index.html

view this post on Zulip Jose Costa Teixeira (Dec 10 2020 at 21:59):

How do I set that up @Jean Duteau ?

view this post on Zulip Jean Duteau (Dec 10 2020 at 22:01):

not sure - I didn't set it up. @Lloyd McKenzie did you do anything special for fhir-spl?

view this post on Zulip Lloyd McKenzie (Dec 10 2020 at 23:02):

Builds to branches will publish, but they publish in the wrong place and they go poof after 30 days and don't show up on the builds page

view this post on Zulip Lloyd McKenzie (Dec 10 2020 at 23:03):

So in practice, you do need to create a 'master' branch to have things publish properly


Last updated: Apr 12 2022 at 19:14 UTC