Let catalog produced by CI be hosted publicly #19

New issue

Open

opened 2023-05-30 08:12:32 +00:00 by jsheunis · 3 comments

jsheunis commented

2023-05-30 08:12:32 +00:00

(Migrated from github.com)

Build artifacts can be handled by appveyor: https://www.appveyor.com/docs/packaging-artifacts/

I'm not sure if appveyor cloud storage can act as a server, I think artifacts can only be fetched via API

Option could be to push the built catalog to a catalog branch of the inm-icf-utilities repo and then host that via github pages. On merge to main, I would say (i.e. not all PRs)

Build artifacts can be handled by appveyor: https://www.appveyor.com/docs/packaging-artifacts/ I'm not sure if appveyor cloud storage can act as a server, I think artifacts can only be fetched via API Option could be to push the built catalog to a `catalog` branch of the [inm-icf-utilities](https://github.com/psychoinformatics-de/inm-icf-utilities) repo and then host that via github pages. On merge to main, I would say (i.e. not all PRs)

jsheunis commented

2023-05-30 08:17:56 +00:00

(Migrated from github.com)

We could make use of publishing releases to: https://www.appveyor.com/docs/deployment/github/

Or just pushing to a specific branch directly: https://www.appveyor.com/docs/how-to/git-push/#conclusion

We could make use of publishing releases to: https://www.appveyor.com/docs/deployment/github/ Or just pushing to a specific branch directly: https://www.appveyor.com/docs/how-to/git-push/#conclusion

jsheunis commented

2023-05-30 08:41:44 +00:00

(Migrated from github.com)

Another option: deposit build artifacts using appveyor and then use a github action (on merge to main) to fetch that artifact (https://www.appveyor.com/docs/packaging-artifacts/#permalink-to-the-last-successful-build-artifact) and merge it into the catalog branch.

christian-monch commented

2023-05-30 09:15:42 +00:00

(Migrated from github.com)

We could make use of publishing releases to: https://www.appveyor.com/docs/deployment/github/

Or just pushing to a specific branch directly: https://www.appveyor.com/docs/how-to/git-push/#conclusion

I think putting it into a github release is not too bad. I did something like this with the Windows installer

> We could make use of publishing releases to: https://www.appveyor.com/docs/deployment/github/ > > Or just pushing to a specific branch directly: https://www.appveyor.com/docs/how-to/git-push/#conclusion I think putting it into a github release is not too bad. I did something like this with the Windows installer