Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add(ci): GitHub workflow to package plugin on CI/CD #22

Merged
merged 3 commits into from
Oct 2, 2024

Conversation

Guts
Copy link
Collaborator

@Guts Guts commented Oct 1, 2024

To be merged after #21

In this PR, a GitHub workflow to:

  • package the plugin on every PR where plugin's files have been modified
  • release it as GitHub Release
  • publish it automatically to official QGIS repository (see below)

@kannes to make the workflow work, you have to set your plugins.qgis.org credentials as GitHub Actions Secrets (OSGEO_PASSWORD and OSGEO_USER). Screenshot from QTribu:

image


@Guts Guts changed the title add(ci): GitHub workflow to package on main add(ci): GitHub workflow to package plugin on CI/CD Oct 1, 2024
@kannes
Copy link
Contributor

kannes commented Oct 1, 2024

Oh nice! Tbh we do not have a technical account for this yet but all our plugins are maintained by different people and their accounts... It's something we were just discussing internally the other day. Is there a standard process that you can recommend? Does OSGeo allow technical accounts? I'd like to not use my personal account for this.

@Guts
Copy link
Collaborator Author

Guts commented Oct 1, 2024

We use the oslandia account at Oslandia and the geotribu account at Geotribu but TBH it's not so important I think, personal account is OK. Iwas using it for QTribu until recently. You just need to use credentials of an user who is authorized to publish a new version of the plugin (owner or maintainer level on https://plugins.qgis.org).

For a few months, API token are available but it's still not supported in QGIS Plugin CI (opengisch/qgis-plugin-ci#285).

@Guts Guts force-pushed the ci/add-gh-workflow-to-package-on-main branch from 2b5802b to 4f496b2 Compare October 1, 2024 14:57
@Guts Guts self-assigned this Oct 2, 2024
@Guts Guts requested a review from jmkerloch October 2, 2024 04:40
Copy link
Collaborator

@jmkerloch jmkerloch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again every thing looks OK to me 🚀

@Guts Guts merged commit 47301b3 into WhereGroup:main Oct 2, 2024
1 check passed
@Guts Guts deleted the ci/add-gh-workflow-to-package-on-main branch October 2, 2024 07:36
@kannes
Copy link
Contributor

kannes commented Oct 9, 2024

I have set up the secrets with my personal account for now and switch to the technical account once we have it.

@Guts Guts added the ci-cd Intégration et déploiement continus (GitHub Action, Workflow) label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-cd Intégration et déploiement continus (GitHub Action, Workflow)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants