How can I add a custom button on GitHub.com which I could click on in order to deploy changes from the Master branch to a related Salesforce.com DEV Org?
What have you tried? Have you seen https://developer.salesforce.com/blogs/2020/01/using-salesforce-dx-with-github-actions ?
You can steal sample actions from SF official repo at https://github.com/trailheadapps/lwc-recipes.
You'll need to provide the secret login URL to your target org, there are blog posts how to generate it and store in GitHub variable, for example https://tigerfacesystems.com/blog/sfdx-continuous-integration/ or https://github.com/sfdx-actions/setup-sfdx
Last but not least - to have action available for manual run (not just automated) read up about "workflow_dispatch"
our project "XY" is certified and deployed in production. We are migrating our production from bare metal to cloud platform. In the process we are changing DNS and domain. The only changes we are trying to achieve are update fulfillment and linking endpoints for this project.
According to: https://developers.google.com/assistant/smarthome/develop/launching#modify-action
We must go through 3 stages:
Resubmit your test suite results.
Fill out a new certification request form.
Resubmit your Action for review.
The first phase is not accomplishable:
In order to run the test suite:
A) Enabled device testing for current draft. (Success)
B) Link action to your google account using the same account you used to sign in to the actions console. (failed)
Why does the "B" fail ?
Enabling current draft for testing do not reflect changes in the fulfillment and linking endpoints.
During the linking process in the Google Home app there is no option to select draft under the [test] prefixed section. I can only see linking for the deployed version which is already certified but has old endpoints to fulfillment and linking. The test suite has no relevance against the deployed version. I want to test against the current draft.
I've come across the same problem:
Testing the Google Smart Home Action
What can I do for resubmit test suite results ?
Thanks for pointing this out, we are working to improve this process.
For testing of your new configuration, I'll bring over part of the answer from the question you linked:
Once your Action is deployed to production, the project will no longer reflect console changes to the test agent until those changes are submitted and reviewed. The recommended way to work around this constraint is to create a second project in the Actions console that you can use to test/validate your change.
For deploying production, I would recommend resubmitting your new Action version for review without using the test suite. During review, the certification team will reach out to you and work with you on the fact that this is an update to an existing Action.
Concourse CI provides an easy way to trigger and abort pipeline job builds via the web interface or the fly CLI.
I haven't found a way to determine who performed these actions after the fact. Is this information logged somewhere that can be accessed by users?
The information displayed on the web page and accessible by the fly watch command doesn't appear to contain these details.
There was the work-around to viewing this, you can enable auditing and check the logs (Check_Here).
But there was one open issue related to display who triggered job in the UI (Check Issue here)
Our App Center 'Build on every push' is not working. When I merge a PR in Azure DevOps and refresh App Center it shows the new commit but never triggers a build even though the build is configured to do so. This issue reports the same issue, but doesn't offer any resolution.
In Azure DevOps I see two service hooks configured for App Center (both created by an ex-employee). When I try to test those hooks, both return a 404 error from App Center. I can find no documentation on how service hooks between Azure DevOps and App Center should be set up.
Is there some way I can disconnect the service hooks and re-create them?
Is there some way I can disconnect the service hooks and re-create them?
The answer is yes.
You could go to the Project Settings->Service hook, select the service hook for App Center. You could delete it, then create a new service hook:
If you could not delete it, please check if you have permission to delete the service hook.
Update:
Since you want to create a service hook, you could configure it as follows stpes:
Select Azure devops as service on the Build tab:
Sign in with your Azure devops account and select the project you want to build.
Make sure the option Build this branch on every push is select:
Then, we could submit any change in that project in azure devops repo, the build in app center will be triggered. We could also check the service hook:
Hope this helps.
I contacted App Center support using the chat button in the lower corner. They did a soft reset on the projects on their back end and the existing service hooks started working.
Not sure could I have fixed the issue without support, as I didn't try recreating the service hooks myself.
I've installed the Google Cloud Build app from Github Marketplace, and enabled it on several repositories, only to discover that enabling access for those repositories automatically starts running the Google Cloud Build "check" after every PR or push to a PR. Since some of those repositories are not actually ready for Google Cloud build, I needed to turn off the checks... I used the URL mentioned in the docs to get to the page where you can select which repositories should be connected to your GCP project, and unchecked a bunch of them... this disconnected them from the project, but, surprisingly, did not disable the Github checks! So now, there are Github checks on several repositories that just result in an error because they're not connected to any projects in Cloud Build.
Surely, it is not an uncommon use case to need a way to "disable Checks" on a per-repository basis - is there any way to do that?
(If not, consider it a requested feature if there are any Google Engineers reading!) ;)
I did talk to chat support, and the only way we could figure out to remove the checks would be to uninstall Google Cloud Build completely from the entire organization, which I don't want to do because we do have some setup that I want to keep, and I don't know how much of that configuration would have to be redone if I uninstalled it completely.
Here is a screenshot of the broken check that I can't disable:
I think there are 2 steps to disable CloudBuild,
1. Disable on CloudBuild itself. For some time I kept seeing 2 builds per push made, but disabling a trigger on CloudBuild helped fix that.
2. On Github, you can configure the Cloudbuild app to monitor a specific repo on the organization level setting.
3. If you feel a lot adventurous though and it's not solved, on the project level setting, you could delete the Webhooks integration for cloudbuild, as that's what Github notifies of each build.
It can be found within GH App installations:
https://console.cloud.google.com/gcb-github-registration
Select the GH account used for your link between Cloud Build and GH, then the GCP project you want to edit.
Here connected repositories can be edited, and in the second step (Trigger settings), the "Default GitHub Checks" can be disabled.
You can also goto settings of your repository and click installations inside settings.
And then remove Google cloud build from Installed apps and authorized github apps.
Cloud Build Triggers are still in beta, and have gone through several updates since this question was posted, but it now appears that the "Github Default Checks" are no longer hidden from management. They are now explicitly offered (but not automatically created) when connecting a repo, and you can finally view and disable (or delete) individual "Github Default Checks" on the trigger management page: https://console.cloud.google.com/cloud-build/triggers
I'll leave this as unanswered, because I'm uncertain this is how it is working for everyone, or that this answer will remain true, but if it works for you, feel free to vote up the answer!
To link GCP Project to the Github repository, create a trigger by clicking on resolve link, besides Action Required and then disable the same. For me this procedure worked out.