We have integrated sentry project with our GitHub repositories, but we are unable to view commits information in Sentry releases page.
We have performed the following steps:
Configured SDK in all our repositories. So we have handled and
unhandled exceptions coming from these on our sentry.
Then integrated github repositories with sentry.
Thirdly we also created a release for one of our repositories by installing sentry CLI and associated commits by using this command: sentry-cli releases set-commits --auto $VERSION
After performing the above steps, we are still unable to gets commits information from the repository the integration has been setup. Please help what are we missing to understand or is there any addition step that we have to perform.
For reference, here is the sdk configuration:
Sentry.init({
dsn: 'https://xyz#xyz.ingest.sentry.io/292307',
release: '#1.0.0',
debug: true,
environment: config.env,
serverName: 'Webhook',
sendDefaultPii: true
})
When we run create new release command we get the following response:
Created release 1.0.0
When we associate commits to the release we get the following response:
On sentry releases, page we can see the release but commits info is not being shown.
Can anyone help me understand what we are doing wrong or is there an additional step that we need to perform to get the commits info?
Related
I have
developed a skeleton Android App in Android Studio
the Build pipeline in Azure DevOps
An Internal Testing track for this app on my Google Dev Console
Uploaded MANUALLY via the GUI of the Google Dev Console the signed .aab bundle produced
via Android Studio to the Internal Testing Track
The testers that had been set up for the track have been able to install the app on their devices and test it
The steps above work fine.
I then implemented the following
Created a Release Pipeline in Azure DevOps using the editor (not in YAML)
In this Release the Google Play Release Bundle plugin has been used (see pics
below) with its Track Property set to "Internal test" as per the available dropdown
value
Added a Deploy Stage following this Release (see pics below).
However, when the Release pipeline runs I get the error in the title (Only releases with status draft may be created on draft app.) that is also visible in the screenshots below.
I read the SO posts below
Only releases with status draft may be created on draft app
ERROR: Only releases with status draft may be created on draft app
and also articles/documentation like the following
Trigger Azure Pipelines with Postman and Parameters
Release pipelines - What is a draft Release
Releases - Create
How do I specify variables I want to edit when a release is created?
Publish to Google Play Store
I suspect that to remove the error I need to somehow create a release such that
isDraft = true;
that is a draft release that would not be rejected on deployment by the Azure Dev Console Internal Testing Track, but I am a bit at loss with it as I would have expected the Google Play Release Bundle plugin to take care of this detail for me but something apparently goes wrong or I do not clearly understand and I cannot figure out what it is or how to approach this problem in the best/simplest way.
Working on porting a Jenkins plugin to Azure Dev Ops Pipelines plugin (as per https://learn.microsoft.com/en-us/azure/devops/extend/develop/add-build-task?view=azure-devopsv ) and I've seen in the docs info about how the logging commands can be used to add annotations to the GitHub checks on the PR that's being build. (https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands)
This is great since I don't have to call GitHub APIs myself and create new GitHub App.
But in my tests it doesn't look like Azure Dev Ops Pipelines post the build log on the PR Check. Only annotations are posted. Can we also post the full log of a section that failed on GitHub PR?
If not as plan B, can we get the output of the failed build somehow so that I can manually use GItHub APIs and post it?
I refer to a lot of examples, but web hooks are not configured successfully, I do not know why? The URLs in the web hooks have also tried various situations, but they have always been 500 error.
Gitlab version : 10.6.2-ee
Jenkins version:2.83
Gitlab plugin: 1.5.4
Gitlab Hook plugin: 1.4.2
Error 500 means the server misbehaved.
You need to check the GitLab server logs to see the exact nature of the exception mentioned by the GitLab server.
It could be an authentication (token) issue, as reported in gitlab-ce issue 34143.
The OP blue mentions in the comments:
[...] because the GitLab and Jenkins services are not on a network segment.
There is also an open configuration "Allow requests to the local network from hooks and services"
That was mentioned in jenkinsci/gitlab-plugin issue 272
You have to enable "Allow requests to the local network from hooks and services" in Setting page in Gitlab with new updates.
I have set up a fresh Crafter CMS 3.0.2 installation following the instructions here. When I login as admin user I don't get Preview Sync and Sync From Repository options in the Site Config section as show in the page here. How can I add those options for the admin user? I could not find the instructions for the same in the documentation
Sync'ing is now automatic starting version 3.0.2, see the release notes: http://docs.craftercms.org/en/3.0/release-notes/index.html
You can make updates to the underlying git repo, and the system will automatically pick those up.
I want quickbuild to automatically run on each push detected on a github repository. How can I do that?
I already have a flow that clones and executes mvn deploy but I am missing an automatic trigger.
QuickBuild 5.1 adds the ability of detecting pull requests and trigger relevant builds off them. Refer to the GitHub integration guide for details:
http://wiki.pmease.com/display/QB51/Working+with+GitHub