-
Notifications
You must be signed in to change notification settings - Fork 47
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
Use mirror repo for unit tests to avoid need for credentials #22
Comments
I just found |
By the way, THANK YOU @fooman for setting up the mirror! |
I think this is just work in progress. The first step into improving things was to add secrets, so that the secrets could be used in different actions - this is what I'm using already, but indeed, the secrets will not work with Pull Requests :( For that matter, there is no way to share an environment variable ("secret") with others than the contributors of the project. However, the thing that you bump into is more a flaw in the documentation, than the actual workflow files. In the docs, it is mentioned to use the following snippet: jobs:
env:
MAGENTO_MARKETPLACE_USERNAME: ${{ secrets.MAGENTO_MARKETPLACE_USERNAME }}
MAGENTO_MARKETPLACE_PASSWORD: ${{ secrets.MAGENTO_MARKETPLACE_PASSWORD }} But it is quite common that people fill in the details differently. The dependency in the workflow files is with the environment variable. The way to fill in that environment variable - for instance, using secrets or hard-coded - is up to you. (Obviously, hard-coded is not pretty.) jobs:
env:
MAGENTO_MARKETPLACE_USERNAME: foo
MAGENTO_MARKETPLACE_PASSWORD: bar But you already changed the topic: Why not use the mirror? Good point - I see no reason not to. I'm going to fix that right away. Ideally, with a switch |
Done. |
Awesome, thanks @jissereitsma. This should make it easier to use for open source modules. |
Cam this issue be closed? |
Let's keep it open for the moment. I'd like to take a look at pre-seeding the Composer cache for the mirror repo. |
Am still also considering pre-building images to effectively jump straight to here |
@fooman As of yet, all is working fine with this change. Can we close this issue? |
The unit test build requires setting
secrets.MAGENTO_MARKETPLACE_USERNAME
andsecrets.MAGENTO_MARKETPLACE_PASSWORD
.For myself as the maintainer that is not a problem, but it means I have to ask every contributor to set up the secrets when they open a PR...
I'm just wondering, shouldn't it be possible to execute the build without the credentials, since it also works for the integration test build?
The text was updated successfully, but these errors were encountered: